You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to 0.112.0, I manually configured the speedtestdotnet integration via UI and removed it from configuration.yaml. Since I want to control it myself, I checked the box "disable auto update" and put 0 as update frequency.
After I've restarted, I noticed extreme cpu usage and saw that the speedtests are done multiple times a minute, so I assume the check-box "disable auto update" gets ignored after a restart. When I go to the integrations' option and hit submit (without changing the options), it works as expected and the cpu usage is back to normal - but only until the next restart.
Environment
Home Assistant Core release with the issue: 0.112.0
Last working Home Assistant Core release (if known): probably none, as UI configuration is new in 0.112.0 - but it worked fine with yaml configuration on 0.111.4
Hey there @rohankapoorcom, @engrbm87, mind taking a look at this issue as its been labeled with an integration (speedtestdotnet) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)
Hello guys, thank you very much for the quick reaction! I just updated to 0.112.3, but unfortunately the problem is still there (tests every ~15 sec, with auto-updates disabled). May I please ask you to have a look at it again?
The problem
After upgrading to 0.112.0, I manually configured the speedtestdotnet integration via UI and removed it from configuration.yaml. Since I want to control it myself, I checked the box "disable auto update" and put 0 as update frequency.
After I've restarted, I noticed extreme cpu usage and saw that the speedtests are done multiple times a minute, so I assume the check-box "disable auto update" gets ignored after a restart. When I go to the integrations' option and hit submit (without changing the options), it works as expected and the cpu usage is back to normal - but only until the next restart.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: