Z-wave not working after 2 days or so, needs to restart HA

Hi, after around 0.64 or so, I’m having a problem with my zwave net. After a pair of days or so working flawlessly it stops working and I have to restart my HA container on docker in order to get it back working again. Then after another 2 days it happens again.
I don’t know why this is happenning, my zwave network is becoming quite big, around 27 devices, more or less. However, I don’t think this should be a problem. I don’t know either if this has something to do with my HA version or if it is just because of an specific zwave component, although when working, all seem to work fine.

Most of my zwave devices are zwave+ although 2 are old plain zwave.
I would appreciate any orientation on what could be the problem. Thanks!!

I have 35+ devices, mix between zwave+ and regular, and i’m running 0.64.3. I’m not having any issues. If you aren’t getting errors in the logs, I would look towards your hardware as being the culprit. Maybe there is a setting that auto shuts off your usb? assuming you have usb

Thanks for your answer petro. Great to know you have more z-wave devices than I do and everything is working fine for you. Then my problem should be another, and not the number of devices and neither my HA version.
And, yes, I have an USB aeotec 5th gen in my Synmology Ds216+, I will take a look at my synology as I didn’t know there was an option that could auto shut off my USB port. Regarding the log, I already took a look at it, but couldn’t find anything of interest. Thank you again for your clues, I’m gonna look for that shut off option, it may be the problem, I’ll report back!

Hi I’m still having this problem intermittently so my zwave network is not reliable at all now with Home Assistant. I’m needing time and time again, after 1 or 2 days, to reset my container to have zwave working again. Any help would be appreciated.
I am attaching my OZW log file just in case someone with knowledgedge could find something that I couldn’t. I trimmed it a bit and converted it to yaml just to be able to upload it to the forum.

Thanks in advance!!OZW_Log.yaml (3.0 MB)

I’ve limited my HA log to errors or worse. And now this is what I’m getting from this evening alone, zwave did not stop but:

2018-05-03 17:13:45 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-03 17:38:43 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-05-03 18:07:52 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-05-03 19:09:41 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-03 19:15:14 ERROR (MainThread) [homeassistant.components.websocket_api] WS 139974718936400: Client exceeded max pending messages [2]: 512
2018-05-03 19:15:14 ERROR (MainThread) [homeassistant.components.websocket_api] WS 139974718936400: Client exceeded max pending messages [2]: 512
2018-05-03 19:15:14 ERROR (MainThread) [homeassistant.components.websocket_api] WS 139974718936400: Client exceeded max pending messages [2]: 512
2018-05-03 19:15:14 ERROR (MainThread) [homeassistant.components.websocket_api] WS 139974718936400: Client exceeded max pending messages [2]: 512
2018-05-03 19:23:27 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-05-03 20:17:07 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-03 21:04:42 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-05-03 21:49:28 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()

No idea what it got out of sync and no idea about the other errors either. I don’t know if this is important or not. I’m running docker from a DS216+ synology. Would it be better to run HA from a dedicated Raspberry Pi 3 B+? Could the issue be caused because of my synology doing too many tasks at the same time?? Thanks in advance for your answers!!

I would love if someone could help me with this!!:disappointed_relieved::disappointed_relieved:

Now I can see new things in the log, somehow related to Sonos, weather underground and duplicity of entity_ids?? See below, I need help please!.

2018-05-04 20:05:29 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:05:34 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:05:44 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:05:51 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:05:55 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:05:59 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:06:24 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:06:32 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()
2018-05-04 20:09:34 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:10:57 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:11:37 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:16:20 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-04 20:17:06 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:17:12 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()
2018-05-04 20:17:12 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:17:18 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:17:26 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:17:28 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:19:37 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:22:17 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:22:23 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:22:26 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:22:31 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:27:35 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 20:58:36 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()
2018-05-04 20:59:24 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:00:32 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:02:18 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:03:35 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:03:39 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:06:37 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.dormitorio fails
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity.py”, line 204, in async_update_ha_state
yield from self.async_device_update()
File “/usr/src/app/homeassistant/helpers/entity.py”, line 327, in async_device_update
yield from self.hass.async_add_job(self.update)
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/media_player/sonos.py”, line 478, in update
self._subscribe_to_player_events()
File “/usr/src/app/homeassistant/components/media_player/sonos.py”, line 458, in _subscribe_to_player_events
device.update_groups()
File “/usr/src/app/homeassistant/components/media_player/sonos.py”, line 686, in update_groups
coordinator_uid = self.soco.group.coordinator.uid
AttributeError: ‘NoneType’ object has no attribute ‘coordinator’
2018-05-04 21:17:31 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:17:37 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:17:57 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:18:00 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:18:03 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:18:08 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:18:11 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:18:28 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:19:04 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:19:19 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:19:27 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:19:30 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:19:39 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:19:49 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:19:55 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:06 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:09 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:14 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:21 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:24 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:29 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:32 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:36 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:40 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:20:45 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:21:01 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:21:05 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:21:13 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:21:15 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:21:19 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:24:25 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-05-04 21:24:40 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()
2018-05-04 21:29:51 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()
2018-05-04 21:39:31 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 308, in _async_add_entity
msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: media_player.shield_android_tv. Platform plex does not generate unique IDs
2018-05-04 21:41:02 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-04 21:50:28 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()
2018-05-04 22:22:20 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

