So my zwave network is getting large, but not over 25 devices yet. However, it seems like every single time I reboot the NUC itself. The zwave hangs with an error and I get a whole screen full of entity not available on the overview. I flip over to the zwave logs and I see frame errors etc… and The Aeotec stick has stopped talking to OpenZwave. Usually I have to reboot Hass a couple of times. I’ve had to reload my zwave config sometimes to get it to restart. During this process it is very common for my devices to come back in the integration, and you can see the network working in the OpenZwave log, but my Overview panel still says every entity is not available. Usually I can just restart home assistant again and it will come back.
In this forum I’ve read many different things about the zwave stick being rebooted while it is writing its config. Including zwave as an integration instead of by zwave: in configuration.yaml. There are quite a few issues that I’m trying not to go into at the moment.
Right now, I just want to ask the group, what is the best practice for success when rebooting this configuration NUC/Hass.io/Aeotec zwave plus stick. Once I know I’m using the best/recommended procedure, I will start troubleshooting elsewhere.
- Should I stop the zwave network first?
- Should I stop home assistant first?
- Should I use the reboot or shutdown from the hass.io/system panel?
- Should I just use the power button on the NUC (I know this is wrong, I’m just including as an example)?