Z-Wave long startup and timeouts

Configuration Z-Wave
1

Hi

I’m using OpenZWave within HASS and always have issues restarting HASS because it takes almost an hour for Z-Wave to come back to live. However, more often than not not all devices are Ready when the process is complete and some devices are not functional in HASS, while they seem to work perfectly fine.

I have attached a full log, and was wondering if someone can help me out with the cause for this delay in startup and all the errors. I’m using an Aeotec Gen5 stick. There are times during this startup process where it seems to hang. During those moments the ‘disco ball’ on the stick is either off or stuck to a certain color. It no longer alternates colors. In the logs this can be seen from 23:21.43 to 23:28.15 (7 minute pauze) and again between 23.29 and 23.35 (6 minute pauze).

I have tried to migrate to the new HASS OpenZWave-daemon plugin. However, the OpenZWave-MQTT Docker container exhibits the same issues. The same timeouts, the same ‘hangs’.

I have about ~30 modules. I have this issue for as long as I can remember using ZWave with HASS / OpenZWave. I used to run HomeSeer 3 and that worked perfectly fine. Boot/startup was done in matter of seconds.

Any help is appreciated!

Log can be found on http://www.tozz.nl/attachments/zwave-08062020.txt

2

stupid question - you’ve tried to “repair” your network?!

Long waiting times (without looking to your log) sounds to me as a problem with the zwave network itself

3

HASS automatically ‘heals’ every night IIRC. So, I didn’t try to manually heal the network but I believe I shouldn’t need to. Additionally, my modules never change location after I’ve added them so I don’t see why a network heal should resolve anything.

After all, network heal is only ‘fixing’ return routes isn’t it?

1 Like
4

What is the hardware you are running HASS on? I know there are issues with the Gen5 stick with a PI4.
https://www.raspberrypi.org/forums/viewtopic.php?t=245031

5

Intel NUC. Shouldn’t be an issue I think?

6

This was stopped some time ago since it served no purpose.

Try running your log in the analyzer: http://openzwave.com/log-analyzer

7

Does dmesg mention anything during such a pause? It seems weird that the disco colors even stop during that time, maybe the USB port does not receive enough power or something?

8

I think I found the issue. Apparently Node 3 is dead/non-responsive, and this causes the gigantic delays and timeouts. I will remove Node 3 this weekend and see if that fixes things.

I can rule out OZW as the culprit. I’ve used the Aeotec IMATool on my laptop and it exhibits the same issue. As soon as it tries to query nodes it fails with lots of timeouts. I’ve also restored the EEPROM on a new stick, again same issue.

So it’s probably the dead node or perhaps interference on the 868 Mhz band.