Problems again with zwave after power outage

[Lightning707]

For the second time in 2 years time, all my zwave devices have disappeared after a general power outage. Last time it was after of a general power outage of the electricity network in my street. I then did a hard reset of my AEOTEC zwave gen5 stick and re-included all my zwave devices again.
This time the power outage was my own fault. I was working on my electrical installation and I had to switch off the general circuit breaker. I completely forgot to first shutdown my raspberry Pi. After switching on the power again, all my zwave devices were gone in the hardware list.

I really thought that this time, I had all the necessary backups to do a more clever fix. I removed the domoticz.db file and replaced it with a backup of several hours before the power outage. The problem was still there and I the Zwave devices list was still empty. Then I removed the ozwcache XML file and also replaced it with a backup. After rebooting all my zwave devices where again in the list. When I push the physical button of a switch, the state in Domoticz does change. However, I'm still not able to control a switch from Domoticz. I do not get any error messages in the log list when trying to operate a switch from domoticz.

I also had a backup from my AEOTEC zwave gen5 stick. I restored this backup using "zwave_500", but this did not solve the problem either.

Do you have any suggestions?

[Lightning707]

Update: I was able to control two roller shutters, but unfortunately it does not work again now

[Lightning707]

I have read in another post on this forum that the ozwcache XML file is not really required, as it is created by Domoticz/OpenZwave.
I have therefore removed the file from /domoticz/Config/ again.

When I reboot Domoticz I get the following messages in the log:

2022-06-03 16:35:09.822 Status: Zwave stick: using config in: /home/pi/domoticz/Config/
2022-06-03 16:35:09.828 Status: Zwave stick: Starting...
2022-06-03 16:35:09.828 Status: Zwave stick: Version: 1.6-1911-gc6a420ef
2022-06-03 16:35:09.831 Status: Zwave stick: A DNS Error Occurred
2022-06-03 16:35:09.831 Status: Zwave stick: ManufacturerSpecificDB Ready

Does anybody know what I can do about the DNS Error?

[Number8]

In hardware tab does the stick shows as connected? Check it is connected to the right usb interface.

[mgugu]

OZW does dot unfortunately offer serious troubleshooting. Simply install zwavejs2mqtt on your machine (or other machine) and plug your stick on it.Zwavejs2mqtt shows detailed log. I solved such OZW strange problem like that in the past (viewtopic.php?p=282817#p282817)

[sammyke007]

I migrated two days ago from OZW to ZwaveJS2MQTT. Just follow this guide:
https://www.domoticz.com/wiki/ZwaveJS2MQTT (at the bottom is the migration part)

Didn't need to repair anything.

[Lightning707]

In hardware tab does the stick shows as connected? Check it is connected to the right usb interface.

The stick is definitely connected to the right usb interface. When I operate the physical switch, the status also changes in Domoticz.

[Lightning707]

I migrated two days ago from OZW to ZwaveJS2MQTT. Just follow this guide:
https://www.domoticz.com/wiki/ZwaveJS2MQTT (at the bottom is the migration part)

Didn't need to repair anything.

Thanks! I will try this.

[lost]

The stick is definitely connected to the right usb interface. When I operate the physical switch, the status also changes in Domoticz.

Loosing access to all zwave devices is usually a consequence on not having made usb persistent for the zwave controller (see wiki). IMO, you may triple check this. Operate physical switches "successfully" in such situation may be misleading & just done on the interface. Not even sure you'll see OZW timeouts if the controller is unseen...

I'm almost 100% zwave & after a main power fail I may have a few issues (not always) for some devices but that's solved by a power off/on for those using 220Vac (I have a aeotec relay module that sometimes have such issue) or triggering a node wake-up (usually a triple-click on association button) on battery ones (rarely have the issue on some neo-coolcam PIR sensors). More tricky, my qubino smart-meter at the head of my home power breaker panel sometimes still report power measurements (thus seems OK at first sight) but only wired relay endpoint cannot be controlled anymore: After wasting time excluding/re-including, I found relay function was restored by triggering a "resfresh node info" on the module from OZW control panel.

But, again, that's not consistent issues (maybe only the smart-meter relay endpoint now is: Not sure if this was after OZW 1.6 or some module ageing issue, power outage are quite rare).

In such situation, try to understand what's wrong before restoring configurations & changing anything on zwave network. Trying to fix only what's precisely needs to get fixed as global changes are in such situation adding new issues to current ones.

[Number8]

I definitely second what lost says. All issues I had with zwave disapeared when I made usb connection persistent. I also had an issue because of the poor quality of an usb extender.