Native API heartbeat that works on new firmware, plus crash and naming fixes
What's new
- "Log in to the Native API during the heartbeat" setting (on by default). Starting with ESPHome 2026.10, the GDO blaQ only counts a logged-in Native API client as connected, so the old connect-only heartbeat no longer stopped the reboot every 15 minutes. The heartbeat now keeps a real, logged-in session open. Turn the setting off to go back to the connect-only heartbeat.
What's fixed
- No more crashes when port 6053 is unreachable (#12). If the Native API is disabled in your blaQ firmware, the plugin logs one warning suggesting you turn the heartbeat off, instead of crashing Homebridge.
- The Display Name from your config now shows in the Home app (#10), instead of the device's own name (e.g. "GDO blaQ e2e0e4"). A name typed in the config also takes priority over the auto-discovered name. The Home app may keep the old name until you rename the tile or remove the cached accessory.
- Quieter logs during device reboots (#11). "EventSource got error" is now a warning, not an error, once the connection has worked before. The plugin reconnects on its own.
Do you need to change anything?
- Native API on (default firmware): keep the Native API heartbeat setting on. If you had it off and saw the blaQ reboot every 15 minutes, turn it on.
- Native API disabled in firmware: turn the Native API heartbeat setting off.
Full Changelog: V0.4.1...V0.4.2