Hi, wondering if anyone can point me in the right direction.
I’ve successfully setup a zwave aeotec_zw090_z_stick_gen5 and paired a four way sensor. I was reading values from it, until I had to do a HASS.io restart.
My Z stick seems to be stuck at "initializing (Neighbours) and consequently the sensor is showing “entity not available”. A screenshot is attached.
It seems as though i spend a lot of time configuring and trouble shooting this setup only to have it fail each time a reboot (I had different errors previously).
I can see both the ‘Z stick’ and the sensor in the “Z-Wave Node Management” Nodes drop down. But nothing is happening. What am I doing wrong?
How long have you waited?
It may take a little while for z-wave to be ready after rebooting (although it should be short with the low number of devices you have)
No nodes are listed in the Z-Wave Network Management panel.
It should be there right? Do I need some sort of docker pass though somewhere? Running all commands on the Z-Wave panel just gives me a “failed to call service error”.
I performed an update and the zwave entities remained after the restart.
Added the system health component to configuration.yaml, performed a restart and now they’ve gone. Completely, not event present under the Z-Wave Node Management panel.
Sometimes its there, sometimes it isn’t. Just doesn’t seem to be any rhyme or reason to it all.
Did a reboot, lost everything again. Repeated by removing z-wave competent and associated files and rebooted again. Got the z-stick back, unable to include the sensors back in. Hopeless.
The Z stick came up by itself after and update and reboot. I’ve managed to reconnect one sensor, the others refuse to join. More trouble than its worth I reckon.
Did you guys ever find any solution? I ran into the same thing when switching HA from my PI to ubuntu. I have tried many things- nothing so far other than:
Turning on ubuntu from a cold start NEVER works. Once HA is up the only way to get the zwave back and working again is to do a REBOOT. And you can’t do it right away- you have to wait a few minutes. If you reboot right away you get nothing or just a few nodes with errors. Wait a bit and you get everything back…
I found one thread where someone had same issue but he fixed it by started over from scratch . New HA and exclude and include zwave all devices,
I may do that eventually- just want to make sure first this is not do to running zwave under ubuntu vs pi (ie thats the best it gets)