Everspring evr_sp814 inclusion in openhab2

Setup, Configuration and Use Beginners
,
1

My setup is a pi3, raspbian, openhab2 through apt beta release channel and an aeotec z-stick gen5.

I have included an Everspring evr_sp814 into the zwave network and have gotten an xml for it after about 6 hours of waiting (included below).

PaperUI and habmin gives it as an unkown device (Z-Wave Node 5 (0060:0001:0002:1.2) Unknown Device). Should it be included into the zwave database or am I doing something wrong?

<node>
  <deviceClass>
    <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
    <genericDeviceClass>BINARY_SENSOR</genericDeviceClass>
    <specificDeviceClass>ROUTING_SENSOR_BINARY</specificDeviceClass>
  </deviceClass>
  <homeId>0xf6ab9cce</homeId>
  <nodeId>5</nodeId>
  <version>3</version>
  <manufacturer>0x60</manufacturer>
  <deviceId>0x2</deviceId>
  <deviceType>0x1</deviceType>
  <listening>false</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <nodeInformationFrame>
    <commandClass>SENSOR_BINARY</commandClass>
    <commandClass>VERSION</commandClass>
    <commandClass>MANUFACTURER_SPECIFIC</commandClass>
    <commandClass>ASSOCIATION</commandClass>
    <commandClass>WAKE_UP</commandClass>
    <commandClass>BATTERY</commandClass>
    <commandClass>CONFIGURATION</commandClass>
    <commandClass>BASIC</commandClass>
  </nodeInformationFrame>
  <supportedCommandClasses>
    <entry>
      <commandClass>MANUFACTURER_SPECIFIC</commandClass>
      <manufacturerSpecificCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>1</versionSupported>
      </manufacturerSpecificCommandClass>
    </entry>
    <entry>
      <commandClass>ASSOCIATION</commandClass>
      <associationCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>2</versionSupported>
        <configAssociations/>
        <maxGroups>2</maxGroups>
      </associationCommandClass>
    </entry>
    <entry>
      <commandClass>WAKE_UP</commandClass>
      <WakeUpCommandClass>
        <version>2</version>
        <instances>1</instances>
        <versionSupported>2</versionSupported>
        <targetNodeId>1</targetNodeId>
        <interval>3600</interval>
        <minInterval>60</minInterval>
        <maxInterval>16777215</maxInterval>
        <defaultInterval>3600</defaultInterval>
        <intervalStep>1</intervalStep>
        <lastWakeup>2016-08-10 20:03:52.541 UTC</lastWakeup>
        <isGetSupported>true</isGetSupported>
      </WakeUpCommandClass>
    </entry>
    <entry>
      <commandClass>BASIC</commandClass>
      <basicCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>1</versionSupported>
        <isGetSupported>true</isGetSupported>
      </basicCommandClass>
    </entry>
    <entry>
      <commandClass>CONFIGURATION</commandClass>
      <configurationCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>1</versionSupported>
        <configParameters/>
      </configurationCommandClass>
    </entry>
    <entry>
      <commandClass>SENSOR_BINARY</commandClass>
      <binarySensorCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>1</versionSupported>
        <isGetSupported>true</isGetSupported>
        <types/>
      </binarySensorCommandClass>
    </entry>
    <entry>
      <commandClass>BATTERY</commandClass>
      <batteryCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>1</versionSupported>
        <batteryLevel>100</batteryLevel>
        <batteryLow>false</batteryLow>
        <isGetSupported>true</isGetSupported>
      </batteryCommandClass>
    </entry>
    <entry>
      <commandClass>VERSION</commandClass>
      <versionCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>1</versionSupported>
        <libraryType>LIB_CONTROLLER_BRIDGE</libraryType>
        <protocolVersion>2.64</protocolVersion>
        <applicationVersion>1.2</applicationVersion>
      </versionCommandClass>
    </entry>
    <entry>
      <commandClass>NO_OPERATION</commandClass>
      <noOperationCommandClass>
        <version>1</version>
        <instances>1</instances>
        <versionSupported>1</versionSupported>
      </noOperationCommandClass>
    </entry>
  </supportedCommandClasses>
  <securedCommandClasses/>
  <nodeNeighbors>
    <int>1</int>
  </nodeNeighbors>
  <lastSent>2016-08-10 20:03:52.792 UTC</lastSent>
  <lastReceived>2016-08-10 20:03:53.351 UTC</lastReceived>
</node>
2

The device needs updating in the online database and then adding to the binding. I’ll do this tonight as I think all that’s needed is to upload your XML.

3

Ok, thank you

4

This should be updated in tonights binding.

5

Chris, I was wondering if you could include the Merten dual pole switch as well, although I didn’t have time to figure out the details on how the config params work(what they do). I compiled with the test xml, and it reported max 5 nodes in group 1.

6

Just to be clear - is this the one you mean?

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/399

7

Yes!

8

Done.

9

Thanks!