Skip to content

v2.0.26 — HA setup.xml namespace fix, Discover-now docs, 60s default timeout

Choose a tag to compare

View all tags
@K0rb3nD4ll4S K0rb3nD4ll4S released this 13 May 02:24
· 23 commits to main since this release
v2.0.26
91f5edd

Fix: HA integration now actually registers discovered Wemos as entities

After v2.0.23/.24 got SSDP working in the HAOS VM (9 locations returned), the integration still showed zero entities. Cause: setup.xml was being fetched and XML-parsed successfully, but every field lookup returned an empty string — including UDN, which is used as the unique key. Devices without a UDN were silently dropped, so the coordinator started with 0 devices and no switch entities were registered.

Root cause: Wemo's setup.xml declares xmlns="urn:Belkin:device-1-0", not the UPnP standard urn:schemas-upnp-org:device-1-0 that the parser was looking up. Every find(".//d:UDN", ns) returned None.

What changed

  • custom_components/dibby_wemo/wemo_client.py — _fetch_setup_xml_sync now matches tags via the {*} wildcard namespace (Python 3.8+), so any namespace Belkin's firmware uses (current or future) resolves correctly.
  • Warning-level log when setup.xml parses but UDN is empty.
  • New summary log on every scan: discover_devices: N raw -> M device(s) (failed_fetch=…, missing_udn=…, duplicates=…).
  • async_setup_entry now logs the device list handed to the coordinator.

Tweak — default discovery timeout raised 10 → 60 s

DEFAULT_DISCOVERY_TIMEOUT_S in const.py bumped to give the SSDP scan + unicast subnet sweep enough budget on busy LANs and multi-/24 setups. Existing installs keep their saved value.

Docs — README rewrite

  • "Remove HA's built-in wemo integration" is now a numbered Step 1 prerequisite above the HACS install steps, with the consequences of running both spelled out (duplicate entities, racing pollers, discovery hijack).
  • New section "Adding more Wemos later — the Discover devices now button" walks through the seven-step Configure flow for picking up new Wemos without restarting Home Assistant.

Upgrade

  • HACS: ⋮ → Reload data → Dibby Wemo → ⋮ → Redownload → 2.0.26 → restart HA
  • Homebridge: npm install -g homebridge-dibby-wemo@2.0.26
  • Node-RED: npm install -g node-red-contrib-dibby-wemo@2.0.26
Assets 4
Loading