Zwave Vision Shock Sensor ZS5101EU-5

casperleenheer · January 13, 2017, 9:22am

Hi,

I just received my ZS5101 sensor. Include went well. I do see wakeups, but no sensor notifications or tamper alarms. I shook it quite hard, but nothing. I checked my zwave debug log, but there is nothing except the wakeups. Does anyone having a working version of this device?

This is what I see also in the log:

Line 52255: 2017-01-13 11:19:20.153 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 31: Starting initialisation from DONE
Line 52257: 2017-01-13 11:19:20.155 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 31: Incoming command class BATTERY
Line 52258: 2017-01-13 11:19:20.156 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 31: Received Battery Request
Line 52259: 2017-01-13 11:19:20.157 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 31: Battery report value = 80
Line 52261: 2017-01-13 11:19:20.159 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
Line 52262: 2017-01-13 11:19:20.160 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 80
Line 52263: 2017-01-13 11:19:20.162 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Updating channel state zwave:device:b3c28c69:node31:battery-level to 80 [DecimalType]
Line 52269: 2017-01-13 11:19:20.174 [DEBUG] [curityCommandClassWithInitialization] - NODE 31: updating lastSentMessageTimestamp
Line 52270: 2017-01-13 11:19:20.175 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
Line 52271: 2017-01-13 11:19:20.176 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Response processed after 72ms/3690ms.
Line 52274: 2017-01-13 11:19:20.181 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 31: Sending REQUEST Message = 01 09 00 13 1F 02 30 02 25 CC 23 
Line 52280: 2017-01-13 11:19:20.198 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 31: Sent Data successfully placed on stack.
Line 52286: 2017-01-13 11:19:20.215 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 31: SendData Request. CallBack ID = 204, Status = Transmission complete and ACK received(0)
Line 52287: 2017-01-13 11:19:20.216 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 31: Starting initialisation from DONE
Line 52292: 2017-01-13 11:19:25.182 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Timeout while sending message. Requeueing - 1 attempts left!
Line 52293: 2017-01-13 11:19:25.183 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 31: Is sleeping
Line 52294: 2017-01-13 11:19:25.184 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 31: Putting message SendData in wakeup queue.
Line 52325: 2017-01-13 11:20:18.979 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 31: Transaction not completed: node address inconsistent.  lastSent=31, incoming=255
Line 52343: 2017-01-13 11:20:19.070 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 31: Transaction not completed: node address inconsistent.  lastSent=31, incoming=255
Line 52361: 2017-01-13 11:20:19.332 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 31: Transaction not completed: node address inconsistent.  lastSent=31, incoming=255
Line 52379: 2017-01-13 11:20:19.514 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 31: Transaction not completed: node address inconsistent.  lastSent=31, incoming=255
Line 52395: 2017-01-13 11:20:19.598 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 31: Transaction not completed: node address inconsistent.  lastSent=31, incoming=255

casperleenheer · January 16, 2017, 11:00am

I was not sure if the other device is faulty, so I got another one. And it’s the same. I would think it’s not fully supported by OH. I can provide logs etc. What to do to fix this? Any help would be greatly appreciated.

Thanks Casper

sihui · January 16, 2017, 11:36am

Sometimes you have to wake battery operated devices a dozen of times until they get fully initialized.
Do you see a node.xml file generated?

Edit: at least it is in the database:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/442

casperleenheer · January 16, 2017, 11:38am

Oh yes, I have this line:

Line 2934: 2017-01-16 12:01:38.130 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 32: Starting initialisation from DONE

which proves it should be ok, I think. Do you have a working device?

sihui · January 16, 2017, 11:39am

Did you do a secure inclusion (security enabled)?
openHAB2 does not support yet security enabled devices …
Some devices can be included “secure” or “unsecure” …

sihui · January 16, 2017, 11:39am

and the xml file was created?

casperleenheer · January 16, 2017, 11:42am

This is the setting of my controller:

Secure Inclusion Mode
Entry Control Devices
Sets the controller secure inclusion mode
All Devices

casperleenheer · January 16, 2017, 11:44am

