LAN fix — connectivity no longer flaps off when a device is turned on (#57)
Fixes a bug in the new LAN transport reported by testers on v2026.6.21: a device's LAN connectivity sensor would flip to Disconnected the moment the device was turned on, and subsequent commands would silently move to the cloud ("report separately").
Cause: a single verify-by-read confirm miss flipped the whole LAN transport unavailable with no tolerance. A freshly-powered Govee WiFi controller often can't answer the local status read within the 0.5s confirm window (or briefly still reports its old state), so a normal power-on looked like a LAN failure.
Fix: LAN write-confirm misses now use the same 3-strike hysteresis the read path already had — a transient power-on miss no longer marks LAN down, and a successful local read resets the counter. Commands still fall through LAN → MQTT → REST on every miss (nothing is ever stranded), and a genuinely unreachable device still demotes.
No action needed — update via HACS. If LAN still drops for you, please share a fresh diagnostics download on #57 (the transport_health.lan.last_failure_reason field tells us exactly what's happening).
Full changelog: v2026.6.21...v2026.6.22