After discussing this with the author of the adjusted xml files for the FGRGBW-442 he states that the XML-files aren't finished and need further work. That's probably the reason not all devices are being found. He also states that open-zwave might only support version 2 of the command class color ...

When adding the Fibaro RGBW Controller 2 to Domoticz, I'm missing some devices. The device needed to switch on/off/dim the light is missing. I tried all devices that were found, but these are not working. Just the following devices are discovered: RGBW Controller 2.PNG I want to switch 12v halogen ...

Same result for me, have you already tried the following steps?
https://www.domoticz.com/forum/viewtopi ... 26#p227691

I'm using Domoticz 4.97 and am trying to include the smart implant. Including doesn't work for me. Can anyone tell me if this can be caused by my missing configuration around the xml and open z-wave part? Or should including always work? The manual states there is a color led on the device, but for ...

Another reboot showed the following errors: 2018-12-09 23:33:00.002 EventSystem thread seems to have ended unexpectedly 2018-12-09 23:33:00.002 Error: Scheduler thread seems to have ended unexpectedly 2018-12-09 23:33:00.002 Error: Z-Stick hardware (2) thread seems to have ended unexpectedly And ...

I'm using Domoticz 4.97 and using only the Z-Wave functionality with a Aeotec Z-Stick Gen 5. This has been running for a year now and worked fine. I haven't changed anything lately, no new devices have been added for weeks. Suddenly out of the blue, since this evening, I'm receiving timeout ...

For now I have not found a way to convince the sensor to report its battery-status voluntary, other then by pressing the action-button. The Aeon Labs Helpdesk has confirmed the devices do not communicate their battery level. They stated a firmware update is required. Unfortunately they won't ...

OZW is sending all of this sensor's messages correctly to Domoticz, according to me, that's not the issue. This is what's happening: - Users add the sensor to their network and Domoticz shows the battery level. - From then onwards, the module always sleeps and only sends 'open' or 'closed' messages ...

My prediction is that you will see the battery level for the next few days and then it will disappear. The sensors do not send their battery level again without pushing the action button. Months later, the sensors will start sending out the low battery level message every time you open or close the ...

Update: I discovered this module DOES send out a battery message. But only when the low battery level is reached and when this low battery message is enabled. This is the message I saw in one of the Aeotec Z-Stick Gen 5 firmware upgrade tools: 08:33:31.826: Received: 008 - COMMAND_CLASS_BATTERY ...

Egregius wrote:Do you have polling enabled? If yes, try disable it.
I only see higher retries on 2 nodes where I have polling enabled. All other nodes have retries < 5.

No, I don't have polling enabled. Added this information to the first post.

My current z-wave setup is not as reliable as I hoped for when choosing for z-wave. 4 of the highlighted nodes in the attached screenshot are Fibaro Dimmer 2 modules. All of these are located within 2 meters of the Aeon Labs z-stick gen 5, but there are thin walls in between. The transmitter is ...

I've had a discussion by email with Aeotec about these door window sensors. It turns out that these modules do not send battery information when waking up (when a door is opened or closed). Also, setting wake up times does not help, because the module will still not send the battery information ...

I also got my Aeon Labs ZW112 door/window sensor 6 working, but have issues showing the battery level. First the battery level was available, but after a couple of days it didn't show anymore. I tried setting a wake up time, enabling low battery setting, even tried polling data, but Domoticz doesn't ...