Hi,
I’m trying to add the Monoprice Z-Wave Plus Shock Detector to OpenHAB2 but it’s only recognizing it as an “Unknown Device”. Is there any documentation on how to add devices that are unrecognized to OpenHAB2 device database? I’m not sure if this device is in the latest build as I’m using build #621. The latest build throws a java stack overflow error whenever I try to assign a tty port to my Z-Wave USB stick.
The device is found in HABmin and PaperUI. I’ve tried to reinitialize the device multiple times and it’s seen in the logs but never properly identified like the rest of my devices.
Manufacturer 0190
Type / ID 2003:0307
Firmware Version 16.6
Z-Wave Plus Type HOME_SECURITY_SENSOR
Log shows:
2016-11-29 22:13:09.402 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 0109:2003:0307::16.6
2016-11-29 22:15:18.313 [WARN ] [l.serialmessage.SendDataMessageClass] - NODE 6: Already processed another send data request for this callback Id, ignoring.
2016-11-29 22:15:23.273 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 6: Timeout while sending message. Requeueing - 0 attempts left!
2016-11-29 22:17:16.856 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-11-29 22:17:16.868 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 0109:2003:0307::16.6
2016-11-29 22:25:34.701 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 6: setupNetworkKey useSchemeZero=false
2016-11-29 22:25:34.996 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 0109:2003:0307::16.6
2016-11-29 22:25:35.752 [INFO ] [ommandclass.ZWaveVersionCommandClass] - NODE 6: Command Class BASIC has version 0!
2016-11-29 22:28:06.633 [WARN ] [rialmessage.IsFailedNodeMessageClass] - NODE 6: Is currently marked as failed by the controller!
2016-11-29 22:28:19.360 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 6: setupNetworkKey useSchemeZero=false
2016-11-29 22:28:19.585 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 0109:2003:0307::16.6
2016-11-29 22:28:20.372 [INFO ] [ommandclass.ZWaveVersionCommandClass] - NODE 6: Command Class BASIC has version 0!
Yes, it’s battery powered. I’ve woken it up many times and I can see it pop up in the logs but it doesn’t recognize it. I’ve also let it sit for a day now, usually it would connect by now if it knew what it was.
I’ve had a very similar sensor (probably identical except f/w) from a rebranded vendor that was recognized instantly. But the sensor was faulty as it never seemed to send the off command. Probably could have just worked around that issue easier than this.
Are the nodeX.xml files the ones that handle everything for the zwave binding? I’m not able to export the device above from the website for some reason.
You’re not meant to export it - this won’t really help you unless you want to compile a binding yourself.
I’ll take a look at this tonight, but if it’s not in the database we can add it - can you post the XML for this device that comes from the userdata/zwave folder.
Awesome! Thanks! I’ll clone my vm and give the latest build a try. The last time only Build #621 worked for me and the other threw a stack overflow when I tried to initialize the /dev/ttyACM0 for the zwave binding in the GUI. I saw a thread posted on a similar issue where they recommended an earlier build and that worked. Always love the latest and greatest though!