🧪 2.11.0 Beta 7
Push connections: back to frequent reconnects
Beta 6 made the periodic reconnect really happen every 30 minutes, as intended. In practice that made pushes worse: on a Xenio the cloud delivered pushes only during the first 12–14 minutes of each connection. After that, keep-alives kept arriving, but no measurements or state changes until the next reconnect. Temperature, heater on/off and the other values then came only from the 5-minute poll. The roughly 6-minute reconnects of Beta 1–5 (the result of a counting bug) had kept the pushes flowing without anyone noticing.
- The push connections now reconnect every 5 minutes again. Since Beta 6 a reconnect takes a fraction of a second instead of 10 seconds, so the gap in which a message could be lost stays tiny.
- On Xenio, a "subscription completed" message from the cloud now triggers an immediate reconnect, as it already did on Fenix. Until now it was ignored.
- With debug logging enabled, each incoming Xenio message is now logged with its feed, which makes push gaps visible in the log.
- On Fenix, the "subscription registered and active" line is now logged at debug level instead of info, so the more frequent reconnects don't fill the log.
Everything from Beta 1–6 is included — including the note on automations that use Power (Xenio).
This is a pre-release. Enable "Show beta versions" for the integration in HACS to test it.