Strips - The invisible door/window sensor - Sensative

Thanks syncing works now.

Hopefully the sensor will work soon with Indigo.

Indigo Z-Wave Version: 1.0.363
Node ID: 42
Model: Routing Slave
Model ID: 00030003
Manufacturer: Unknown
Manufacturer ID: 019A
Protocol Version: 4.05
Application Version: 0.04
Model Definition Version: 0
Library Type: 6
Class Name: Routing Slave
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 80v1 30v1 84v2 85v1 86v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 2, 4, 7, 10, 15, 16
Associations: 1:[1]
Config Values: - none -

Please add support.

Hi, any update on the adding of these sensors, bought two of them yesterday.

Thanks

[jay (support)]

No update and no ETA.

bump - these strips have been on the market now for quite some while... please!

Any progress on this?

[matt (support)]

High priority for v7. Stay tuned...

Started to test my Sensative Strips now with the Z-Wave plugin 2.0.40.

When using the Aeon Labs S2 USB stick the inclusion into the controller just stops:
Z-Wave Debug SENT enterInclusionMode: 01 04 00 4A 81 30
Z-Wave Debug RCVD enterInclusionMode: 06 (ACK)
Z-Wave started controller inclusion mode
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 02 01 00 00 B1
Z-Wave Debug RCVD inclusionMode node found: 01 07 00 4A 02 02 00 00 B2
Z-Wave Debug RCVD inclusionMode adding slave node: 01 16 00 4A 02 03 2F 0F 04 07 01 5E 86 72 30 70 71 5A 85 59 80 84 73 EA
Z-Wave Debug RCVD inclusionMode node respondCmds: 5E 86 72 30 70 71 5A 85 59 80 84 73

And nothing more here.

However, in my DEV environment with same software setup BUT with the Aeon Labs S5 Gen5 USB stick inclusion into controller works fine as well as syncing into Indigo.
State changes works fine as well.

Are newer Z-Wave PLUS devices sometimes not compatible with older Gen 2 (and Gen 1) controllers due to the usage of newer command classes?

[matt (support)]

I believe it should add using NWI (Z-Stick plugged into Mac and Indigo starting the inclusion) with either the S2 or G5 Z-Stick. It is possible there is some incompatibility between the Sensative Strip and the S2 Z-Stick, although Z-Wave+ devices are in theory backwards compatible with non-plus modules (including controllers, like the Z-Stick).

If you add it the old manual way (removing the Z-Stick and using the button) does it then work in Indigo (after the sync)?

If you add it the old manual way (removing the Z-Stick and using the button) does it then work in Indigo (after the sync)?

Nope, same issue independent of NWI method or the old classic method for the S2 stick.
As soon as I do NWI (or old classic method) with the S5 stick all goes smoothly.

I was anyway planning to move over to the S5 stick during Christmas but I might start doing it this or next weekend in order to get all the testing we are doing for Qubino devices and other devices I have in the "into PROD environment"-queue...

I'm using Strips with a Z2 ok.

The only issue was understanding the instructions re the magnets so I made a little guide sheet which I'll attach here later for anyone's future reference.


Sent from my iPhone using Tapatalk

Soon strange that you get it to work with Aeon Labs S2 stick while I can't. I have no issues with the S5 stick at all. Works at first attempt.
No matter if I do the "old" inclusion method with S2 or the newer NWI method.
I can include the device into the controller but the sync always times out when using the S2 stick.

Here is the full inclusion log with the S2 stick and as you can see it takes almost 1 minute before it finds the node:

Code: Select all