And the XML

<node>

  <deviceClass>

    <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>

    <genericDeviceClass>SENSOR_NOTIFICATION</genericDeviceClass>

    <specificDeviceClass>NOTIFICATION_SENSOR</specificDeviceClass>

  </deviceClass>

  <homeId>0xd1c6c9b7</homeId>

  <nodeId>32</nodeId>

  <version>4</version>

  <manufacturer>0x109</manufacturer>

  <deviceId>0x307</deviceId>

  <deviceType>0x2003</deviceType>

  <listening>false</listening>

  <frequentlyListening>false</frequentlyListening>

  <routing>true</routing>

  <security>false</security>

  <beaming>true</beaming>

  <maxBaudRate>40000</maxBaudRate>

  <supportedCommandClasses>

    <entry>

      <commandClass>SENSOR_BINARY</commandClass>

      <binarySensorCommandClass>

        <version>0</version>

        <instances>0</instances>

        <versionSupported>0</versionSupported>

        <isGetSupported>true</isGetSupported>

        <types/>

      </binarySensorCommandClass>

    </entry>

    <entry>

      <commandClass>MANUFACTURER_SPECIFIC</commandClass>

      <manufacturerSpecificCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>2</versionSupported>

        <initSerialNumber>false</initSerialNumber>

        <deviceManufacturer>265</deviceManufacturer>

        <deviceType>8195</deviceType>

        <deviceId>775</deviceId>

      </manufacturerSpecificCommandClass>

    </entry>

    <entry>

      <commandClass>DEVICE_RESET_LOCALLY</commandClass>

      <deviceResetLocallyCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>1</versionSupported>

      </deviceResetLocallyCommandClass>

    </entry>

    <entry>

      <commandClass>BASIC</commandClass>

      <basicCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>1</versionSupported>

        <isGetSupported>true</isGetSupported>

      </basicCommandClass>

    </entry>

    <entry>

      <commandClass>ASSOCIATION_GROUP_INFO</commandClass>

      <associationGroupInfoCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>1</versionSupported>

        <autoSubscribeGroups>

          <int>1</int>

        </autoSubscribeGroups>

      </associationGroupInfoCommandClass>

    </entry>

    <entry>

      <commandClass>VERSION</commandClass>

      <versionCommandClass>

        <version>2</version>

        <instances>1</instances>

        <versionSupported>2</versionSupported>

        <libraryType>LIB_SLAVE_ENHANCED</libraryType>

        <protocolVersion>4.24</protocolVersion>

        <applicationVersion>16.6</applicationVersion>

        <hardwareVersion>2</hardwareVersion>

      </versionCommandClass>

    </entry>

    <entry>

      <commandClass>BATTERY</commandClass>

      <batteryCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>1</versionSupported>

        <batteryLevel>80</batteryLevel>

        <batteryLow>false</batteryLow>

        <isGetSupported>true</isGetSupported>

      </batteryCommandClass>

    </entry>

    <entry>

      <commandClass>APPLICATION_STATUS</commandClass>

      <ZWaveApplicationStatusClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>1</versionSupported>

      </ZWaveApplicationStatusClass>

    </entry>

    <entry>

      <commandClass>ASSOCIATION</commandClass>

      <associationCommandClass>

        <version>2</version>

        <instances>1</instances>

        <versionSupported>2</versionSupported>

        <maxGroups>1</maxGroups>

      </associationCommandClass>

    </entry>

    <entry>

      <commandClass>NO_OPERATION</commandClass>

      <noOperationCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>1</versionSupported>

      </noOperationCommandClass>

    </entry>

    <entry>

      <commandClass>POWERLEVEL</commandClass>

      <powerLevelCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>1</versionSupported>

        <powerLevel>0</powerLevel>

        <powerTimeout>0</powerTimeout>

      </powerLevelCommandClass>

    </entry>

    <entry>

      <commandClass>FIRMWARE_UPDATE_MD</commandClass>

      <firmwareUpdateCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>2</versionSupported>

      </firmwareUpdateCommandClass>

    </entry>

    <entry>

      <commandClass>WAKE_UP</commandClass>

      <WakeUpCommandClass>

        <version>2</version>

        <instances>1</instances>

        <versionSupported>2</versionSupported>

        <targetNodeId>1</targetNodeId>

        <interval>21750</interval>

        <minInterval>500</minInterval>

        <maxInterval>605000</maxInterval>

        <defaultInterval>21750</defaultInterval>

        <intervalStep>250</intervalStep>

        <lastWakeup>2017-01-16 11:01:29.787 UTC</lastWakeup>

        <isGetSupported>true</isGetSupported>

      </WakeUpCommandClass>

    </entry>

    <entry>

      <commandClass>ALARM</commandClass>

      <alarmCommandClass>

        <version>4</version>

        <instances>1</instances>

        <versionSupported>4</versionSupported>

        <alarms>

          <entry>

            <alarmType>BURGLAR</alarmType>

            <alarmState>

              <alarmType>BURGLAR</alarmType>

              <reportedEvents>

                <int>2</int>

                <int>3</int>

              </reportedEvents>

              <outer-class reference="../../../.."/>

            </alarmState>

          </entry>

        </alarms>

        <v1Supported>false</v1Supported>

        <isGetSupported>true</isGetSupported>

      </alarmCommandClass>

    </entry>

    <entry>

      <commandClass>ZWAVE_PLUS_INFO</commandClass>

      <zwavePlusCommandClass>

        <version>1</version>

        <instances>1</instances>

        <versionSupported>2</versionSupported>

        <zwPlusVersion>1</zwPlusVersion>

        <zwPlusRole>6</zwPlusRole>

        <zwPlusNodeType>0</zwPlusNodeType>

        <zwPlusDeviceType>0xc07</zwPlusDeviceType>

        <zwPlusInstallerIcon>0xc07</zwPlusInstallerIcon>

        <isGetSupported>true</isGetSupported>

      </zwavePlusCommandClass>

    </entry>

  </supportedCommandClasses>

  <securedCommandClasses/>

  <associationGroups>

    <entry>

      <int>1</int>

      <associationGroup>

        <index>1</index>

        <name>Lifeline</name>

        <profile1>0x0</profile1>

        <profile2>0x1</profile2>

        <commands>

          <commandClass>BATTERY</commandClass>

          <commandClass>DEVICE_RESET_LOCALLY</commandClass>

          <commandClass>BASIC</commandClass>

          <commandClass>ALARM</commandClass>

        </commands>

        <associations/>

      </associationGroup>

    </entry>

  </associationGroups>

  <nodeNeighbors>

    <int>1</int>

    <int>3</int>

    <int>8</int>

    <int>11</int>

    <int>14</int>

    <int>15</int>

    <int>22</int>

    <int>28</int>

  </nodeNeighbors>

  <lastSent>2017-01-16 11:01:35.196 UTC</lastSent>

  <lastReceived>2017-01-16 11:01:35.261 UTC</lastReceived>

