Closed andreibanaru closed 5 years ago
The hub is set to 60 seconds and the platform will get the same data within that timeframe.
Can MIN_TIME_BETWEEN_UPDATES be overridden?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍
This issue wasn't really addressed. 60s is a very slow poll time and given the time critical nature of actions when responding to a power out it would be good to be able to change the frequency. Would there be any downside to having it as a default 10s or user configurable? Not sure if this can be reopened as the original user described it well or if i need to raise a new issue. Thanks
I agree a parameter or 10s or 15s default would be nice
Home Assistant release with the issue:
0.72.1
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/components/sensor.apcupsd/
Description of problem:
scan_interval doesn't work with sensor.apcupsd.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: