I can confirm my Zwave installation seems stable now. In my specific case it was likely caused by the missing node and thereby missing query complete message in the cachefile. Most likely the Zwave driver will remove the cachefile is it sees a device missing from the cache and starts with a new ...

I think I might have found the reason. If you look in the cache XML you can see each node has a query_stage="Complete" field. These where all set, but there was one node missing in the backup cachfile. So I gues that it will delete the cache if a node is not listed as query_stage="Complete", if a ...

Hmm, that is strange. Then it must be something in my cachfile which is preventing it from being preserved. If we could find out what part of the cache file is indicating that the file must remain persistent we can see if that part is indeed indicating a problem. I will have a look in the cache xml.

Hi EddyG, that was true for domoticz 2020.2 stable...The latest builds are rewriting the cachefile after each service restart, also when all devices are working for weeks allready and are done probing/initializing. You can check the new behaviour also by using our earlier solution: On 2020.2: - Stop ...

Updated to latest Beta 12639 but still the same problem with the xml file which is being overwritten. I am not alone with this problem, these seem all related to Zwave losing its cachfile: https://www.domoticz.com/forum/viewtopic.php?f=24&t=33892 https://www.domoticz.com/forum/viewtopic.php?f=24&t ...

Well, it was running perfectly for months. Then I added some new curtain motors and everything was running fine till the next reboot of the RPi. After the reboot Zwave lost some nodes again. Restoring the cachfile from the backup (see how-to above) fixed it. As I saw that there where config update ...

Yes! I tried beta build 12077. Did do this: - update rpi with sudo apt-get update and sudo-apt upgrade - update Domoticz to latest beta - started Domoticz to see zwave in trouble with lost nodes again - sudo service stop domoticz - copied the backup of my ozw cachefile over the broken cachefile ...

True! If you don’t stop domoticz it wil not change anything till restarting domoticz, but when restarting domoticz it will first write a new cachefile on closure.

Correct, be sure to press within 5 seconds as the node refresh will likely timeout. Other option is to just use the include button in domoticz and on your device. It works the same as refresh as far as I can see but gives more time. The nodes are already known so the won’t be added again.

I have been reading around here for a while due to the fact that I also had major problems with my zwave network after upgrading to 2020.2 So far I found out: - Enabling the allow new hardware option prevents domoticz from crashing after the upgrade, this is a great find! - Some nodes where still ...