</node>

sihui · January 16, 2017, 11:58am

No, I don’t have any “secure” devices, so I’m not a lot of a help here.

That looks good, so the device was added without security.

That’s exactly the device in the database, so that’s okay too.

Did you manually define your items file? I’ve made the experience that this does not work for all zwave devices, f.e. I had to use PaperUI/HABmin to setup the items for my FGR222, with text files it did not work …

casperleenheer · January 16, 2017, 12:00pm

No, I created them through Paper UI. If I look in the zwave.log this is what I see:

Line 2918: 2017-01-16 12:01:38.116 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 32: Starting initialisation from DONE
Line 2925: 2017-01-16 12:01:38.121 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Went to sleep
Line 2926: 2017-01-16 12:01:38.122 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Is sleeping
Line 2927: 2017-01-16 12:01:38.123 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
Line 2928: 2017-01-16 12:01:38.124 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 32: Response processed after 45ms/4598ms.
Line 2933: 2017-01-16 12:01:38.129 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Application Command Request (ALIVE:DONE)
Line 2934: 2017-01-16 12:01:38.130 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 32: Starting initialisation from DONE
Line 2936: 2017-01-16 12:01:38.131 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Incoming command class WAKE_UP
Line 2937: 2017-01-16 12:01:38.132 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Received Wake Up Request
Line 2938: 2017-01-16 12:01:38.134 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Received WAKE_UP_NOTIFICATION
Line 2939: 2017-01-16 12:01:38.135 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Is awake with 0 messages in the wake-up queue.
Line 2941: 2017-01-16 12:01:38.136 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveWakeUpEvent
Line 2945: 2017-01-16 12:01:39.138 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: No more messages, go back to sleep
Line 2946: 2017-01-16 12:01:39.139 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
Line 2950: 2017-01-16 12:01:39.144 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 32: Sending REQUEST Message = 01 09 00 13 20 02 84 08 25 80 EE 
Line 2956: 2017-01-16 12:01:39.166 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 32: Sent Data successfully placed on stack.
Line 2957: 2017-01-16 12:01:44.146 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 32: Timeout while sending message. Requeueing - 2 attempts left!
Line 2958: 2017-01-16 12:01:44.147 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Is sleeping
Line 2959: 2017-01-16 12:01:44.148 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Putting message SendData in wakeup queue.
Line 2965: 2017-01-16 12:01:46.502 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 32: SendData Request. CallBack ID = 128, Status = Transmission complete, no ACK received(1)
Line 2969: 2017-01-16 12:01:46.506 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 32: WAKE_UP_NO_MORE_INFORMATION. Treated as ACK.
Line 2971: 2017-01-16 12:01:46.507 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Went to sleep
Line 2972: 2017-01-16 12:01:46.508 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 32: Is sleeping
Line 2973: 2017-01-16 12:01:46.508 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
Line 2989: 2017-01-16 12:04:48.316 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3005: 2017-01-16 12:04:50.518 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3021: 2017-01-16 12:04:52.724 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3037: 2017-01-16 12:04:54.913 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3053: 2017-01-16 12:04:57.118 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3069: 2017-01-16 12:04:59.322 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3085: 2017-01-16 12:05:01.524 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3101: 2017-01-16 12:05:03.732 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3119: 2017-01-16 12:05:04.338 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3134: 2017-01-16 12:05:04.412 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3147: 2017-01-16 12:05:04.430 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3163: 2017-01-16 12:05:04.511 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3177: 2017-01-16 12:05:04.526 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3193: 2017-01-16 12:05:05.933 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3209: 2017-01-16 12:05:08.140 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3225: 2017-01-16 12:05:10.366 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255
Line 3241: 2017-01-16 12:05:12.554 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 32: Transaction not completed: node address inconsistent.  lastSent=32, incoming=255