2016-12-03 13:33:23.232   Z-Wave Debug   SENT enterInclusionMode: 01 04 00 4A 81 30
2016-12-03 13:33:23.235   Z-Wave Debug   RCVD enterInclusionMode: 06 (ACK)
2016-12-03 13:33:23.237   Z-Wave   started controller inclusion mode
2016-12-03 13:33:23.238   Z-Wave Debug   RCVD inclusionMode ready: 01 07 00 4A 01 01 00 00 B2
2016-12-03 13:34:16.794   Z-Wave Debug   RCVD inclusionMode node found: 01 07 00 4A 01 02 00 00 B1
2016-12-03 13:34:16.914   Z-Wave Debug   RCVD inclusionMode adding slave node: 01 16 00 4A 01 03 34 0F 04 07 01 5E 86 72 30 70 71 5A 85 59 80 84 73 F2
2016-12-03 13:34:16.915   Z-Wave Debug   RCVD inclusionMode node respondCmds: 5E 86 72 30 70 71 5A 85 59 80 84 73
2016-12-03 13:34:48.986   Z-Wave Debug   RCVD inclusionMode node added: 01 07 00 4A 01 05 34 00 82
2016-12-03 13:34:48.987   Z-Wave Debug   SENT exitInclusionMode: 01 04 00 4A 05 B4
2016-12-03 13:34:48.989   Z-Wave Debug   RCVD exitInclusionMode: 06 (ACK)
2016-12-03 13:34:49.063   Z-Wave Debug   RCVD inclusionMode finished: 01 07 00 4A 01 06 34 00 81
2016-12-03 13:34:49.065   Z-Wave Debug   SENT getNodeProtocolInfo: 01 04 00 41 34 8E
2016-12-03 13:34:49.074   Z-Wave Debug   RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A
2016-12-03 13:34:49.075   Z-Wave Debug   . .  getNodeProtocolInfo:       node 052, class name: Notification Sensor
2016-12-03 13:34:49.076   Z-Wave Debug   . .  getNodeProtocolInfo:            class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
2016-12-03 13:34:49.076   Z-Wave Debug   . .  getNodeProtocolInfo:         base class command: 00
2016-12-03 13:34:49.077   Z-Wave Debug   . .  getNodeProtocolInfo:   supported class commands: 20 80 84 85 86 30 70 71 72 73 59 5A 5E
2016-12-03 13:34:49.078   Z-Wave Debug   . .  getNodeProtocolInfo:     encrypt class commands:
2016-12-03 13:34:49.078   Z-Wave Debug   . .  getNodeProtocolInfo:                   features: routing, battery, beaming, waking
2016-12-03 13:34:49.079   Z-Wave   controller included module: 052 - Notification Sensor
2016-12-03 13:34:49.083   Z-Wave   stopped controller inclusion mode

