please help constant issues with 0.60 Hassbian
imputations stop working overall system lag
no issues on older versions of hassio.
Turns out alot of my issues are being cause by all my automatons stopping working even after rebooting system.
I am having to manually restart the automation’s service via Hass UI only thing i can see in logs is lots of Timer got out of sync errors as per below .
2017-12-29 03:31:52 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=9 from 2017-12-29 03:23:09.933090)
2017-12-29 03:32:08 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.
2017-12-29 03:32:08 WARNING (MainThread) [homeassistant.setup] Setup of sensor is taking over 10 seconds.
2017-12-29 03:32:08 WARNING (MainThread) [homeassistant.setup] Setup of binary_sensor is taking over 10 seconds.
2017-12-29 03:32:08 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
2017-12-29 03:32:08 WARNING (MainThread) [homeassistant.setup] Setup of alarm_control_panel is taking over 10 seconds.
2017-12-29 03:32:08 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds.
2017-12-29 03:32:19 WARNING (MainThread) [homeassistant.setup] Setup of remote is taking over 10 seconds.
2017-12-29 03:32:54 WARNING (MainThread) [homeassistant.components.media_player] Setup of platform cast is taking over 10 seconds.
2017-12-29 03:33:27 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-12-29 03:33:35 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-12-29 04:13:40 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-12-29 05:02:43 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-12-29 05:08:50 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-12-29 05:09:10 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
Hi wouldn’t the initial_state thing be default to True anyway. Also I normally just do full reboots and issue still happens .
I’ve never had to add initial_state to my automations before but I have recently upgraded to Hassbian 0.60 form a older version maybe 0.53 or something talk about frustrating The time errors in log seem to effect my autiomations especially ones that have sun states or time involved basically effects all of them and over all system lag maybe my Pi 3 is not powerful enough for HASS
also experiencing lag! I disabled all automations and still when playing/pauzing kodi in home assistant it takes a good 2 to 3 seconds, it used to be nearly instant.
Yeah I’ve just done multiple fresh installs after Home Assistant comes online check the logs and even with fresh install nothing installed default settings/untouched multiple timer out of sync errors this is with Hassbian 0.60
Roll HA back. 0.60 is buggy and I’m yet to see a real fix that can be made by end users. Some core component is just chewing up 100% of the CPU as I’ve seen people even claim this happens on a fresh install with no configuration. I went back to 0.56.2 and I have no problems.
I was on 0.50.2 before upgrading to 0.60 and then had this problem even though I made no configuration changes. I rolled back to 0.59 and it didn’t fix my problems and others reported the same happened as far back as 0.57.
Is it possible to downgrade HASS in Hassbian 0.60 image
Or do I need to download a new Hassbian image would you have a link as I couldn’t seem to find it on github thanks or do i do something like this below
I’m seeing this issue showing up in 0.62, but no CPU usage although it’s effecting my zha components, which I can no longer trigger until I restart hass. Not sure if this is a coincidence.
Just like to say, I’m seeing this as well in 0.62 (and before). Thought it was related to SNMP but I disabled that and it persists:
2018-01-28 19:29:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.water_heater is taking over 10 seconds
2018-01-28 19:34:04 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.water_heater is taking over 10 seconds
2018-01-28 19:37:07 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-28 19:37:14 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-28 19:37:41 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-28 19:37:41 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.rhomeautomation_subsribers is taking over 10 seconds
2018-01-28 19:37:56 WARNING (MainThread) [homeassistant.components.sensor] Updating darksky sensor took longer than the scheduled update interval 0:00:30
2018-01-28 19:37:56 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-28 19:37:56 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.dark_sky_daily_high_apparent_temperature_4 is taking over 10 seconds
2018-01-28 19:37:58 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-28 19:38:58 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-28 19:39:23 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.water_heater is taking over 10 seconds
2018-01-28 19:39:23 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-28 19:44:13 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.water_heater is taking over 10 seconds
You get the error even on a fresh install without anything installed or changes made ,
although it’s a lot less errors on fresh install I had huge amount of errors so brought a second PI and use that for MQTT and python scripts leave my other PI for just HASS alone . Still get errors but only one or two not pages of them . I believe HASS has out grown the PI and its caused by either memory or cpu being under powered but that’s a guess as I haven’t run any hardware monitor stuff as yet
I’m also experiencing lots of timer out of sync errors since 0.60 or so. At first I thought it was because I’m using history_graphs since then but appearently it’s not related. I have to reboot way more often then before too ensure Hass will not get unresponsive.