I am running my ZWave JS outside of Home-assistant in a docker comtainer. The network has been stable for over 6 months, however, my machine is starting to lock up. I decided to move my ZWave JS to a different host assuming as long all the store directory was copied over and mounted to the same location no problem. However, nothing worked after moving my docker container to the new host. I do know I have done this in the past and so not sure what has changed in terms of Zwave JS stack changes. Can we still backup the store mount to a new location and have everything moved over? Or I am missing something in newer versions of ZWaveJS?
I see errors like this in the new host:
zwavejs | 11:43:18.981 CNTRLR [Node 192] The node did not respond after 1 attempts, it is presumed dead
zwavejs | 11:43:18.984 CNTRLR [Node 192] ping failed: The node did not acknowledge the command (ZW0204)
zwavejs | 11:43:18.986 CNTRLR [Node 192] Interview attempt (1/5) failed, node is dead.
zwavejs | 2023-10-29 11:43:18.987 ERROR Z-WAVE: [Node 192] Interview FAILED: The node is dead
zwavejs | 11:43:18.993 DRIVER all queues idle
It looks like ZWave JS is not seeing your controller. It may be that the path to the controller in Docker has changed from your previous system. Also, make sure that the Z-Wave keys are correct.
Aren’t the keys in the config? Are you taking about the SESSION_SECRET? I thought those would be stored in the store and be saved on the volume. How do I have make sure the keys are same?
Everything is in the mounted folder including keys. I’ve moved it around between hosts successfully. As @sota says it’s is the path to your controller and/or the docker run / docker compose isn’t mapping the right device in. Maybe share your docker config.
@sota how did you determine it was CONTROLLER not working? I don’t see any error in the logs relating ot the CONTROLLER. Here is the top of the logs when container starts…
Also, you say that you copied the files over to the new system, perhaps if you tried the built-in backup / restore feature in ZWave JS you might have better luck.
Also, were the old and new systems running the same version?
Yes, I have a similar problem. I have Aeotec Gen5 1.1 and that works fine. I copied the config to a Gen5+ with the latest firmware, using the windows backup tool, and that worked fine. But with the Gen5+ stick in the raspberry pi I get this same problem. All nodes marked dead. Going back to the old Gen5 stick in the raspberry pi and all works fine.
So some combo of firmware and backup/restore between gen5 and gen5+ doesnt work, or the gen5+ doesnt like the raspberry pi 4.