Zwave OH2: Benext Door Sensor not properly initalized

Add-ons Bindings
1

Ok, so I’m migrating my OH2 from Zwave 1.9 to 2.0. Most devices are detected properly, as they were with the zwave 1.9 binding, but my Benext Door Sensor is not.
It’s referenced here in Chris’ database (great job btw!).

For reference, this is the zwave node xml file on disk where is was working properly:

<node>
  <deviceClass>
    <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
    <genericDeviceClass>BINARY_SENSOR</genericDeviceClass>
    <specificDeviceClass>NOT_USED</specificDeviceClass>
  </deviceClass>
  <homeId>0xd200d959</homeId>
  <nodeId>29</nodeId>
  <version>4</version>
  <name>Deur hobbykamer</name>
  <location>Hobbykamer</location>
  <manufacturer>0x8a</manufacturer>
  <deviceId>0x101</deviceId>
  <deviceType>0x4</deviceType>
  <listening>false</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <healState>DONE @ 2017-01-02T09:11:20+0000</healState>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>

This is the first part of the node file as written by the zwave 2.x addon binding:

<node>
  <deviceClass>
    <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
    <genericDeviceClass>BINARY_SENSOR</genericDeviceClass>
    <specificDeviceClass>NOT_USED</specificDeviceClass>
  </deviceClass>
  <homeId>0xd200d959</homeId>
  <nodeId>29</nodeId>
  <version>4</version>
  <manufacturer>0x8a</manufacturer>
  <deviceId>0x101</deviceId>
  <deviceType>0x4</deviceType>
  <listening>false</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>

Chris’ database site adds support for 0004:0100 while my device returns 004:0101. That’s a mismatch and the probable cause that my device was not detected. I assumed zwave devices detected in 1.9 would have been migrated to 2.0, can anyone confirm that?

@chris: How can I get it added? Update the database? Add a new entry (a copy) with deviceId 0x101? Do you maybe require my zwave logs?

2

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

Secondly, many devices use multiple sets of deviceType and deviceId as explained above in the device identification section. Again, uploading a new XML file will allow this to be resolved.

3

Thank you. If only I’d read the whole page I wouldn’t have had to waste anyone’s precious time.

4

No problem at all, there is some spare time left for answers :grinning:

5

I think I require Chris to give me access to add the node xml? I’m missing the “Add” button after logging in with the newly created account. It gives me “Please note that you must contact the administrator to get edit rights to the database once you have registered.” My accountname is “randomname872634”.

6

Yes, just send him an email to the adress mentioned on the database page.
But from other posts I know he is on holiday, so be patient with him :slight_smile:

7

Thanks for the update. I already sent him a DM via this forum. Good to know he’s on holiday, I’ll hold my horses :wink:

8

Would it by possible to get my device added to the database while Chris is unvailable? Would this require me to manually build the zwave binding?

1 Like
9

Ok, so I’ve got my change in the database, but how do I get it included with the next snapshot build of the zwave binding? Do I require @chris to approve it?

10

Yes - I’ll look to do an update tonight.

11

That’s great, thx!

12

For the record. My Benext Door Sensor is now properly detected, running the snapshot version of everything (I couldn’t figure out how to run the snapshot of the Zwave 2.x binding only).
A note: I had to delete the Thing and let it be re-discovered before it would update the Item’ values properly.