And here is the sync attempt (tried MANY times and I always wake it up properly according to the instructions from Sensative's own video at Sensative Strips Wakeup video

Code: Select all

2016-12-03 13:34:59.912   Z-Wave   Syncing - started for "052 - Notification Sensor"
2016-12-03 13:34:59.926   Z-Wave Debug   SENT getNodeNeighbors: 01 06 00 80 34 01 01 4D
2016-12-03 13:34:59.933   Z-Wave Debug   RCVD getNodeNeighbors: 01 20 01 80 04 66 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 28 10 18 00 02 00 03 00 1F
2016-12-03 13:34:59.934   Z-Wave Debug   . .  getNodeNeighbors: nodeId 052, neighbors: 3, 10, 11, 14, 15, 66, 172, 174, 181, 188, 189, 202, 217, 218
2016-12-03 13:34:59.935   Z-Wave   Syncing - retrieved module neighbors list: 3, 10, 11, 14, 15, 66, 172, 174, 181, 188, 189, 202, 217, 218
2016-12-03 13:34:59.935   Z-Wave   Syncing - assigning return route to "052 - Notification Sensor"
2016-12-03 13:34:59.936   Z-Wave Debug   SENT assignReturnRoute: 01 05 00 46 34 01 89
2016-12-03 13:34:59.972   Z-Wave Debug   RCVD assignReturnRoute: 01 04 01 46 01 BD
2016-12-03 13:35:02.406   Z-Wave Debug   RCVD assignReturnRoute: 01 05 00 46 01 01 BC
2016-12-03 13:35:02.408   Z-Wave Debug   . .  assignReturnRoute: node 052, success 0
2016-12-03 13:35:02.408   Z-Wave Error   Syncing - failed to assign return route
2016-12-03 13:35:02.409   Z-Wave Debug   SENT requestNodeInfo: 01 06 00 60 34 24 9B 12
2016-12-03 13:35:04.192   Z-Wave Debug   RCVD requestNodeInfo: 01 06 00 49 81 00 00 31
2016-12-03 13:35:04.193   Z-Wave Debug   RCVD requestNodeInfo: failed (module asleep or doesn't support command)
2016-12-03 13:35:04.194   Z-Wave Error   Syncing - failed
2016-12-03 13:35:04.426   Z-Wave Error   No response from "052 - Notification Sensor". Module might be asleep, or is unreachable.

I have tested with quite many exclusions and inclusions but all the time the same result as shown in the logs above.
I do the reset of the strip according to Sensative's video for reset instructions. and I can see that it resets.

So strange that it just goes without problems with the S5 stick.

Here is the same strip when including it to my Aeon Labs S5 Gen5 controller:

Code: Select all

2016-12-03 14:40:04.766   Z-Wave Debug   SENT enterInclusionMode: 01 04 00 4A C1 70
2016-12-03 14:40:04.769   Z-Wave Debug   RCVD enterInclusionMode: 06 (ACK)
2016-12-03 14:40:04.769   Z-Wave   started controller inclusion mode
2016-12-03 14:40:04.770   Z-Wave Debug   RCVD inclusionMode ready: 01 07 00 4A 01 01 00 00 B2
2016-12-03 14:40:13.027   Z-Wave Debug   RCVD inclusionMode node found: 01 07 00 4A 01 02 00 00 B1
2016-12-03 14:40:13.260   Z-Wave Debug   RCVD inclusionMode adding slave node: 01 16 00 4A 01 03 09 0F 04 07 01 5E 86 72 30 70 71 5A 85 59 80 84 73 CF
2016-12-03 14:40:13.261   Z-Wave Debug   RCVD inclusionMode node respondCmds: 5E 86 72 30 70 71 5A 85 59 80 84 73
2016-12-03 14:40:13.654   Z-Wave Debug   RCVD inclusionMode node added: 01 07 00 4A 01 05 09 00 BF
2016-12-03 14:40:13.655   Z-Wave Debug   SENT exitInclusionMode: 01 04 00 4A 05 B4
2016-12-03 14:40:13.656   Z-Wave Debug   RCVD exitInclusionMode: 06 (ACK)
2016-12-03 14:40:13.732   Z-Wave Debug   RCVD inclusionMode finished: 01 07 00 4A 01 06 09 00 BC
2016-12-03 14:40:13.733   Z-Wave Debug   SENT getNodeProtocolInfo: 01 04 00 41 09 B3
2016-12-03 14:40:13.736   Z-Wave Debug   RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A
2016-12-03 14:40:13.738   Z-Wave Debug   . .  getNodeProtocolInfo:       node 009, class name: Notification Sensor
2016-12-03 14:40:13.739   Z-Wave Debug   . .  getNodeProtocolInfo:            class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
2016-12-03 14:40:13.739   Z-Wave Debug   . .  getNodeProtocolInfo:         base class command: 00
2016-12-03 14:40:13.739   Z-Wave Debug   . .  getNodeProtocolInfo:   supported class commands: 20 80 84 85 86 30 70 71 72 73 59 5A 5E
2016-12-03 14:40:13.739   Z-Wave Debug   . .  getNodeProtocolInfo:     encrypt class commands:
2016-12-03 14:40:13.741   Z-Wave Debug   . .  getNodeProtocolInfo:                   features: routing, battery, beaming, waking
2016-12-03 14:40:13.741   Z-Wave   controller included module: 009 - Notification Sensor
2016-12-03 14:40:13.744   Z-Wave   stopped controller inclusion mode

And here is the sync log that works at first attempt without problems:

Code: Select all

2016-12-03 14:40:22.109   Z-Wave Debug   intiatingSyncUI (timeout in 1500 seconds)
2016-12-03 14:40:23.890   Z-Wave   Syncing - started for "009 - Notification Sensor"
2016-12-03 14:40:23.891   Z-Wave Debug   SENT getNodeNeighbors: 01 06 00 80 09 01 01 70
2016-12-03 14:40:23.903   Z-Wave Debug   RCVD getNodeNeighbors: 01 20 01 80 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16
2016-12-03 14:40:23.903   Z-Wave Debug   . .  getNodeNeighbors: nodeId 009, neighbors: 4, 7
2016-12-03 14:40:23.903   Z-Wave   Syncing - retrieved module neighbors list: 4, 7
2016-12-03 14:40:23.904   Z-Wave   Syncing - assigning return route to "009 - Notification Sensor"
2016-12-03 14:40:23.904   Z-Wave Debug   SENT assignReturnRoute: 01 05 00 46 09 01 B4
2016-12-03 14:40:23.926   Z-Wave Debug   RCVD assignReturnRoute: 01 04 01 46 01 BD
2016-12-03 14:40:26.530   Z-Wave Debug   RCVD assignReturnRoute: 01 05 00 46 01 00 BD
2016-12-03 14:40:26.530   Z-Wave Debug   . .  assignReturnRoute: node 009, success 1
2016-12-03 14:40:26.531   Z-Wave   Syncing - assigned return route
2016-12-03 14:40:26.531   Z-Wave Debug   SENT requestNodeInfo: 01 06 00 60 09 24 F6 42
2016-12-03 14:40:26.794   Z-Wave Debug   RCVD nodeInfoFrame: 01 15 00 49 84 09 0F 04 07 01 5E 86 72 30 70 71 5A 85 59 80 84 73 49
2016-12-03 14:40:26.797   Z-Wave Debug   . .  nodeInfoFrame: node 009, combined class list: 20v1 80v1 84v1 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
2016-12-03 14:40:26.798   Z-Wave Debug   SENT requestManufactureInfo: 01 09 00 13 09 02 72 04 25 F7 4A
2016-12-03 14:40:27.077   Z-Wave Debug   RCVD requestManufactureInfo: 01 0E 00 04 00 09 08 72 05 01 9A 00 03 00 03 18
2016-12-03 14:40:27.078   Z-Wave Debug   . .  requestManufactureInfo: node 009, manufacturerId 019A, productId 00030003
2016-12-03 14:40:27.079   Z-Wave Debug   . .  requestManufactureInfo: Sensative, Door/Window Sensor (Strips)
2016-12-03 14:40:27.079   Z-Wave   Syncing - retrieved manufacture and model names: Sensative - 019A, Door/Window Sensor (Strips) - 00030003
2016-12-03 14:40:27.080   Z-Wave Debug   SENT requestVersInfoGen: 01 09 00 13 09 02 86 11 25 F8 A4
2016-12-03 14:40:27.361   Z-Wave Debug   RCVD requestVersInfoGen: 01 11 00 04 00 09 0B 86 12 06 04 05 00 01 01 01 00 01 7B
2016-12-03 14:40:27.362   Z-Wave Debug   . .  requestVersInfoGen: node 009, protoVers 4.05, appVers 0.01
2016-12-03 14:40:27.362   Z-Wave   Syncing - retrieved protocol version 4.05, app version 0.01
2016-12-03 14:40:27.362   Z-Wave Debug   SENT requestVersInfoCmdClass: 01 0A 00 13 09 03 86 13 84 25 F9 21
2016-12-03 14:40:27.647   Z-Wave Debug   RCVD requestVersInfoCmdClass: 01 0A 00 04 00 09 04 86 14 84 02 E8
2016-12-03 14:40:27.650   Z-Wave Debug   . .  requestVersInfoCmdClass: node 009, class command 84 using version 2
2016-12-03 14:40:27.650   Z-Wave Debug   . .  requestVersInfoCmdClass: node 009, combined class list: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
2016-12-03 14:40:27.650   Z-Wave   Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
2016-12-03 14:40:27.651   Z-Wave   Syncing - retrieved command classes: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
2016-12-03 14:40:27.651   Z-Wave   Syncing - retrieved encrypt commands: - none -
2016-12-03 14:40:27.651   Z-Wave   Syncing - retrieved capabilities: routing, battery, beaming, waking
2016-12-03 14:40:27.651   Z-Wave Debug   SENT requestWakeInterval: 01 09 00 13 09 02 84 05 25 FA B0
2016-12-03 14:40:27.931   Z-Wave Debug   RCVD requestWakeInterval: 01 0C 00 04 00 09 06 84 06 01 51 80 00 AA
2016-12-03 14:40:27.933   Z-Wave Debug   . .  requestWakeInterval: node 009, interval 1440 minutes, wakeTarget 000
2016-12-03 14:40:27.933   Z-Wave   Syncing - retrieved wake interval of 1440 minutes
2016-12-03 14:40:27.933   Z-Wave Debug   SENT setWakeInterval: 01 0D 00 13 09 06 84 04 00 0E 10 01 25 FB AF
2016-12-03 14:40:27.963   Z-Wave   Syncing - device "009 - Notification Sensor" wake interval changed to 60 minutes
2016-12-03 14:40:27.965   Z-Wave Debug   SENT requestAssociationGroupCount: 01 09 00 13 09 02 85 05 25 FC B7
2016-12-03 14:40:28.251   Z-Wave Debug   RCVD requestAssociationGroupCount: 01 09 00 04 00 09 03 85 06 01 7A
2016-12-03 14:40:28.252   Z-Wave Debug   . .  requestAssociationGroupCount: node 009, group count: 1
2016-12-03 14:40:28.252   Z-Wave Debug   SENT requestAssociations: 01 0A 00 13 09 03 85 02 01 25 FD B2
2016-12-03 14:40:28.536   Z-Wave Debug   RCVD requestAssociations: 01 0B 00 04 00 09 05 85 03 01 01 00 7A
2016-12-03 14:40:28.536   Z-Wave Debug   . .  requestAssociations: node 009, group: 1, num associations: 0, max associations: 1, replies left: 0
2016-12-03 14:40:28.537   Z-Wave Debug   . .  requestAssociations: node 009, group: 1, associations: []
2016-12-03 14:40:28.537   Z-Wave   Syncing - retrieved group 1 associations: []
2016-12-03 14:40:28.538   Z-Wave Debug   SENT addInterfaceAssociation: 01 0B 00 13 09 04 85 01 01 01 25 FE B5
2016-12-03 14:40:28.819   Z-Wave   Syncing - added group 1 association to interface
2016-12-03 14:40:28.819   Z-Wave Debug   . .  addInterfaceAssociation: node 009, group: 1, associations: [1]
2016-12-03 14:40:28.820   Z-Wave Debug   RCVD requestAlarmSensorStatus: 01 10 00 04 00 09 0A 71 05 00 00 00 FF 06 16 00 00 73
2016-12-03 14:40:28.820   Z-Wave Debug   . .  requestAlarmSensorStatus: node 009, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
2016-12-03 14:40:28.820   Z-Wave Debug   . .  requestAlarmSensorStatus: typeExt 6, valueExt 22, classSubKeyExt 7100000616
2016-12-03 14:40:28.820   Z-Wave Debug   SENT requestConfigVal: 01 0A 00 13 09 03 70 05 01 25 FF 42
2016-12-03 14:40:29.103   Z-Wave Debug   RCVD requestConfigVal: 01 0B 00 04 00 09 05 70 06 01 01 01 8B
2016-12-03 14:40:29.103   Z-Wave Debug   . .  requestConfigVal: node 009, parm index 1, value 1 (size 1)
2016-12-03 14:40:29.103   Z-Wave   Syncing - retrieved parameter 1 "Notification type" is 1
2016-12-03 14:40:29.104   Z-Wave Debug   SENT setConfigVal: 01 0C 00 13 09 05 70 04 01 01 00 25 01 BC
2016-12-03 14:40:29.384   Z-Wave   Syncing - device "009 - Notification Sensor" parameter 1 "Notification type" changed to 0 (was 1)
2016-12-03 14:40:29.385   Z-Wave Debug   . .  pushNewValToNode: node 009, combined config vals: 1:0
2016-12-03 14:40:29.385   Z-Wave Debug   SENT requestConfigVal: 01 0A 00 13 09 03 70 05 02 25 02 BC
2016-12-03 14:40:29.662   Z-Wave Debug   RCVD requestConfigVal: 01 0B 00 04 00 09 05 70 06 02 01 01 88
2016-12-03 14:40:29.663   Z-Wave Debug   . .  requestConfigVal: node 009, parm index 2, value 1 (size 1)
2016-12-03 14:40:29.663   Z-Wave   Syncing - retrieved parameter 2 "LED blink during open/close" is true
2016-12-03 14:40:29.664   Z-Wave Debug   . .  requestConfigVal: node 009, combined config vals: 1:0 2:1
2016-12-03 14:40:29.664   Z-Wave Debug   SENT requestBatteryLevel: 01 09 00 13 09 02 80 02 25 03 4A
2016-12-03 14:40:29.744   Z-Wave Debug   . .  requestBatteryLevel: requeuing 1 unsolicited packets
2016-12-03 14:40:29.995   Z-Wave Debug   RCVD requestBatteryLevel: 01 09 00 04 00 09 03 80 03 FF 84
2016-12-03 14:40:29.996   Z-Wave Debug   . .  requestBatteryLevel: node 009, level 255
2016-12-03 14:40:29.997   Z-Wave   Syncing - retrieved battery level of 0%
2016-12-03 14:40:29.997   Z-Wave Debug   RCVD requestBatteryLevel: 01 09 00 04 00 09 03 80 03 FF 84
2016-12-03 14:40:29.999   Z-Wave Debug   . .  requestBatteryLevel: node 009, level 255
2016-12-03 14:40:29.999   Z-Wave   Syncing - retrieved battery level of 0%
2016-12-03 14:40:30.244   Z-Wave   Syncing - created device "009 - Door/Window Sensor"
2016-12-03 14:40:30.283   Z-Wave   Syncing - complete
2016-12-03 14:40:30.435   Z-Wave Debug   terminatingSyncUI

And finally the updates when I simulate a door close/open:

Code: Select all

Door closed
2016-12-03 14:40:49.941   Z-Wave Debug   RCVD requestBinarySensorStatus: 01 09 00 04 00 09 03 30 03 00 CB
2016-12-03 14:40:49.943   Z-Wave Debug   . .  requestBinarySensorStatus: node 009, endpoint None, value 0
2016-12-03 14:40:49.943   Z-Wave   received "009 - Door/Window Sensor" status update is off

Door open
2016-12-03 14:40:53.466   Z-Wave Debug   RCVD requestBinarySensorStatus: 01 09 00 04 00 09 03 30 03 FF 34
2016-12-03 14:40:53.467   Z-Wave Debug   . .  requestBinarySensorStatus: node 009, endpoint None, value 255
2016-12-03 14:40:53.467   Z-Wave   received "009 - Door/Window Sensor" status update is on

[matt (support)]

Is this just a range problem? The Gen5 Z-Stick is going to have a better range than the S2 so maybe with the S2 the commands aren't reliably making it to the module.

Dont think it is a range problem since I am sitting here in my "lab" where both the Gen5 stick and Gen2 sticks are within 1-2 meters from the strip.

I have emailed Sensative Strips about these issues. My strips are very early (bought them as soon as they were on the market here in Sweden) so it might be a firmware issue.
Sensative have been good on support to other users and they are made here in Sweden.

Unless you see any strange differences in the inclusion logs between the S5 and S2 sticks then we´ll just wait for Sensative's response.
I´ll report back here when/if I get any feedback from them.