Domoticz

Hi guys,

I encountered a weird (at least for me) problem with Raspberry, Domoticz and Z-Wave. My configuration is:

• Raspberry 1, model B, Rev 2
• RaZberry (shield), HW Rev. 2.0, 11/04/2018
• Domoticz V4.10717
• Raspbian Buster Lite (Version 10)
• one Fibaro wall switch FGWPE/F-102

My problem is that after the RPi has booted up and Domoticz is running, most of the times (but not always!) the Fibaro switch on my dashboard is colored red. Switching on and off yields an error message:

Error sending switch command, check device/hardware !

The logfile shows:

Error: OpenZWave: Node not found! (NodeID: 2, 0x02)

Having this problem for many weeks now, I discovered that restarting Domoticz in most cases solves the problem.That's why I have made a (virtual) switch in Domoticz which triggers in Blockly a tiny little bash script containing the command: This enables me to restart Domoticz from a remote location when I see an error while pressing the Fibaro switch.

To narrow down the problem I took a new SD-card, downloaded the latest distro (2020-02-13-raspbian-buster-lite.img) and installed this (with some minor changes in rasp-config). After that I installed Z-Wave using (from z-wave.me): With the webgui I could switch on and off the Fibare switch. After several times rebooting (I used a 'cold' boot) the system keeps functioning fine and as expected.
Then I installed Domoticz using "the easy way" from the wiki: After configuring the RaZberry hardware and the associated switches I could switch on and off a lamp connected to the Fibaro switch.
Rebooting shows the well known error with Fibaro (see above).
Sometimes I can include the node by pressing the button on the switch but this is not a good solution.
I have studied the logfiles (in /var/log: syslog, z-way-server.log, daemon.log and a few more). No clue whatsoever, as far as I could see.
But I consider restarting Domoticz in case of a failure in Z-Wave very unsatisfactory; one could say it is a poor man's solution. What I would like to know:

• are more people encountering this very problem?
• what would you suggest to solve my problem in a proper way?

Thanks in advance!

No one? Am I the only loser with this problem?

OldPensionado wrote: ↑Monday 09 March 2020 16:44 No one? Am I the only loser with this problem?

It would be interesting to find out if you encounter the same issue after updating to a recent Beta. If you have the time and enough confidence in your backups (to return to the stable version and database if no luck with this- or other issues) that is.

Thanks for your advice!
Well, I have a lot of confidence in backups, I've made them very often (using USB Backup).
I upgraded to beta 4.11780 (which number reminds me of the good old VAX...). Shutdown completely, power off, boot up and the same red color showed up in the Fibaro switch.
But I see a few different (and new for me) messages in the log:

• OpenZWave: A Config File Failed to download
• OpenZWave: Type_Notification, NodeID not found internally!. HomeID: 0, NodeID: 255 (0xff)
• (after pressing the switch) Error: OpenZWave: Driver Failed!!

Any ideas?

Raspberry Pi 3 Model B Rev 1.2
Z-Stick Gen5
domoticz beta V4.11780

I installed also fresh domoticz on fresh buster same way as OldPensionado. I use a brand new Z-Stick Gen5. I also got "OpenZWave: A Config File Failed to download". In Domoticz Setup/Hardware/OpenZwaveUSB setup/ Node management/Control panel It's completely blank
Need help! I don't want to run through the whole set up process again I have some nodes hard to reach.

Last stable works! Seems to be a bug in latest beta.

Interesting, I suppose you are referring to the error in OpenZWave about the failure of downloading the config file?

Question: how did you go back to the last stable version (4.10717).