all Zwave data lost after a general Power cut

[Tylou]

Hello,
I'm facing an issue with Domoticz and my zwave devices.
I lost all nodes in the Zwave devices list but Hardware liste is OK. The openZwave Control Panel is empty too
I have 9 devices in my home (NodeOn, Figaro, Qubino, ...) All worked fine since 5 years, with buggs sometimes but nothing I couldn't solved .

here is the hardware list

Presse-papiers-1.jpg (42.03 KiB) Viewed 19468 times

device list (empty)

Presse-papiers-2.jpg (62.27 KiB) Viewed 19468 times

No error in the log and all other things are working fine (MQTT, lua script python script, HTTP API,...)

If I ask to include a new node an error appears:
2020-11-06 11:27:44.290 Error: OpenZWave: Exception. Type: 100, Msg: Invalid HomeId passed to GetDriver, File: /home/pi/build32/open-zwave-read-only/cpp/src/Manager.cpp (Line 410) OpenZWave.cpp:3483
2020-11-06 11:27:51.623 Error: OpenZWave: Exception. Type: 100, Msg: Invalid HomeId passed to GetDriver, File: /home/pi/build32/open-zwave-read-only/cpp/src/Manager.cpp (Line 410) OpenZWave.cpp:3877

I tryed with a DB backup ==> still same issue
I tryed a former SD backup of the whole Rasp that worked ==> still same issue
I opened the DB and it seem OK (but not sure : I'm not confident with SQL DB)

Configuration :
Rasp3 model B - Buster and up to date (OS + firmware)
Domoticz stable 2020.1
RaZberry V1

Please, is someone has an idea to help?
And I would like avoid to reset all zwave devices & controller
Thanks

[mark.sellwood]

Is the Serial Port correct as it can change?

[Tylou]

Hi,
Thanks for your help
I think it's OK, I have 4 serial port deteted and ttyAMAO0 which is a links to SERIAL0
(I made that when I upgrate to Rasp3 keeping my existing DB)
Thus RaZberry controller is detected with both
But how can I check the communication between RazBerry and the Raspi? I didn't find any tutos yet

Thanks

[Tylou]

update,

found that : https://forum.z-wave.me/viewtopic.php?p=86789#p86789

in /boot/config.txt, I added

Code: Select all

enable_uart=1

I execute following command

Code: Select all

sudo systemctl stop [email protected]
sudo systemctl disable [email protected]

Now I retreive the full list of Zwave devices

Presse-papiers-3.jpg (165.04 KiB) Viewed 19458 times

But I'm not able to controle my devices

now I have this error in log

Code: Select all

2020-11-06 15:27:20.752 Error: OpenZWave: Type_Notification, NodeID not found internally!. HomeID: 0, NodeID: 255 (0xff)

I tested update some devices :

from devices to Domoticz ==> it's refreshing Domoticz
command from Domoticz ==> nothing appends

Help still needed,
thanks

[Number8]

I don't know whether you solved your problem. I had same issue today running beta 12467. Pretty scarry. After several reboot, several service stop/start, I unplugged zwave stick, plugged it back, rebooted once again, and everything was back up. I can testify it was no a wrong USB port issue. I just don't know what was the issue.

[jake]

I don't know whether you solved your problem. I had same issue today running beta 12467. Pretty scarry. After several reboot, several service stop/start, I unplugged zwave stick, plugged it back, rebooted once again, and everything was back up. I can testify it was no a wrong USB port issue. I just don't know what was the issue.

I seem to have the same problem now. I had one Fibaro plug that 1 out of 5 times did not want to turn OFF (ON always worked). I tried the same trick as with another one of those plugs: reset the device, let domotic detect the failed node and do a 'replace failed' and include again under the same ID.

However, it didn't work for this one, so I turned the OpenZwave hardware off and on again in Domoticz (build 13058) and ever since the OpenZwave is dead, the setup button is red. I tried a soft reset of the controller, after renaming the openzwave config file in pi/domoticz/Config. It than built a new file which was slowly growing, it showed all devices with red text, but none would work. Updated times were improving as well (except some sensors). Unfortunately, after a reboot of the complete pi, I'm back to square 1 with no OpenZwave at all.

lsusb shows the Gen2 Stick (Bus 001 Device 008: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family]) but it seems improper loaded in Domoticz.

When I now disable the OpenZwave, Domoticz locks up and isreset by Monit after some time. Afterwards OpenZwave is disabled, but when I enable it again, I only get the following in the log (while filtered on zwave):

Code: Select all

2021-03-10 23:34:43.329 Status: OpenZWave: Starting...
2021-03-10 23:34:43.329 Status: OpenZWave: Version: 1.6-1520-g893e076a
2021-03-10 23:35:07.645 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:35:48.384 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:36:23.663 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:36:58.807 Status: OpenZWave: A Config File Failed to download

How to fix this?

EDIT:
Patiently waiting for 15 minutes fixed it by itself luckily. For now, I won't touch Zwave anymore

[waaren]

When I now disable the OpenZwave, Domoticz locks up and isreset by Monit after some time. Afterwards OpenZwave is disabled, but when I enable it again, I only get the following in the log (while filtered on zwave):

Code: Select all

2021-03-10 23:34:43.329 Status: OpenZWave: Starting...
2021-03-10 23:34:43.329 Status: OpenZWave: Version: 1.6-1520-g893e076a
2021-03-10 23:35:07.645 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:35:48.384 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:36:23.663 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:36:58.807 Status: OpenZWave: A Config File Failed to download

How to fix this?

There seems to be a recent change in the OpenZwave part of domoticz. I am on build 13063 and see something similar. A github issue is created for this and I will link this topic into it.

Until the code is fixed again in a next build, the best you can do is to sit tight and don't touch it. I almost destroyed my config in the process to fix it and only because I could recover the mess I created using a recent backup and after waiting almost an hour the devices appeared again.

[Alcloud]

I only get the following in the log (while filtered on zwave)

Yes, I have the same error

[Number8]

When I now disable the OpenZwave, Domoticz locks up and isreset by Monit after some time. Afterwards OpenZwave is disabled, but when I enable it again, I only get the following in the log (while filtered on zwave):

Code: Select all

2021-03-10 23:34:43.329 Status: OpenZWave: Starting...
2021-03-10 23:34:43.329 Status: OpenZWave: Version: 1.6-1520-g893e076a
2021-03-10 23:35:07.645 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:35:48.384 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:36:23.663 Status: OpenZWave: A Config File Failed to download
2021-03-10 23:36:58.807 Status: OpenZWave: A Config File Failed to download

How to fix this?

There seems to be a recent change in the OpenZwave part of domoticz. I am on build 13063 and see something similar. A github issue is created for this and I will link this topic into it.

Until the code is fixed again in a next build, the best you can do is to sit tight and don't touch it. I almost destroyed my config in the process to fix it and only because I could recover the mess I created using a recent backup and after waiting almost an hour the devices appeared again.

When a cold reboot is performed the same error is reported. Currently running 12485

[waaren]

When a cold reboot is performed the same error is reported. Currently running 12485

Seems to be related with an outage of the OpenZwave download server. Check github issue 4723

[antwan]

There is an update available for this problem (openzwave server down).

If you update to the latest version 13064 then domoticz /Zwave start again super fast.

[jake]

There is an update available for this problem (openzwave server down).

If you update to the latest version 13064 then domoticz /Zwave start again super fast.

Yes, this fixed it for me too!

Verstuurd vanaf mijn SM-G970F met Tapatalk