Domoticz

I was always on (close to) the latest beta.
I am now on 4.10717 the latest stable.
Because the beta's right after this latest stable gave me a lot of Z-Wave problems. So I stayed reverted back to the latest stable.
Is Z-Wave save and stable to try the latest beta again?
I am using Neo Coolcam PIR's, Power plugs, Water Leakage, Door/Window detectors, Fibaro PIR's, EUROtronic thermostats, Aeotec Wallmote, and Gen5 controller.
Is it without problem to switch to beta?

Mine runs better than before...

Ynx, that looks promising.
I listed my devices, could you comment on those?
Are there any devices that do not work (yet)?

About a year ago I abandoned OpenZwave and replaced it with HomeSeer (because their implementation of Z-Wave is Z-Wave certified and in my opinion the best I've ever seen). I've got a node-red flow that sends it to MQTT and then into Domoticz.

The Node-Red flow simply matches control by device names, eg a light switch called "Kitchen" in Domoticz if turned on the flow will check to see if HomeSeer has a device named "Kitchen" and if so match the Domoticz status.

It's responsive for Motion sensors, remote controls etc.. I don't notice any delay.

The HomeSeer setup sits on a dedicated Raspberry Pi that almost never gets rebooted.

https://shop.homeseer.com/products/home ... -for-hs3-1

EddyG wrote: ↑Thursday 30 January 2020 8:51 I listed my devices, could you comment on those?
Are there any devices that do not work (yet)?

Hard to comment on devices you don't own.
These are the devices I have and they all work fine:

1 AEON Labs ZW090 Z-Stick Gen5 EU
2 AEON Labs DSA03202 Minimote
4 Danfoss Z Thermostat 014G0013
1 Everspring SP816 Outdoor Motion Detector
1 FIBARO System FGBS001 Universal Binary Sensor
5 FIBARO System FGK101 Door Opening Sensor
4 FIBARO System FGMS001 Motion Sensor
9 FIBARO System FGRM222 Roller Shutter Controller 2
1 FIBARO System FGS212 Switch 3kW
5 FIBARO System FGS222 Double Relay Switch 2x1.5kW
6 FIBARO System FGSD002 Smoke Sensor
6 FIBARO System FGWPE/F Wall Plug
1 GreenWave Reality Inc PowerNode 6 port
1 Horstmann (Secure Meters) ASR-ZW Thermostat Receiver
1 Philio Technology Corp PH-PSE02.eu Zipato Indoor Siren
5 Qubino (Goap) ZMNHBA2 Flush 2 Relays
1 Qubino (Goap) ZMNHCDx Flush Shutter
4 Qubino (Goap) ZMNHDA2 Flush Dimmer
5 Qubino (Goap) ZMNHDD1 Flush Dimmer
1 Qubino (Goap) ZMNHND1 Flush 1D relay
2 Qubino (Goap) ZMNHVDx Flush Dimmer 0-10V
7 Remotec ZRC-90
2 Shenzhen Neo Electronics Co Ltd NAS-WR01Z Power plug 12A

I guess it was just in the beginning of OpenZwave 1.6 there were lot's of issues. Most of them are already solved.

Tnx for both the answers, Much appreciated.
Final question: do I have to exclude and include again when I switch to Openzwave 1.6?

I have a Raspberry Pi running the latest stable, with a Razberry board for z-wave, and another PI, with a AEON z-stick 5, running a fork of the latest development, which is partially set up to be a z-wave secondary controller, however at present the replication from primary to secondary does not complete. In the logs on the secondary I see

2020-01-30 11:49:13.638 Status: OpenZWave: Receive Configuration initiated... m_conrollerID 12345
2020-01-30 11:49:13.638 Status: OpenZWave: ReceiveConfiguration ControllerCommand - Starting - from GetAsString
2020-01-30 11:49:16.640 Status: OpenZWave: Type_Notification from Broadcast Node Subtype 1 - controllerID 12345
2020-01-30 11:49:16.640 Status: OpenZWave: Received Broadcast timeout notification from HomeID: 12345 , NodeID: 255 (0xff)
2020-01-30 11:49:16.640 Status: OpenZWave: ControllerCommand - Error - Failed - from GetAsString
2020-01-30 11:49:43.104 Status: ZWave: Stopping Controller command (Timeout!)

(I have added a bit of extra debug information to my fork to try to work out what is going on.)


2020-01-30 11:49:25.940 Status: OpenZWave: Replication to Secondary Controller initiated...
2020-01-30 11:49:25.943 Status: OpenZWave: ControllerCommand - Starting
2020-01-30 11:49:25.952 Status: OpenZWave: ControllerCommand - Waiting
2020-01-30 11:49:30.010 Status: OpenZWave: ControllerCommand - InProgress
2020-01-30 11:49:30.083 Status: OpenZWave: ControllerCommand - InProgress
2020-01-30 11:49:32.948 Status: OpenZWave: ControllerCommand - InProgress
2020-01-30 11:49:33.326 Status: OpenZWave: Node Removed. HomeID: 12345, NodeID: 37 (0x25)
2020-01-30 11:49:34.054 Status: OpenZWave: New Node added. HomeID: 12345, NodeID: 37 (0x25)

The primary controller is NodeID 1, and the secondary is NodeID 37

The secondary shows the z-wave devices in its Setup, but some of the Manufacturer IDs, and Devices Types are 0, and there is little information beyond the fact that they exist, while others have more information, and appear as Devices in Domoticz

In my case it was not necessary to include again. After update not a single issue!!

Tnx, I will switch to beta in the near future.

I had one battery device for which I had to do a Refresh Node because the device was not recognized in Domoticz, but after that all works fine

Refresh node is a good idea to reload the device specific xml.

Please keep us posted, because I've had nothing but problems... I'm on version 4.11476 now, built with a somewhat modified openzwave library (added some extra output like others did) and this works mostly right. But I've had to exclude and include every device I have at least twice, and still need to do an occasional refresh node info of some devices. My system was working fine when openzwave was at 1.4 and like you i installed every beta I could get my hands on, since v1.6 however it has been nothing but problems. I've tried many beta versions since then and they all sucked big time...
- Keeps logging messages on timeouts being reported by devices.
- often there are 5+ seconds delays before a device responds.
- sometimes devices don't respond at all.
- some (sub) devices only get an initial value but never get any updates after that.

The last time I tried installing latest beta was end of last year. I had to restore a backup to get my system up and running again after another day wasted on experimenting: Domoticz kept "dropping" devices (giving a message openzwave found a node to be unresponsive, so it removed it. Next call to this device it complained the node id was unknown. No wonder: you just removed it!). I think it has something to do with nodes being out of direct range of the controller because those are mostly the devices that show issues first in my system.

My advice: create a backup of your system before you upgrade and check that the backup can be restored before you upgrade. But please do let us know your experiences: I'm afraid to try it myself again for some time.

This morning I tried to upgrade from the stable version 4.10717 on a raspberry PI 3B to beta version 4.11666.
Most of the powered devices were almost instantly detected and worked fine. But when I tried to switch on of my FIBARO System FGD212 Dimmer 2, Domoticz crashed. I can set the level, but trying to switch it off, Domoticz crashes.

So I went back to the stable.

Works ok, very stable for several weeks. Had to include some devices again, no big deal

Off topic,: how to get rid of these messages? How to set Location?
OpenZWave: Alarm received (Home Security: Motion Detected at Unknown Location), NodeID: 10 (0x0a)

After solving a few problems, I was ready to make the switch to beta.
I switched, and it did not work. Domoticz crashed.
After a few hours of wasting my time, I discovered this item https://www.domoticz.com/forum/viewtopi ... =6&t=31157
Nice, such a surprise (not really). So I went back to my original setup.
This ambush with Buster was too much for me.
I know I have to upgrade to Buster some time and some of my raspberry's are already on Buster (Octoprint).
I even have a LUN on my Synology ready with Buster, but I have to copy and test a lot of scripts on Buster first, and make a 'Domoticz' version of my Buster setup.
So this ambush with Buster was/is not appreciated.

ben53252642 wrote: ↑Thursday 30 January 2020 9:20 About a year ago I abandoned OpenZwave and replaced it with HomeSeer (because their implementation of Z-Wave is Z-Wave certified and in my opinion the best I've ever seen). I've got a node-red flow that sends it to MQTT and then into Domoticz.

The Node-Red flow simply matches control by device names, eg a light switch called "Kitchen" in Domoticz if turned on the flow will check to see if HomeSeer has a device named "Kitchen" and if so match the Domoticz status.

Hi, Is this documented anywhere?

renerene wrote: ↑Sunday 02 February 2020 10:29 Works ok, very stable for several weeks. Had to include some devices again, no big deal

Off topic,: how to get rid of these messages? How to set Location?
OpenZWave: Alarm received (Home Security: Motion Detected at Unknown Location), NodeID: 10 (0x0a)

don't know how to get rid of the messages; i think they come from inside openzwaveand most likely it requires some compile setting to suppres it. That location is a feature in openzwave not used by domoticz, so there wil most likely not be an option to set it from domoticz either.

ben53252642 wrote: ↑Thursday 30 January 2020 9:20 About a year ago I abandoned OpenZwave and replaced it with HomeSeer (because their implementation of Z-Wave is Z-Wave certified and in my opinion the best I've ever seen). I've got a node-red flow that sends it to MQTT and then into Domoticz.

The Node-Red flow simply matches control by device names, eg a light switch called "Kitchen" in Domoticz if turned on the flow will check to see if HomeSeer has a device named "Kitchen" and if so match the Domoticz status.

It's responsive for Motion sensors, remote controls etc.. I don't notice any delay.

The HomeSeer setup sits on a dedicated Raspberry Pi that almost never gets rebooted.

https://shop.homeseer.com/products/home ... -for-hs3-1

@ben53252642

Can you share the node-red flow and maybe some documentation