-
-
Notifications
You must be signed in to change notification settings - Fork 34.2k
Constant polling for Husqvarna Automower #147957
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
base: dev
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add tests for it?
So we make sure that the timer will not bet reseted even in the future
I've marked this PR a draft, as changes are requested that need to be processed. Thanks! 👍 ../Frenck |
Thank you |
Well they are not passing 😬 |
They were flakey. But now they work 👍 |
Breaking change
Proposed change
The built-in implementation of the update coordinator resets the polling timer on every websocket update. Since websockets do not deliver all required data (e.g. statistics or work area details), we enforce a constant REST polling cadence by overwriting the built
async_set_updated_data
method of the coordinator.Please include in next patch release.
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
.To help with the load of incoming pull requests: