v0.7.0-rc1
Pre-releaseRelease candidate for 0.7.0. Install through HACS → Redownload → Show beta versions, restart Home Assistant, then run the four checks below. Tag the final only if all four pass.
Five commits, all from one night's failures on a real network. Full detail in the changelog and in PR #21.
What to check, and what a failure looks like
1 — The first click after a restart is fast. With keepalive_seconds: 0, restart Home Assistant, wait for the lamp to become available, then toggle it. It should act immediately.
Failure is visible as: a multi-second pause before the lamp moves — the startup probe released the link instead of keeping it, which is the old behaviour this release removes.
2 — A timed keep-alive still releases the link. Set keepalive_seconds to something small (30), restart, toggle the lamp, then leave it alone past the timeout and confirm the vendor app can still take the lamp.
Failure is silent, and this is the check worth the most: if the link is now held for a timed keep-alive too, nothing in any log says so — you only find out because the vendor app can no longer connect. That option exists precisely to hand the lamp's single slot back.
3 — Availability survives a Home Assistant shutdown. Restart Home Assistant and read the log during the CLOSE stage.
Failure is visible as: reconnection attempts, or Insufficient authorization, logged while the core is already shutting down — the watchdog chasing a link nobody wants back.
4 — Colour temperature and brightness still round-trip. Change both from the vendor app or a wall remote and confirm Home Assistant follows.
Failure is visible as: Home Assistant showing the value it last sent rather than the lamp's own. Nothing here should touch that path, which is why it is worth confirming it did not.
Known gap in this candidate
One behaviour has never been observed live: recovery from a permanent link lost while availability still reads true — the probe on the fast interval plus the next advert triggering a connect. No link has dropped outside a restart on the author's network since 2026-09-04, so that path is covered by tests only. It cannot be forced on demand; if a drop happens while this rc is installed, that is the observation the final release wants.
Everything else has been running on the author's Home Assistant since 2026-09-04 19:47: two restarts recovering the proxy in about a second, one cold start with no proxy in reach recovering in 28 seconds, keepalive_seconds: 0 throughout, no errors.