-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: lumiOutageCountRestoreBindReporting sometimes stuck #7805
Merged
Conversation
This file contains 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
Koenkk
reviewed
Jul 27, 2024
Well I tried 3 times and could not trigger a failure (of course I can't when I want one)... at least the restoring is still working :)
|
Seems good, outage count of device + db match and there has been no repeat attempts to restore binds.
Good to go in. |
thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed I was getting bind errors over and over again, due to timeouts.
There seems to have been some changes in zh, maybe in the past these did not propagate properly to zhc?
When the device recovers from a power outage (aka sometimes battery voltages dips when for example it refreshes the eInk display. We try and restore the bind/reporting settings, generally the device is awake for a bit after this happens before going to sleep.
If we somehow end up hitting a timeout,
meta.outageCount
was never updates because the bind and/or reporting hit an error. So we try again every message we get, but on a normal message the device does not seem to be awake for long to finish all the bind/reporting restores. So we end up where we started.We can 'avoid' this by updating
meta.outageCount
first and adding atry {} catch {}
around the bind/reporting restores.This seems to be doing OK for the 2 power outages I triggered. Will monitor for a few days.