LAN discovery now works — and reaches other subnets/VLANs (#57)
Fixed
- LAN discovery returned 0 devices. Govee devices send their scan reply as multicast to
239.255.255.250:4002, not unicast to the sender, so the listener must join the multicast group (IP_ADD_MEMBERSHIP) — otherwise the kernel drops every reply (device_count: 0, error: null). The diagnostics scan now joins the group on each enabled interface plus the default route, co-binds port 4002 (SO_REUSEADDR/SO_REUSEPORT) alongside other LAN tools, and emits the scan out every NIC for multi-homed hosts.
Added
-
"LAN device addresses / subnets" option (Options → advanced) for LAN-enabled devices on a different subnet/VLAN than Home Assistant, which a local multicast scan can't reach. Accepts a comma-separated list of:
- device IPs —
10.20.0.51 - broadcast addresses —
10.20.0.255 - CIDR subnets (≤ /24) —
10.20.0.0/24, unicast-swept since inter-VLAN firewalls usually drop directed broadcast
The scan is sent to each target; devices reply unicast back across the VLAN. Validated in the options form.
- device IPs —
-
Richer diagnostics: the
lan_discoveryblock now reports the enabled interface classes (e.g. flags a container-bridge source IP that can't reach the LAN) and the configured-target count — without leaking host IPs or the raw option.
How to use (testers on #57)
- Update to v2026.6.15, restart HA.
- If your Govee devices share HA's network, just re-download diagnostics — they should now appear.
- If they're on another VLAN/subnet: Settings → Govee Cloud Integration → ⋮ → Configure → enter that subnet (e.g.
10.20.30.0/24) or the device IPs in LAN device addresses / subnets, then re-download diagnostics.