After this log, my zwave network and devices are working but not having a quick response (delay of more than 20 seconds, not normal at all). Please help!!:confounded::confounded:

UPDATE: Zwave stopped working again!!:sob::sob:

Looks like your container has lost network access.

1 Like

Thank you for your answer! how do you know that? Is it because of the timer got out of sync message??..and actually, you might be right bc, if I stop and restart my container it keeps working fine for a day or so and then, it all happens again but, why? what could be the reason? Should I run HA as hassbian from a dedicated raspberry pi instead of from docker in my synology? Or I just need to find the real issue and everything will work fine again??

^ Network connection issue

^ Unable to communicate with your media_player device (more network connection issues)

As I am unfamiliar with synology I couldn’t say why it’s occurring, you’d have to look at any logging Synology does for your containers, if you want a quick fix, yes move your configs to a Pi or another server/computer.

1 Like

OK, these are the last lines of my container inside docker log:

/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being m
ade. Adding certificate verification is strongly advised. See: Advanced Usage - urllib3 2.2.1 documentation
arnings
InsecureRequestWarning)
/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being m
ade. Adding certificate verification is strongly advised. See: Advanced Usage - urllib3 2.2.1 documentation
arnings
InsecureRequestWarning)
/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being m
ade. Adding certificate verification is strongly advised. See: Advanced Usage - urllib3 2.2.1 documentation
arnings
InsecureRequestWarning)

Do these mean that I am under attack?? I am also getting synology notifications like this one:

Auto Block:
IP address [103.89.90.103] of DS216plus has been blocked by SSH

Not sure about the docker errors.

Could be a port scan, hard to say, I don’t use synology. Do you have it exposed to the outside world?

Hi.
I am no expert, but did get the same “Timer got out of sync. Resetting” a lot on the same hardware setup. I deleted the log database for HA, which corrected that error. Just stopped the docker and deleted the file.
I have not gotten the error since.

I have my HA exposed under SSL (https connection), however I also had my synology exposed with its ‘quickconnect feature’ (not SSL) to access synololgy front end so, I have deactivated it now to only access it now from inside my LAN. I’ll see if my system stops having the problem and the auto block ip messsages. I will let you know, thanks!!

When I filtered my log to only ‘errors and above’, I also deleted first the log database but still had all the issues. Thank you anyway, I’m glad that solved your problem.

Even with quickconnect and external accesss to synology closed, I am still getting this from HA log:

2018-05-05 08:30:45 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/sensor/synologydsm.py”, line 109, in run_setup
for volume in config.get(CONF_VOLUMES, api.storage.volumes):
TypeError: ‘NoneType’ object is not iterable
2018-05-05 08:51:45 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140104782114488: Client exceeded max pending messages [2]: 512
2018-05-05 08:53:30 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-05-05 08:54:58 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-05-05 08:57:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-05 09:05:18 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140104781494032: Client exceeded max pending messages [2]: 512
2018-05-05 09:05:18 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140104781494032: Client exceeded max pending messages [2]: 512
2018-05-05 09:05:18 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140104781494032: Client exceeded max pending messages [2]: 512
2018-05-05 09:09:22 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-05-05 09:10:14 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out

I don’t know how to solve it!!:cold_sweat::cold_sweat:

Try throwing your HA on a separate system.

Yep, I’ll get a Pi3 B+ and install hassbian, I was planning this for the near future anyway, so I will order it now!:sunglasses:

OK, just to report back: I’ve installed a Hassbian image on a Pi3B+ and it has been much easier to set up than was Docker in my Synology, especifically SSL with Duckdns was a breeze now as it came already in a script. Now, everything is working fine for 2 days. I hope it will continue like this: zwave net, with around 40 devices, is working great. Thank you.

Good to hear.

Hello,

I’m using Hassio now for one year.
i have 32 nodes, and i had an automation to heal network all night. Since i have this automation, z-wave does not brake every one or two days. I have anyhow problems from time to time.
Sometimes nothing works, and after one or two hours every thing works again, and sometimes it is realy fast, and sometimes it needs 20 to 30 seconds to respond.

But as more often i read from others with bigger networks that they have no problems, i think I’m doing something wrong.

can someone help troubleshoot what I’m doing wrong? It’s not nice as it is at the moment.