feat(coordinator): add 60s polling fallback for MQTT push - #2
Merged
Conversation
The integration is push-only: the DataUpdateCoordinator had no update_interval, so state relied entirely on the AWS IoT MQTT subscription. That subscription can silently stall (observed on HA 2026.6.1: connection alive but SUBSCRIBE never ACKed, watchdog unable to recover without a full restart), leaving entity state frozen until a manual restart. Add an update_method that refreshes each appliance over REST via pyhon's appliance.update(), on a 60s interval. Push stays the primary fast path; polling bounds staleness and keeps state usable when push is dead — restoring the resilience the old cloud_polling integration had. Also pass config_entry=entry to the coordinator (silently ignored pre-2026.8, required from 2026.8 — avoids a future breakage). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The integration is push-only: the DataUpdateCoordinator had no update_interval, so state relied entirely on the AWS IoT MQTT subscription. That subscription can silently stall (observed on HA 2026.6.1: connection alive but SUBSCRIBE never ACKed, watchdog unable to recover without a full restart), leaving entity state frozen until a manual restart.
Add an update_method that refreshes each appliance over REST via pyhon's appliance.update(), on a 60s interval. Push stays the primary fast path; polling bounds staleness and keeps state usable when push is dead — restoring the resilience the old cloud_polling integration had.
Also pass config_entry=entry to the coordinator (silently ignored pre-2026.8, required from 2026.8 — avoids a future breakage).