so I noticed on the OpenZwave github page, "Please note device configuration files for 1.6 and 1.4 are different. If your application is based on OpenZWave version 1.4, the older database is still available but unmaintained at: OpenZWave 1.4 branch, config folder" The update I applied was a pretty ...

sorry forgot to add the domoticz version info. Here you go,

Version: 2020.2
Build Hash: b63341bc0
Compile Date: 2020-04-26 07:47:55

I've got two GE door hinge sensors that have been working flawlessly for several years. As of an update a few weeks back, neither are working. There has been no change to my configuration and both show up in the OZW Control Panel as well as the Hardware and Devices screen. I tried removing one of ...

Thanks for the insights. I'm on an RPi which is horrible for compilation (don't have cross compile set up), but I could move platforms to test this.... Are you working in the github repo, or just doing this on your own?

What version of domoticz are you running? I can't recall seeing anything like what you've seen. Mine just looks dead after pairing.

I'm still wondering if anyone else has gotten this to work yet?

do your switches work to begin with? Mine are non-functioning within Domoticz but will work in the OpenZWave control panel.

it looks like they have a US freq model. Can we revitalize this thread?

http://www.monoprice.com/product?c_id=1 ... 1&format=2

I tried paring this again (secure) with the Domoticz box moved into the garage so that it's local to the node. I ended up with two nodes in the node list, one is dead and the second one is still unsecured. I don't have the same list of Information items as the OP, rather I just have one item which ...

Nope. I just posted that last weekend. For a while I thought it might be the fact that it needed a secure interface but I ended up pairing it with my ZStick by bringing the ZStick into the garage. My belief is that it's not in the current version of the OpenZWave that domoticz is using. This is what ...

I can confirm that I get the same error. I'm running the beta verion 3.5033 at the moment.