how do you do this as i i didn’t enable it maybe happened automatically as i do have a google home on the network. but I can not find any entries in my configuration any ideas thanks
Again, I’m running an intel atom Ubuntu server and I have the same problem in 0.60 and I did disable Chromecast and it made no difference.
Edit: just realized it was a different thread about this problem that I said I was running Ubuntu on a micro itx board.
Looking at the timing again, it probably isn’t related to the ‘Timer out of sync’ messages - (Although personally I think a possible leak of personal information to google is probably more important, so I would want to know what is happening).
The next thing to check is to see if the messages relate to anything in the system logs to correlate. try
$ journalctl
and see if any messages occur at the same time as the error message.
On my Pi, it is influxdb compressing its database that causes ‘Timer out of sync’ messages.
1 Like
I am getting timer out of sync always when time is around 12:15 no matter AM PM ( both time)
i was getting this error when i open history or logbook,
But i created history_graph and removed it from history and also i have set hours to show to 6 error was gone, now its ok when i open history no error,
but i am gettig this error on fix time as i mentioned it above at around 12:15 AM/PM
i have set my local time to +5:30
Please guide me to solve this error
thanks
2018-01-03 09:41:11 DEBUG (Recorder) [homeassistant.components.recorder] Connected to recorder database
2018-01-03 09:41:13 DEBUG (Thread-16) [homeassistant.components.recorder.util] converting 19 rows to native objects took 0.137067s
2018-01-03 10:41:16 INFO (MainThread) [homeassistant.components.updater] Submitted analytics to Home Assistant servers. Information submitted includes {}
2018-01-03 12:20:56 DEBUG (Thread-20) [homeassistant.components.recorder.util] converting 24 rows to native objects took 0.062880s
2018-01-03 12:20:56 DEBUG (Thread-20) [homeassistant.components.history] get_significant_states took 0.082854s
2018-01-03 12:20:57 DEBUG (Thread-20) [homeassistant.components.recorder.util] converting 8 rows to native objects took 0.201521s
2018-01-03 12:20:57 DEBUG (Thread-20) [homeassistant.components.history] getting 8 first datapoints took 0.257204s
2018-01-03 12:20:57 DEBUG (MainThread) [homeassistant.components.history] Extracted 32 states in 0.352189s
2018-01-03 15:11:05 DEBUG (Thread-19) [homeassistant.components.recorder.util] converting 24 rows to native objects took 0.028418s
2018-01-03 15:11:05 DEBUG (Thread-19) [homeassistant.components.history] get_significant_states took 0.038126s
2018-01-03 15:11:05 DEBUG (Thread-19) [homeassistant.components.recorder.util] converting 8 rows to native objects took 0.156601s
2018-01-03 15:11:05 DEBUG (Thread-19) [homeassistant.components.history] getting 8 first datapoints took 0.207522s
2018-01-03 15:11:05 DEBUG (MainThread) [homeassistant.components.history] Extracted 32 states in 0.265904s
2018-01-03 15:11:40 DEBUG (Thread-17) [homeassistant.components.recorder.util] converting 24 rows to native objects took 0.059207s
2018-01-03 15:11:40 DEBUG (Thread-17) [homeassistant.components.history] get_significant_states took 0.078676s
2018-01-03 15:11:40 DEBUG (Thread-17) [homeassistant.components.recorder.util] converting 8 rows to native objects took 0.166490s
2018-01-03 15:11:40 DEBUG (Thread-17) [homeassistant.components.history] getting 8 first datapoints took 0.224782s
2018-01-03 15:11:40 DEBUG (MainThread) [homeassistant.components.history] Extracted 32 states in 0.315535s
2018-01-03 16:59:38 DEBUG (Thread-8) [homeassistant.components.recorder.util] converting 1591 rows to native objects took 1.765564s
2018-01-03 16:59:38 DEBUG (Thread-8) [homeassistant.components.history] get_significant_states took 1.779682s
2018-01-03 16:59:38 DEBUG (Thread-8) [homeassistant.components.recorder.util] converting 5 rows to native objects took 0.030725s
2018-01-03 16:59:38 DEBUG (Thread-8) [homeassistant.components.history] getting 5 first datapoints took 0.046118s
2018-01-03 16:59:38 DEBUG (MainThread) [homeassistant.components.history] Extracted 1596 states in 1.864406s
2018-01-03 17:46:09 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-01-03 22:07:42 DEBUG (Thread-10) [homeassistant.components.recorder.util] converting 24 rows to native objects took 0.024855s
2018-01-03 22:07:42 DEBUG (Thread-10) [homeassistant.components.history] get_significant_states took 0.036161s
2018-01-03 22:07:42 DEBUG (Thread-10) [homeassistant.components.recorder.util] converting 8 rows to native objects took 0.078123s
2018-01-03 22:07:42 DEBUG (Thread-10) [homeassistant.components.history] getting 8 first datapoints took 0.104951s
2018-01-03 22:07:42 DEBUG (MainThread) [homeassistant.components.history] Extracted 32 states in 0.146987s
2018-01-03 22:08:14 DEBUG (Thread-4) [homeassistant.components.recorder.util] converting 1607 rows to native objects took 0.742370s
2018-01-03 22:08:14 DEBUG (Thread-4) [homeassistant.components.history] get_significant_states took 0.750269s
2018-01-03 22:08:14 DEBUG (Thread-4) [homeassistant.components.recorder.util] converting 5 rows to native objects took 0.076551s
2018-01-03 22:08:14 DEBUG (Thread-4) [homeassistant.components.history] getting 5 first datapoints took 0.092316s
2018-01-03 22:08:14 DEBUG (MainThread) [homeassistant.components.history] Extracted 1612 states in 0.885407s
2018-01-04 05:45:28 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
Bump. I also noticed a lot of Timer out of sync errors since moving to the 0.60 version…
Ok Update from my issues I have moved MQTT server mosquito onto a second raspberry pi running rassbian I have also move a python program that I use to interface with my Paradox alarm system
This has reduced a lot of lag and lots of the trimmer issues still get the odd one but much better.
my guess is the timer error is being caused by lag from many possible areas so anything that speed up the system is better.
only errors I have at the mo are incorrigible warnings now
2018-01-05 02:56:15 WARNING (MainThread) [homeassistant.setup] Setup of media_player is taking over 10 seconds.
2018-01-05 02:56:15 WARNING (MainThread) [homeassistant.setup] Setup of tts is taking over 10 seconds.
2018-01-05 02:56:15 WARNING (MainThread) [homeassistant.setup] Setup of remote is taking over 10 seconds.
Moved to Atom board and so from HASS.io to Home Assistant… the error is disappeared also maintaining the same config.
And the speed of automation trigger and web page loading is decuplicate!
Seems the RPI 3 is lacking enough power to run Home Assistant unless a simple build bit of a shame really as it’s recomended for it
It depends on what you have configured in HA and what else you have running on the Pi. I run HA on Pi B+ and it runs perfectly happily, with the occasional Timer out of sync when influxdb gets greedy.
Running a Xeon processor on a FreeBSD install and seeing alot of this. Wouldn’t care so much but the current zha component basically fatally dies if it starts hitting these timeouts and requires a hass restart 
One thing I did notice is in HASS the discovery component is enabled by default I found at least with my google home if I added it the cast Device manually it would be seen as a second device as the discovery component had already detected it and also cause a lot more time out errors until removal of both cast devises and disabling discovery . Maybe you guys could try disabling the discovery and test see if makes any dif for you
@winter
I am having a similar issue with my Rpi that my zha is not responding after a few hours of running and I am trying to determine what the cause is. Have you determined that the “Timer out of sync” is knocking the zha component out requiring a restart to respond again?
Yes, there is an issue with bellows which outlines the problem:
https://github.com/rcloran/bellows/issues/37
Does that still apply if I am not running in a docker session?
I’m not running in a docker session. I believe this issue is that if there is a hold up in communicating with the zigbee device, then it basically just shuts down and needs to be reinitialised. Rcloran has a couple of options to alleviate this, but it just comes down to time to implement.
Ah, thanks for the info. I didn’t have any issues until the recent upgrade to 0.61.1 Unfortunately it’s a bit annoying as it prevents automations from working. I’ll add some info to the github link provided above and hopefully a resolution can be found soon.
A lot of people have been reporting the timer reset problem in later HA versions. Some people have rolled back to older versions to fix the problem.
I have been using the opportunity to clean up my freebsd box in the hope of minimizing background processors that are causing the problem, until the HA team can improve things. Also upgraded to the latest python, not sure if that will make a difference 
I also see there was an update to bellows by doing this -> pip3 install --upgrade git+git://github.com/rcloran/bellows
Have you run this upgrade? If so, has it made any difference?
1 Like
I try to avoid running non-released code unless it specifically addresses my issue so haven’t tried this out yet. I’m already running my forked openzwave :S
I’ll probably poke through rcloran’s recent PR’s and see if there is anything of interest. I’m assuming he will be doing a formal release some time soon.
Hello.
I’m running HassIO on a Raspberry PI 3
Since I upgraded from 0.65.4 to 0.65.5:
Timer got out of sync. Resetting
6:16 PM core.py (ERROR)
Timer got out of sync. Resetting
6:13 PM core.py (ERROR)
Timer got out of sync. Resetting
6:08 PM core.py (ERROR)
Timer got out of sync. Resetting
6:02 PM core.py (ERROR)
Timer got out of sync. Resetting
5:57 PM core.py (ERROR)
Timer got out of sync. Resetting
5:51 PM core.py (ERROR)
Timer got out of sync. Resetting
5:51 PM core.py (ERROR)
Timer got out of sync. Resetting
5:46 PM core.py (ERROR)
Timer got out of sync. Resetting
5:40 PM core.py (ERROR)
Timer got out of sync. Resetting
5:35 PM core.py (ERROR)
Timer got out of sync. Resetting
5:29 PM core.py (ERROR)
Timer got out of sync. Resetting
5:24 PM core.py (ERROR)
Timer got out of sync. Resetting
5:18 PM core.py (ERROR)
Timer got out of sync. Resetting
5:13 PM core.py (ERROR)
Timer got out of sync. Resetting
5:08 PM core.py (ERROR)
Timer got out of sync. Resetting
5:07 PM core.py (ERROR)
Timer got out of sync. Resetting
5:02 PM core.py (ERROR)
Timer got out of sync. Resetting
4:57 PM core.py (ERROR)
Timer got out of sync. Resetting
4:57 PM core.py (ERROR)
Timer got out of sync. Resetting
4:51 PM core.py (ERROR)
Timer got out of sync. Resetting
4:46 PM core.py (ERROR)
Timer got out of sync. Resetting
4:43 PM core.py (ERROR)
Timer got out of sync. Resetting
4:40 PM core.py (ERROR)
Timer got out of sync. Resetting
4:35 PM core.py (ERROR)
Timer got out of sync. Resetting
4:29 PM core.py (ERROR)
Timer got out of sync. Resetting
4:24 PM core.py (ERROR)
Timer got out of sync. Resetting
4:24 PM core.py (ERROR)
Timer got out of sync. Resetting
4:18 PM core.py (ERROR)
Timer got out of sync. Resetting
4:13 PM core.py (ERROR)
Timer got out of sync. Resetting
4:13 PM core.py (ERROR)
Timer got out of sync. Resetting
4:07 PM core.py (ERROR)