Enerwave ZWN-RSM2-PLUS "Unknown Device" (011A:0111:0606:5.12)

Add-ons Bindings
1

Hello everyone.

I’ve searched in other topics but none of them has the same issues.

I’m running openHab 2.4.0 and Z-Wave binding 2.4.0 on Ubuntu 16.04; I have an Aeotec USB Z-Stick Gen5 as my Z-Wave controller with 2 Vision relay micro switches and all of them works perfectly.

Now I’m adding a new Enerwave ZWN-RSM2-PLUS, but I can’t get it recognized by openHab. The new device is shown as: Z-Wave Node 004 (011A:0111:0606:5.12) Unknown Device

I don’t know if this my be a silly question, but when zwave binding is in discovery proccess ¿is the manufacturer id case sensitive?, because this is the only strange thing that I see (id: 011A with uppercase ‘A’). ¿Or maybe the firmware version (5.12) is not on the device database?.

There are 7 files on my /var/lib/openhab2/zwave folder:

-rw-r--r-- 1 openhab openhab  1887 Jul 13 02:48 network_c4cb8e3a__node_1.xml
-rw-r--r-- 1 openhab openhab  5838 Jul 13 02:48 network_c4cb8e3a__node_2.xml
-rw-r--r-- 1 openhab openhab  8416 Jul 13 02:48 network_c4cb8e3a__node_3.xml
-rw-r--r-- 1 openhab openhab 12194 Jul 13 13:15 network_c4cb8e3a__node_4.xml
-rw-r--r-- 1 openhab openhab  1298 Apr  8 02:00 node1.xml
-rw-r--r-- 1 openhab openhab  4828 Apr  8 21:16 node2.xml
-rw-r--r-- 1 openhab openhab  7314 Apr  8 21:16 node3.xml

node1.xml is from my z-stick, node2.xml and node3.xml are from my Vision switches but there is no node4.xml

In the brochure with the installation instructions that came with my device, there is an URL of a file on GitHub to install it on SmartThings that might be of some use: link

I have the debug log, but I can’t add it to this post.

Thanks ind advanced

2

This device type and id were added in April, so you need to upgrade to the latest 2.5 zwave snapshot binding:
https://ci.openhab.org/job/openHAB2-Bundles/org.openhab.addons.bundles$org.openhab.binding.zwave/
Uninstall the old 2.4 binding, drop the jar from the link in your addons folder, a restart of openHAB may be needed.

3

Awesome!

Your solution worked like a charm, but… I had to manually add another dependency (xstream-1.4.7_1.jar) as stated on this post:

Thank you very much! :smiley:

1 Like