Upgrade to 2020.2 with Zwave WITHOUT fatal error.

[Domoticzuser3109]

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 service domoticz
- Replace cache with a working backup
- Start service domoticz
- All nodes are loaded from the restored cachefile

Eralier that fixed the issue, but not anymore! What happens now is:
On 2020.2 beta build 12639:
- Stop service domoticz
- Replace cache with a working backup
- Start service domoticz
- Domoticz will delete your replaced cachefile and start a new node search with an empty cachefile

So something has changed when a new OZW was merged into the Beta builds.

[EddyG]

I am running 2020.2 build 12554 with OZW 1.6-1520-g893e076a
This version does not build the cache file at the start of Domoticz.
The cache file is build from scratch if it is not 100% complete.

I just complied the latest build 12639 and it still has the same OZW version.

[Domoticzuser3109]

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.

[Domoticzuser3109]

I think I might have found the reason. If you look in the cache XML you can see each node has a

Code: Select all

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 node is not found in the cache or if the OZW version is different.

I will give it a couple days to get stable again and than try a restart to verify the cachefile will survive it now.

[mcmikev]

Hi,

I am experiencing the same problem.
I thought it was my setup.

I build a new rpi4 for domoticz and compile from source. After startup some SVT (heating stuff) is started and then the log shows errors (node xx not found) this is because Z-wave is starting but all the names are italic in the hardware and are being interviewed again.
Only then when that is done, the node is working again.

I have seen that the ozw_cache file is there but not sure If that is being used at that time.
I hve this every time after a reboot!

PS: I am also running 2020.2 build 12629 (build from source) and OpenZwave version 1.6-1545-g1c7b6202

[Domoticzuser3109]

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 cache, after which it will query all nodes again.

The only way to get this fixes is making sure all nodes have send a NIF (node information frame) to the controller. You can do this by using the "refresh node info" and press the include button on the Zwave device within a couple of seconds. If all went well the node is now recognised again. Do not restart domoticz before all nodes are done! In most cases only the battery operated nodes need to send their NIF this way. Mains operated appliances will respond to the query request from the controller.

Before a reboot you can check the ozw cachefile to make sure all nodes are listed as query_stage="Complete". If that is the case make a backup of the file just to be sure.