Lovelace frontend appears to lockup after upgrading to 0.111.3+

I’m running HASSIO on a raspberry pi. Since upgrading to 0.111.3 (and now running 0.111.4), my frontend appears to lockup about once per day. If I try to toggle switches, etc., they switch for a moment then switch back. Google assistant says that “{GA Home Name} is not available right now” when trying voice commands. I can still login via SSH and running ha core logs, the logs are filled with these kinds of lines:

2020-06-21 12:19:37 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:10
2020-06-21 12:19:37 WARNING (MainThread) [homeassistant.components.media_player] Updating yamaha media_player took longer than the scheduled update interval 0:00:10
2020-06-21 12:19:40 WARNING (MainThread) [homeassistant.components.weather] Updating darksky weather took longer than the scheduled update interval 0:00:30
2020-06-21 12:19:40 WARNING (MainThread) [homeassistant.components.weather] Updating openweathermap weather took longer than the scheduled update interval 0:00:30
2020-06-21 12:19:44 WARNING (MainThread) [homeassistant.components.sensor] Updating blink sensor took longer than the scheduled update interval 0:00:30
2020-06-21 12:19:44 WARNING (MainThread) [homeassistant.components.climate] Updating badnest climate took longer than the schedule

There’s these log entries for what looks like just about every component in the front end.

I have to restart home assistant using ha core restart and then everything is back to normal and it appears no state was lost during this phase. It doesn’t seem to lockup at any specific time but happens about once a day.

I’m running the Mariadb add-on for my state and event hstory.

1 Like

This problem is happening also to me. Same behaviour. I’ve noticed this after installed version 0.111.4

Create an issue on github. Attach logs when the warnings first appear. Make sure to grab a few hundred log lines prior to the first warning.

@petro, is there a way to get more log lines from the command line? When I do a “ha core logs” command, it appears to give me a certain, limited number of lines from the log, but not what I can usually get from the front end developer tools.

just look at the whole file, it will be located in your config directory

Doh! Got it.

The problem just happened again, but I didn’t realize the log gets reset after a restart. When it happens next time, I’ll grab the log entries before the restart and create the issue.

You could also post it here. It might be fixable or unrelated to the frontend.