Skip to content
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

Catch all health connect exceptions so we dont crash #4830

Merged
merged 3 commits into from
Nov 19, 2024

Conversation

dshokouhi
Copy link
Member

Summary

Fixes: #4829 by catching the exceptions so the app does not crash

Screenshots

data is still good

image

Link to pull request in Documentation repository

Documentation: home-assistant/companion.home-assistant#

Any other notes

Copy link
Member

@jpelgrom jpelgrom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rate limiting does pose an interesting question as we add more sensors: should this somehow be exposed / allow the user to limit update frequency for HC independently?

@dshokouhi
Copy link
Member Author

should this somehow be exposed / allow the user to limit update frequency for HC independently?

feels like lots of others will request independent updates, ideally all users will have foreground reads here i think

@dshokouhi dshokouhi merged commit a918482 into home-assistant:master Nov 19, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Crash caused by Health Connect rate limiting
2 participants