Hi, I got new ZWave Sensative Strips, Door Window and Comfort. I included them to the controller but they are both not regognized. From the log I can see that the Comfort Strip is reporting luminance and temperature. I think I found both strips in the database, but still after hours not recognized.
Anyone else having this problem? What to do? Already updated to the version 1607.
I had the same problem.
You need to wake up the device a couple of times, until they get properly recognized. How to wake up the strips you can find in the manual or here:
https://sensativesupport.zendesk.com/hc/en-us/articles/360001130552-Manuals-for-Strips-Guard
DO NOT exclude/include from the controller
DO NOT reset the device incidentally
If you have not mounted them, do the wake up very close to the controller.
I got 3 of 5 devices to be recignized, the other two are still unknown, even after 30 - 40 wake up. Any idea or what to check in logs?
Here is one wake up:
2019-06-13 13:56:54.301 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 09 0A 71 05 00 00 00 FF 07 04 00 00 60
2019-06-13 13:56:54.307 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 0A 71 05 00 00 00 FF 07 04 00 00
2019-06-13 13:56:54.309 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 0A 71 05 00 00 00 FF 07 04 00 00
2019-06-13 13:56:54.312 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-06-13 13:56:54.314 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Application Command Request (ALIVE:DONE)
2019-06-13 13:56:54.315 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false
2019-06-13 13:56:54.317 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-06-13 13:56:54.318 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: SECURITY not supported
2019-06-13 13:56:54.320 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 9: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2019-06-13 13:56:54.322 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: NOTIFICATION report - 0 = 0, event=4, status=255, plen=0
2019-06-13 13:56:54.323 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Alarm Type = BURGLAR (0)
2019-06-13 13:56:54.325 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-06-13 13:56:54.327 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2019-06-13 13:56:54.330 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Commands processed 1.
2019-06-13 13:56:54.331 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@67a93b.
2019-06-13 13:56:54.333 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-06-13 13:56:54.334 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-06-13 13:56:54.336 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-06-13 13:56:54.337 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-06-13 13:56:54.353 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 15 00 49 84 09 0F 04 21 01 5E 85 59 86 72 31 5A 73 80 70 71 84 6E
2019-06-13 13:56:54.358 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationUpdate[73], type=Request[0], dest=9, callback=132, payload=84 09 0F 04 21 01 5E 85 59 86 72 31 5A 73 80 70 71 84
2019-06-13 13:56:54.361 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationUpdate[73], type=Request[0], dest=9, callback=132, payload=84 09 0F 04 21 01 5E 85 59 86 72 31 5A 73 80 70 71 84
2019-06-13 13:56:54.362 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-06-13 13:56:54.364 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 0
2019-06-13 13:56:54.365 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: null
2019-06-13 13:56:54.368 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=ApplicationUpdate[73], type=Request[0], dest=9, callback=132, payload=84 09 0F 04 21 01 5E 85 59 86 72 31 5A 73 80 70 71 84
2019-06-13 13:56:54.369 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 9: Application update request. Node information received. Transaction null
2019-06-13 13:56:54.371 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false
2019-06-13 13:56:54.373 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 9: Application update - no transaction.
2019-06-13 13:56:54.375 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-06-13 13:56:54.376 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-06-13 13:56:54.625 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Is awake with 0 messages in the queue
2019-06-13 13:56:54.627 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Start sleep timer at 1000ms
2019-06-13 13:56:54.628 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2019-06-13 13:56:54.635 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 9: Node Status event - Node is AWAKE
==> /var/log/openhab2/events.log <==
2019-06-13 13:56:54.644 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:controller:node9’ has been updated.
==> /var/log/openhab2/openhab.log <==
2019-06-13 13:56:55.128 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: WakeupTimerTask 0 Messages waiting, state DONE
2019-06-13 13:56:55.628 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: WakeupTimerTask 0 Messages waiting, state DONE
2019-06-13 13:56:55.629 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: No more messages, go back to sleep
2019-06-13 13:56:55.630 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 9: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2019-06-13 13:56:55.631 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: SECURITY not supported
2019-06-13 13:56:55.632 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2019-06-13 13:56:55.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1b020f7
2019-06-13 13:56:55.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Bump transaction 401 priority from Immediate to Immediate
2019-06-13 13:56:55.636 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Adding to device queue
2019-06-13 13:56:55.637 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Added 401 to queue - size 7
2019-06-13 13:56:55.638 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-06-13 13:56:55.640 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 09 02 84 08 25 A5 E2
2019-06-13 13:56:55.642 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 9: Sending REQUEST Message = 01 09 00 13 09 02 84 08 25 A5 E2
2019-06-13 13:56:55.643 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2019-06-13 13:56:55.644 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 401: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 165
2019-06-13 13:56:55.645 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2019-06-13 13:56:55.647 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-06-13 13:56:55.648 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-06-13 13:56:55.649 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 401: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 165
2019-06-13 13:56:55.650 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2019-06-13 13:56:55.651 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-06-13 13:56:55.652 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-06-13 13:56:55.653 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2019-06-13 13:56:55.655 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2019-06-13 13:56:55.656 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2019-06-13 13:56:55.657 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 401: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 165
2019-06-13 13:56:55.658 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-06-13 13:56:55.659 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 401: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 165
2019-06-13 13:56:55.660 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2019-06-13 13:56:55.662 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 9: sentData successfully placed on stack.
2019-06-13 13:56:55.663 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 401: Advanced to WAIT_REQUEST
2019-06-13 13:56:55.664 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: TID 401: Transaction not completed
2019-06-13 13:56:55.665 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-06-13 13:56:55.666 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-06-13 13:56:55.668 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 A5 00 00 02 4C
2019-06-13 13:56:55.670 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=165, payload=A5 00 00 02
2019-06-13 13:56:55.671 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=165, payload=A5 00 00 02
2019-06-13 13:56:55.673 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 401: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 165
2019-06-13 13:56:55.673 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-06-13 13:56:55.675 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 401: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 165
2019-06-13 13:56:55.676 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 401: (Callback 165)
2019-06-13 13:56:55.677 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2019-06-13 13:56:55.678 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 401: callback 165
2019-06-13 13:56:55.680 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=165, payload=A5 00 00 02
2019-06-13 13:56:55.681 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 9: SendData Request. CallBack ID = 165, Status = Transmission complete and ACK received(0)
2019-06-13 13:56:55.682 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false
2019-06-13 13:56:55.683 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 401: Transaction COMPLETED
2019-06-13 13:56:55.685 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Response processed after 40ms
2019-06-13 13:56:55.685 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: TID 401: Transaction completed
2019-06-13 13:56:55.687 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: notifyTransactionResponse TID:401 DONE
2019-06-13 13:56:55.688 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-06-13 13:56:55.688 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 401: Transaction event listener: DONE: DONE ->
2019-06-13 13:56:55.690 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Went to sleep COMPLETE
2019-06-13 13:56:55.690 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-06-13 13:56:55.691 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
No idea. I have now also one, that I cannot get recognized. It remains as unknown device but in HABmin I can see, that the controller/OH recognized the wakeup of the device.
I have the same problem with a FIBARO Smoke Sensor now.
Is there any news on this? I’m having the same issue. I got 3 door strips here, tried with two of them but it’s not sending its info. Could add them as a thing on the first try, but even after well over 25 wake-ups they didn’t even transmit the battery level.
Log:
04-Feb-2020 18:02:05.779 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from UNINITIALIZED to INITIALIZING
04-Feb-2020 18:02:05.809 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
04-Feb-2020 18:02:05.811 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
04-Feb-2020 18:02:05.842 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
04-Feb-2020 18:02:05.873 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
04-Feb-2020 18:02:05.889 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
04-Feb-2020 18:02:05.893 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
04-Feb-2020 18:03:23.311 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
04-Feb-2020 18:03:23.313 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
04-Feb-2020 18:06:12.569 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
04-Feb-2020 18:06:12.578 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE: Node initialising: SET_ASSOCIATION
04-Feb-2020 18:07:13.362 [smarthome.event.ThingStatusInfoChangedEvent ] - ‘zwave:device:dd17dc98:node9’ changed from ONLINE: Node initialising: SET_ASSOCIATION to ONLINE
Hi Michel,
it works - but you need time 
what we don‘t have when we like to try it.
For me it worked automatically after a few days. I went away a few days for holiday and when I came back they where included.
Not nice but it worked. Didn‘t try to add a new since then.
Regards
Thomas
Hi @thokl,
what is you experience with them? Are they good?
Would you advise to buy some as an outdoor sensor?
Thanks in advance!
HFM
Hi,
I have 3 of the comfort stripes using outdoor and until now they work well.
Regards
Thomas
Hey Guys, similar case here… I tried over days to activate the strips guard, without luck. dont know how often I ried, but at the end it was hours… I wrote to sensative to get some support, but just got one sloppy answer; the dont even seem to know what openhab is, and always replied with HASS instructions 
before I throw this strip away and never buy one again: if anyone of you who got it working could share again what you did to get it working, pls share it…
one strange thing is, I have now min. 4 nodes “reserved”, as the stick pops up as new node after resetting it… how can I remove / free these nodes? maybe also this helps to get this strip working?
I had the same problem and now it is working. I’m using OpenHAB 2.5 with an Aeotec Z-Stick Gen5 as the Z-wave controller and “11-01-011 Strips-MaZw” as the door/window sensor.
The sensor has not been recognised (though it was included) for about 24 hours even though I have triggered the wake up about 100 times throughout the day. After the first 23 hours, I have set the “Polling Period” setting to 10 minutes and the “Wakeup Interval” to 600 seconds. One hour later, it has been fully recognised. In the end, I increased these two values again because of energy consumption.
I have had some trouble to get the strips connected, but it is working now.
Things I have done to make it work:
- Include in controller, but was unknown device
- Wake up the device around 5-10 times after inclusion with a Aeotec Z-Stick Gen5 Controller
- See wakeup-instructions here How to manually wake up Strips Guard – Sensative AB (zendesk.com)
- Reinitialize the device using PaperUI
- Repeat a number of wakeups. PaperUI show the recognized device type
- Set configuration via PaperUI: the Notificiation type in the configuration to Notification Report
- Set configuration via PaperUI: set Lifeline to Controller
- Above should be the default, but with the default settings it was not working.
- Create an Item of type Contact that can be Open and Closed and bind it to the door_sensor channel.
I did include/exclude the strip a few times because it was not working. I have also executed a factory reset, set it to auto-add mode again and then did above procedure.
So in the best case, it is just a matter of doing enough wakeups for openhab to recognize the device. Worst case, you might also need to do a factory reset (also listed at above link).