2026.4.4
Reduce data update frequency to at least one second
As mentioned in #135 the WebSocket can create some states to change very frequent (technically every 300ms) and this could overload your HA states db (details can be found in #135). With this new release the integration makes sure, that the minimum data update interval (no matter how fast data arrives via the WebSocket) will be one second.
Additional configuration setting
If you enable the new Apply 'Polling Interval' also to WebSocket updates option, the sensors will only be updated at the configured update interval - even when used the WebSocket connection.
E.g. when you have selected 10sec for the polling-data-from-your-goe-device, then the data in HA will be also updated (just) every 10 seconds, even if the integration has received multiple updates via the established WebSocket connection. Of course only the latest data will be populated to your HA .
Completed migration to CoordinatorEntities
I have fully transitioned the integrations DataUpdateCoordinator to utilize the CoordinatorEntity pattern. As part of this update, all "classic" polling logic—specifically individual async_update methods within each entity—has been completely removed.
Key Improvements:
- State Consistency: All entities update simultaneously as soon as the coordinator receives new data, ensuring a unified state across the dashboard.
- Modern Standards: By removing legacy polling logic from individual sensors, the codebase is now cleaner, more maintainable, and fully aligned with current Home Assistant Best Practices.
Please consider supporting me
Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.
