Anybody else experiencing an overall slowdown of the Home Assistant, mostly noticeable on the lovelace interface?
I’ve been noticing that roughly 4 hours after a restart the Home Assistant starts to slow down, the lovelace interface takes a long while to load and sometimes some sections don’t even load at all. The automations go out of sync and those that are triggered in short time intervals (like every 10 seconds) start to overlap.
When I go into the templates screen to test and it takes about 3 to 5 seconds for any changes to the template to resolve.
I also start noticing a lot of warnings in the home-assistant log:
2020-07-29 13:34:34 WARNING (MainThread) [homeassistant.components.automation] Kitchen Motion Daylight Automation: Already running
2020-07-29 13:34:36 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2020-07-29 13:34:40 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
2020-07-29 13:34:42 ERROR (zeroconf-Engine-5445) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiopylgtv/webos_client.py", line 373, in consumer_handler
while not closeout_task.done():
UnboundLocalError: local variable 'closeout_task' referenced before assignment
2020-07-29 13:35:21 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
2020-07-29 13:35:28 ERROR (MainThread) [homeassistant.components.upnp] Timeout fetching Internet Home Gateway Device data
2020-07-29 13:35:31 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
2020-07-29 13:36:03 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
The more time elapses the worse the slowdown gets
2020-07-29 15:15:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.monitor_del_servidor_http_interno is taking over 10 seconds
2020-07-29 15:15:02 WARNING (MainThread) [homeassistant.helpers.entity] Update of calendar.family_calendar_importants is taking over 10 seconds
2020-07-29 15:15:06 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.solar_production is taking over 10 seconds
2020-07-29 15:15:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.wol_nas is taking over 10 seconds
2020-07-29 15:15:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of weather.openweathermap is taking over 10 seconds
2020-07-29 15:15:09 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.cama_de_la_recamara_principal is taking over 10 seconds
2020-07-29 15:15:09 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.spotify_totoromty is taking over 10 seconds
2020-07-29 15:15:11 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.cpu is taking over 10 seconds
2020-07-29 15:15:11 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.processor_use is taking over 10 seconds
2020-07-29 15:15:16 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
2020-07-29 15:15:17 WARNING (MainThread) [homeassistant.components.automation] timeout ticker: Already running
2020-07-29 15:15:17 WARNING (MainThread) [homeassistant.components.sensor] Updating command_line sensor took longer than the scheduled update interval 0:01:00
2020-07-29 15:15:17 WARNING (MainThread) [homeassistant.components.calendar] Updating google calendar took longer than the scheduled update interval 0:01:00
2020-07-29 15:15:18 WARNING (MainThread) [homeassistant.components.sensor] Updating rest sensor took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:18 WARNING (MainThread) [homeassistant.components.switch] Updating wake_on_lan switch took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:18 WARNING (MainThread) [homeassistant.components.weather] Updating openweathermap weather took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:19 WARNING (MainThread) [homeassistant.components.light] Updating flux_led light took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:19 WARNING (MainThread) [homeassistant.components.media_player] Updating spotify media_player took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:20 WARNING (MainThread) [homeassistant.components.sensor] Updating ios sensor took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:20 WARNING (MainThread) [homeassistant.components.sensor] Updating cpuspeed sensor took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:21 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
The reason I went for this is that it has 8 relay channels and 4 analog temperature inputs and wired network connection. I use it to control my heating and ventilation system and wanted it to be all hard wired. I’m a sparky so didn’t mind having to pull a few wires around the place.
I never intended it to be able to take a switch input but that was just an added bonus!
I only have one switch being polled on it.
This being said I’ve got a wi fi dimmer on the way so it will probably become redundant soon!
Yes, I have spotcast on its latest version (3.3.5) both configured and running in my Home Assistant, but never experienced a slowdown issue with it until 0.113.
On 0.113 while running the top command on the host I noticed that python3 kept going through the roof, eating over 150% CPU and Time+ going over 300:xx.0 sending the 15 minute load average around 15.x, when on 0.112.x CPU usually remained below 15%.
I read on the opened issues you mention that spotcast has been spotted as a possible related factor. Hopefully it will get fixed with 35943 or a spotcast update.
take care you prepare your configuration.yaml before upgrading, remove name field and add a # with the orignal name.
upgrade
go to entities and search on the rfx id’s in your configuration.yaml, you will find them and then you can rename them to the original names so all your automations etc will work again without modifying.
trying to work out the already reported issues with google tts notifications, I now notice all my notify.notify services stopped working after updating to 113.2.
this is in the log if I issue a service manually from the developer-tools/service
2020-07-30 17:56:28 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
2020-07-30 17:56:29 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
2020-07-30 17:56:30 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
2020-07-30 17:56:30 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
which is silly because notify.notify has nothing to do with my registered mobile apps, and I am not issuing that command in the first place…
so, checking that in the services page, I now am scattered to see none of these mobile_app services work either…?
hope I am not alone…
is this a(nother) bug?
ha core update --version 0.113.1
restores the earlier mentioned tts %20 issue, but I still have issues with the services page using notify.notify and other notification groups. Pushbullet still works fine, the others give the posted error still
o I’ve missed that, sorry. Thanks for the link, this is a major bummer…
coming to think of it, Ive also updated the iOS app yesterday. Hope this isnt a chain of issues ;-(
update
found my older iPhone and iPad and they did receive the notifications…is it the new app then after all?
I was able to update last night but for some reason I can’t log in when using my normal Firefox session. If I open it in Firefox’s Incognito Mode, I can log in fine. If I use Chrome, it also works fine.
When I log in through the regular session I get 400 errors for the /token endpoint and there’s errors in the JS console.
Uncaught (in promise) TypeError: u.addEventListener is not a function
e core.a99cac39.js:1
o core.a99cac39.js:1
o core.a99cac39.js:1
o core.a99cac39.js:1
hassConnection core.a99cac39.js:1
promise callback*196 core.a99cac39.js:1
I cleared the entire cache and also tried by using Firefox in safe mode and it still doesn’t work. Not sure why Incognito would work fine though.
Update to this issue: I forced Firefox to start in Safe Mode, and was able to get back in with my regular browser session. The Firefox extension I had installed (WebSocketSniffer) was messing up the websocket connection.
Just commenting to say, you guys are awesome! I just got around to checking out the 113 notes and the automation & scripts updates are much, much appreciated. As someone who’s innermost thoughts are comprised of about 50% functional programming code, having the ability to do loops and if/else syntax makes writing up new automations SO MUCH EASIER. I’ve only been messing with HA for about 4 months now and the progress I’ve seen just in that time is unreal, and well worth my support (through HA Cloud subscription).
so are most people on the new iPhone App… check this for development of the issue and hopefully quick fix
for now, resetting your push_id in the app settings makes the notifications work again (though no promises are made for how long)
So still a chance to get it fixed actually…