Open Saentist opened 1 year ago
Given that I'm winding down support for this integration I'm not going to spend time trying to work out how to do this. There is the ability to disable the polling altogether and then set up an automation to only poll when you want, so people can use that instead. I'll leave this ticket open for now but when the new Grott integration takes over I'll be closing anything that isn't essential in this repo.
Given that I'm winding down support for this integration I'm not going to spend time trying to work out how to do this. There is the ability to disable the polling altogether and then set up an automation to only poll when you want, so people can use that instead. I'll leave this ticket open for now but when the new Grott integration takes over I'll be closing anything that isn't essential in this repo.
Hi Muppet,
How can I disable the polling? And can you tell how I can set up an automation to poll the data?
Cheers, Pieter
This is how you can set up an automation to poll the data (copied from my old HA automation for it):
What I remember how to disable polling I'll post it here.
This is how you can set up an automation to poll the data (copied from my old HA automation for it):
What I remember how to disable polling I'll post it here.
Thanks Muppet!
Please let me know how I can disable polling.
FYI I did a little more digging, I'm not 100% certain, but I think the above screenshot that I posted also overrides the default polling interval, so you don't need to disable polling directly (I might be wrong though)
FYI I did a little more digging, I'm not 100% certain, but I think the above screenshot that I posted also overrides the default polling interval, so you don't need to disable polling directly (I might be wrong though)
Thanks!
I think I found it in the code, there is:
SCAN_INTERVAL = datetime.timedelta(minutes=5) THROTTLE = datetime.timedelta(minutes=1)
I can set the scan_interval to more minutes. I hope this fixes my to much API requests. I only don't understand what Throttle means.
You don't need to change anything there at all.
There's some nice documentation on it here for the ping integration: https://www.home-assistant.io/integrations/ping/
You can just do exactly the same for this integration, no need to go tweaking the code
You don't need to change anything there at all.
There's some nice documentation on it here for the ping integration: https://www.home-assistant.io/integrations/ping/
You can just do exactly the same for this integration, no need to go tweaking the code
Ah it will override the default, didn't know. Thanks again.
No, it won't override the default, that's what disabling polling does. Then the automation polls only at the frequency you require.
No, it won't override the default, that's what disabling polling does. Then the automation polls only at the frequency you require.
I see it now, it will disable the default polling..
Is your feature request related to a problem? Please describe. Let's reduce cloud ban, by set fixed data get time.
Describe the solution you'd like On integration install time to be created hard set time with will not allow to get data "Before" next scheduled time frame, no mater system restarted, rebooted or integration reloaded etc.
Describe alternatives you've considered Example" Install and configured time: 15:24h next pool time : +60min (or any other acceptable time in configuration 2h 3h etc.) If reboot, hard No to take data until next allowed time frame.
Additional context This solution is 100% needed to avoid "cloud ban" If possible to see somewhere in integration to have: countdown clock to the next data pool