fix: back off failed cleaning history fetches#1606
Open
Komzpa wants to merge 1 commit into
Open
Conversation
Komzpa
force-pushed
the
codex/cleaning-history-cloud-backoff
branch
from
77fa5ee to
a1e1609
Compare
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.
Summary
Context
On a live Home Assistant instance, an idle X20+ repeatedly logged failures from
sg.api.io.mi.com/app/user/get_user_device_data(Read timed outandConnection reset by peer). Dreame debug showed the vacuum was otherwise healthy and still polling device state every ~10s, so this only backs off the optional cleaning-history fetch after a cloud failure.Validation
python3 -m py_compile custom_components/dreame_vacuum/dreame/device.pygit diff --check