[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
fhempy	==0.1.768 → ==0.1.782

---

Release Notes

fhempy/fhempy (fhempy)

v0.1.782

Compare Source

Bug Fixes

• spotify: Log connection errors once instead of a traceback every interval
  (#​636,
  1590cd9)

Fixes #​635

v0.1.781

Compare Source

Bug Fixes

• Clean up errors from fhempy log (geizhals, Smart Life, SSDP, zigbee2mqtt, miio, tuya)
  (#​634,
  ea1fdb1)

• geizhals: no AttributeError when the product page can't be loaded or parsed; price readings still
  update, page errors logged once - tuya_smartlife: expired login (1010/sign invalid) sets state
  "login expired, please use set relogin" instead of an unhandled traceback; other errors retry with
  backoff - core/ssdp: pass the argument names async-upnp-client 0.48 expects; the advertisement
  listener and the SSDP search failed with TypeError, so DLNA devices were only found by chance.
  Listener retries on errors. - zigbee2mqtt: read PATH once from an interactive bash and run
  commands with a non-interactive bash, no more "cannot set terminal process group" / "no job
  control" lines in the log - miio: unreachable device logged once (and when it is back),
  python-miio "Got error when receiving" errors filtered - tuya: unreachable local device logged as
  one line without traceback, reconnect backoff up to 60s

Claude-Session: https://claude.ai/code/session_01WvAyfgr3cJwkBsxTFpKF5P

Co-authored-by: Claude noreply@anthropic.com

v0.1.780

Compare Source

Bug Fixes

• wienernetze_smartmeter: Browser headers for log.wien login and login diagnostics
  (#​633,
  671612a)

• send browser like User-Agent/Accept headers in the log.wien login steps - error messages name the
  failing login step, the HTTP status and the message log.wien shows (e.g. invalid password,
  2FA/required action) - token errors include Keycloak's error_description - client logs each login
  step through the device logger (verbose 5), without query strings, codes or credentials

Claude-Session: https://claude.ai/code/session_01PSfi1tMioNAMzKV1Kzjtns

Co-authored-by: Claude noreply@anthropic.com

v0.1.779

Compare Source

Bug Fixes

• wienernetze_smartmeter: Adapt login and API to Wiener Netze changes
  (#​632,
  45f0af5)

• log.wien login with PKCE (S256) and two-step username/password form - authorization code parsed
  from the Location fragment - API keys and URLs from app-config.json instead of scraping JS bundles

  • API errors raise instead of returning None, re-login once on 401, token expiry tracked - state
    reading: online / login failed / connection error / update failed

Claude-Session: https://claude.ai/code/session_01PSfi1tMioNAMzKV1Kzjtns

Co-authored-by: Claude noreply@anthropic.com

v0.1.778

Compare Source

Bug Fixes

• bluetooth: Stop long discovery scans for unreachable pairing devices
  (#​629,
  ed18992)

A device that needs pairing but doesn't advertise was searched with three 60s classic+LE discovery
scans every 5 minutes while holding the shared Bluetooth lock, so other BLE devices couldn't
reconnect and the adapter (and the WiFi of Raspberry Pi combo chips) was busy ~40% of the time.

Pairing now does one LE-only 30s scan per attempt, reports connection 'not found' and backs off from
5 minutes up to 1 hour.

Claude-Session: https://claude.ai/code/session_01ScyUix2gXmfq81iGG4Pbjq

Co-authored-by: Claude noreply@anthropic.com

v0.1.777

Compare Source

Bug Fixes

• homekit: Wait for accessories that start after FHEM
  (#​628,
  8f24467)

The gateway gave up after the first failed connection and stayed in error state, e.g. when
Homebridge starts after FHEM. It now waits for aiohomekit's reconnect loop, which connects as soon
as zeroconf announces the accessory. Unpaired gateways keep waiting for discovery. Accessory
devices share the gateway connection.

Fixes #​625

v0.1.776

Compare Source

Bug Fixes

• mqtt_ha_discovery: Support full key names and skip non-config messages
  (#​627,
  680dd22)

Zigbee2MQTT and others send "device"/"state_topic" instead of the ESPHome abbreviations, which
failed with KeyError 'dev' (#​626). Discovery payloads are now normalized (abbreviations, ~ base
topic), topics without node_id and device based discovery are supported, empty/invalid payloads
are ignored.

readingList/setList used $EVENT, which became a literal backslash since CommandAttr quotes with
perlString; write $EVENT and repair existing entries. Light off command sent "on", brightness used
a wrong JSON key.

Claude-Session: https://claude.ai/code/session_01RiP2L62jYcnhU9vguQqitC

Co-authored-by: Claude noreply@anthropic.com

v0.1.775

Compare Source

Bug Fixes

• tibber: Clear message for invalid token and missing subscription
  (#​624,
  50e2b0c)

• invalid token: error log without traceback and state 'invalid token' - no home with an active
  subscription: warning and state, retried after the interval instead of IndexError - other
  connection errors at startup are retried after 60s - lock zipp 4.1.1 (CI install crashed when
  poetry downgraded zipp)

Refs #​620

v0.1.774

Compare Source

Bug Fixes

• esphome: Fixed MQTT client id for the Device Builder
  (#​623,
  ad9fccf)

esphome-device-builder connects to the MQTT broker of devices with mqtt: using
esphome-dashboard-, so FHEM's MQTT2_SERVER autocreated a new MQTT2_DEVICE on every
dashboard start. Start it through a small launcher which fixes the client id to
esphome-dashboard-fhempy-.

Claude-Session: https://claude.ai/code/session_012RxFkmnErti7mPUZApeSnK

Co-authored-by: Claude noreply@anthropic.com

v0.1.773

Compare Source

Bug Fixes

• homekit: Gateway state ready, no KeyError on pairing_data Attr
  (#​622,
  d2333d6)

• set_attr_pairing_data used the Attr message hash, which has no HOMEKIT_ID internal (KeyError on
  every startup); it now uses the device hash and only re-runs the setup if the pairing data changed

  • the gateway sets state connecting/ready/error, it stayed at 'fhempy server offline' after a
    reconnect

Refs #​620

v0.1.772

Compare Source

Bug Fixes

• Homekit zeroconf handler, miio update_functions and xiaomi_tokens QR login
  (#​621,
  9090047)

• homekit: zeroconf calls service handlers with keyword arguments, the handler parameter 'zc' raised
  TypeError on every mDNS packet (endless log) - miio: update_functions (e.g. info:60) failed with
  'argument of type NoneType is not iterable' because send_command got params=None - xiaomi_tokens:
  QR login passed bound methods to run_blocking, which only accepts functools.partial

Fixes #​620

v0.1.771

Compare Source

Features

• openmeteo_weather: Replace google_weather with Open-Meteo weather module
  (#​619,
  2295688)

Google search only returns weather data to browsers running JavaScript, so google_weather got no
data. The new module openmeteo_weather gets current weather and forecasts from Open-Meteo;
locations (names, addresses, LAT,LON) are resolved via Nominatim with Open-Meteo geocoding as
fallback. Readings are unchanged and google_weather stays as alias for existing devices.

v0.1.770

Compare Source

Bug Fixes

• Issues after updating from 0.1.755, new xiaomi_tokens login
  (#​618,
  61f5c48)

• BindingsIo: no uninitialized warning for queued messages without NAME - tuya_cloud/tuya_smartlife:
  pin paho-mqtt 1.6.1 (tuya SDKs use the paho 1.x API) - tuya: report Tuya cloud errors in log and
  state instead of KeyError 'result' - miio: retry failed update functions after 30s, quieter logs -
  pkg_installer: name the module when its manifest.json is missing - xiaomi_tokens: replace micloud
  login with captcha, email code (2FA) and QR login

Fixes #​613

v0.1.769

Compare Source

Bug Fixes

• Quote all values in FHEM commands as single quoted perl strings
  (#​616,
  a0e13e4)

Values in the perl commands sent to FHEM were inserted without escaping, partly into double quoted
strings that perl interpolates. Values coming from the network, e.g. zeroconf announcements
handled by discover_fhempy and discover_mdns, could therefore change the executed perl code. All
values, device and reading names are now passed as escaped single quoted strings and the zeroconf
discovery only accepts a valid ip address and port. getDeviceHashName had a perl syntax error and
works again.

Claude-Session: https://claude.ai/code/session_01LxBGTkhdnEhpLRGGyG1j9w

Co-authored-by: Claude noreply@anthropic.com

• homekit: Restore zeroconf browser needed by aiohomekit, update aiohomekit to 4.0.1
  (#​617,
  3473a5f)

#​536 removed the AsyncServiceBrowser together with its unused handler. aiohomekit doesn't browse by
itself, it attaches to an existing browser for _hap._tcp/_hap._udp, so Controller.async_start()
raised TransportNotSupportedError and no HomeKit device worked. The browser is created again with
a no-op handler; the controller is started only once. aiohomekit updated from 2.6.16 to 4.0.1.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.