So no CommandClass whatever…

sihui · January 16, 2017, 12:11pm

Strange …
Last idea: Association group “Lifeline” is set to your controller?
You should at least see these command classes:

casperleenheer · January 16, 2017, 12:15pm

I can’t set any association for this device… but I have a Sensor, Alarm and Battery item defined.

sihui · January 16, 2017, 3:25pm

<entry>
  <int>1</int>
  <associationGroup>
    <index>1</index>
    <name>Lifeline</name>
    <profile1>0x0</profile1>
    <profile2>0x1</profile2>

Strange … from your xml it looks like it is set that way.
But you may be right, in the database no association groups are defined.
Sorry, no more ideas.

casperleenheer · January 17, 2017, 3:20pm

Maybe this is for Chris:

The fact I can’t set any associations or a lifeline, can that be the cause. I recall in the past for some devices I had to associate to the controller to get any of the reports. Can this be the case: the sensor is sending out it reports, but the controller is not picking them up. From the manual:

For “Association” :removing the cover of the ZS 5101 to get into the “Awake”
mode, then put the Z-Wave™ Interface Controller into “Association”, and following
its instruction to associate the ZS 5101 with other device. Close the cover back after
“association” done, afterward the ZS 5101 will get into “Sleep” mode for power
saving. Support one association group (5 nodes).

Again there is no Association Group in the definition of this device. How to put the controller into “Association”??