I’m running OH3 on a RPi.
I have been trying to couple z-wave devices to my setup, using an Aeotec Z-stick Gen5+ as a controller. This has been successful for 2 (Aeotec MultiSensor 6 and Neo Coolcam smartplug) devices. However, the third device is detected but the thing type is not recognized. In thing configuration i see the following: Z-Wave Node 002 (008A:0006:0200:1.9)
If I enable the debug logging I see the following log showing up:
2021-04-05 14:02:17.945 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 008A:0006:0200::1.9
I’m rather new to OH3, so please let me know if I missed some crucial information in my help request.
Thanks for your support
Thanks for the quick reply. I will try to add this device to the database.
If I read the guide correctly I should make a ticket after registry to the database. I’m waiting now on approval.
Ill post here if I added the device.
I have received access to the database. I tried to add a new device and I get an error as you predicted, but I can’t find the device in the database. I used attached xml file to import the information: network_ce0cf1f8__node_2.xml (6.8 KB)
The device likely is a newer device with new features.
I tried locating Z-Wave association group & config parameters on the device but they are not published on the zwave alliance’s site. Hopefully the vendor has another document somewhere.
There are manual instructions are in the README but basically, you uninstall the zwave binding and place the snapshot jar file in the addons directory. OH automatically installs it but is does not appear ih the UI list of installed bindings. be sure to remove the manually installed addon & add the binding back before upgrading OH.
You are welcome. Currently I am a very frustrated Z-Wave user. Yesterday I received 2 products not yet in the database. I entered one last night and will test on a modified binding but there is no stable release that can be used to test an officially built binding.
I am currently weighing my personal options, unfortunately.