You can try a factory reset on the device & add again. I have had to do that with some cheap Chinese devices before.
Hello Mario,
Yes, finnaly i was able to use the Hank Flood Sensor with OpenHAB. Let me check if I have any documents about how i did it.
1 Like
Are you sure that you are really waking up the device? Often people think they are as they do something that causes a device to send a message, but quite often it is not the right thing. The wakeup is a very specific message.
Please check, or provide the debug logs so you can be sure what is happening.
From the log I get confirmed that when I press the button on the sensor three times the Node7(which is the sensor) wakesup
2019-10-10 10:41:34.238 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Is awake with 1 messages in the queue
Not sure what I should look for (and because I can’t seem to figure out these blockquotes for multiple lines ) I just add the two last loglines. I gues they are an idication that something is not going the way it should:
2019-10-10 10:42:52.337 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Polling…
2019-10-10 10:42:52.347 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Polling deferred until initialisation complete
I will try to get the whole log readout (about node7 ) in asap. But maybe you can give me a hint of what I should look for? (singleline blockquotes work perfectly)
Grts,
Mario
The zwave log viewer may reveal more information.
https://www.cd-jackson.com/index.php/openhab/zwave-log-viewer
From the manual: to wake the device press the Z button once.
This is the complet log after I press the button three times.
I will do the same but then only press the button ones.
2019-10-10 11:08:38.335 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:VERSION)
2019-10-10 11:08:38.338 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2019-10-10 11:08:38.340 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL
2019-10-10 11:08:38.343 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT
2019-10-10 11:08:38.346 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 7: Sensor Type = Temperature(1), Scale = 0
2019-10-10 11:08:38.349 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 7: Sensor Value = 22.5
2019-10-10 11:08:38.352 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2019-10-10 11:08:38.355 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=22.5
2019-10-10 11:08:38.358 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2019-10-10 11:08:38.361 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@be5460.
2019-10-10 11:08:38.405 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:VERSION)
2019-10-10 11:08:38.408 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-10-10 11:08:38.410 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_ALARM
2019-10-10 11:08:38.413 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_ALARM V0 NOTIFICATION_REPORT
2019-10-10 11:08:38.416 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: NOTIFICATION report - 0 = 0, event=9, status=255, plen=0
2019-10-10 11:08:38.419 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: Alarm Type = BURGLAR (0)
2019-10-10 11:08:38.422 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-10-10 11:08:38.425 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2019-10-10 11:08:38.428 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2019-10-10 11:08:38.430 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1bcdb35.
2019-10-10 11:08:38.920 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 7: Application update request. Node information received. Transaction null
2019-10-10 11:08:38.923 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Unsupported command class COMMAND_CLASS_TRANSPORT_SERVICE
2019-10-10 11:08:38.926 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Unsupported command class COMMAND_CLASS_SECURITY_2
2019-10-10 11:08:38.929 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Unsupported command class COMMAND_CLASS_SUPERVISION
2019-10-10 11:08:38.931 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 7: Application update - no transaction.
2019-10-10 11:08:39.185 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Is awake with 1 messages in the queue
2019-10-10 11:08:39.189 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Start sleep timer at 5000ms
2019-10-10 11:08:39.192 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2019-10-10 11:08:39.207 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 7: Node Status event - Node is AWAKE
2019-10-10 11:08:41.693 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: WakeupTimerTask 1 Messages waiting, state VERSION
2019-10-10 11:08:44.193 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: WakeupTimerTask 1 Messages waiting, state VERSION
2019-10-10 11:08:44.196 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: No more messages, go back to sleep
2019-10-10 11:08:44.198 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2019-10-10 11:08:44.201 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_WAKE_UP
2019-10-10 11:08:44.204 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2019-10-10 11:08:44.207 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@809ae0
2019-10-10 11:08:44.211 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Bump transaction 190 priority from Immediate to Immediate
2019-10-10 11:08:44.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Adding to device queue
2019-10-10 11:08:44.222 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Added 190 to queue - size 3
2019-10-10 11:08:44.233 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 7: Sending REQUEST Message = 01 0A 00 13 07 03 86 13 85 25 A1 76
2019-10-10 11:08:44.280 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: sentData successfully placed on stack.
2019-10-10 11:08:44.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 189: Transaction not completed
2019-10-10 11:08:44.317 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: SendData Request. CallBack ID = 161, Status = Transmission complete and ACK received(0)
2019-10-10 11:08:44.322 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 189: Transaction not completed
2019-10-10 11:08:44.332 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:VERSION)
2019-10-10 11:08:44.336 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_VERSION, endpoint 0
2019-10-10 11:08:44.338 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_VERSION
2019-10-10 11:08:44.341 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_VERSION V0 VERSION_COMMAND_CLASS_REPORT
2019-10-10 11:08:44.344 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 7: Process Version Command Class Report
2019-10-10 11:08:44.347 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 7: Requested Command Class = COMMAND_CLASS_ASSOCIATION, Version = 2
2019-10-10 11:08:44.350 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Version = 2, version set. Enabling extra functionality.
2019-10-10 11:08:44.353 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2019-10-10 11:08:44.356 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@187d60.
2019-10-10 11:08:44.359 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@187d60.
2019-10-10 11:08:44.361 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: notifyTransactionResponse TID:189 DONE
2019-10-10 11:08:44.365 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-10-10 11:08:44.377 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@280271
2019-10-10 11:08:44.380 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node Init transaction completed with response COMPLETE
2019-10-10 11:08:44.383 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: VERSION - checking COMMAND_CLASS_ASSOCIATION_GRP_INFO, version is 0
2019-10-10 11:08:44.386 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: VERSION - queued COMMAND_CLASS_ASSOCIATION_GRP_INFO
2019-10-10 11:08:44.388 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 7: Creating new message for application command VERSION_COMMAND_CLASS_GET command class COMMAND_CLASS_ASSOCIATION_GRP_INFO
2019-10-10 11:08:44.392 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: ZWaveCommandClassTransactionPayload - send to node
2019-10-10 11:08:44.396 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_VERSION
2019-10-10 11:08:44.398 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 7: Sending REQUEST Message = 01 09 00 13 07 02 84 08 25 A2 EB
2019-10-10 11:08:44.399 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Command Class COMMAND_CLASS_VERSION is NOT required to be secured
2019-10-10 11:08:44.403 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1bcd25d
2019-10-10 11:08:44.406 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Bump transaction 191 priority from Config to Immediate
2019-10-10 11:08:44.414 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Adding to device queue
2019-10-10 11:08:44.417 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Added 191 to queue - size 2
2019-10-10 11:08:44.449 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: sentData successfully placed on stack.
2019-10-10 11:08:44.453 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 190: Transaction not completed
2019-10-10 11:08:44.477 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: SendData Request. CallBack ID = 162, Status = Transmission complete and ACK received(0)
2019-10-10 11:08:44.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Response processed after 74ms
2019-10-10 11:08:44.485 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 190: Transaction completed
2019-10-10 11:08:44.487 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: notifyTransactionResponse TID:190 DONE
2019-10-10 11:08:44.490 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-10-10 11:08:44.498 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Went to sleep COMPLETE
2019-10-10 11:08:44.505 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 7: Sending REQUEST Message = 01 0A 00 13 07 03 86 13 59 25 A3 A8
2019-10-10 11:08:44.544 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: sentData successfully placed on stack.
2019-10-10 11:08:44.549 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 191: Transaction not completed
2019-10-10 11:08:44.573 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 7: SendData Request. CallBack ID = 163, Status = Transmission complete and ACK received(0)
2019-10-10 11:08:44.579 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: TID 191: Transaction not completed
2019-10-10 11:08:44.587 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:VERSION)
2019-10-10 11:08:44.590 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_VERSION, endpoint 0
2019-10-10 11:08:44.593 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_VERSION
2019-10-10 11:08:44.595 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_VERSION V0 VERSION_COMMAND_CLASS_REPORT
2019-10-10 11:08:44.598 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 7: Process Version Command Class Report
2019-10-10 11:08:44.601 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 7: Requested Command Class = COMMAND_CLASS_ASSOCIATION_GRP_INFO, Version = 1
2019-10-10 11:08:44.604 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Version = 1, version set. Enabling extra functionality.
2019-10-10 11:08:44.606 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2019-10-10 11:08:44.609 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12d278c.
2019-10-10 11:08:44.611 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12d278c.
2019-10-10 11:08:44.614 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: notifyTransactionResponse TID:191 DONE
2019-10-10 11:08:44.617 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-10-10 11:08:44.626 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@1cee782
2019-10-10 11:08:44.629 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node Init transaction completed with response COMPLETE
2019-10-10 11:08:44.631 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: VERSION - checking COMMAND_CLASS_BATTERY, version is 0
2019-10-10 11:08:44.634 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: VERSION - queued COMMAND_CLASS_BATTERY
2019-10-10 11:08:44.637 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 7: Creating new message for application command VERSION_COMMAND_CLASS_GET command class COMMAND_CLASS_BATTERY
2019-10-10 11:08:44.640 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: ZWaveCommandClassTransactionPayload - send to node
2019-10-10 11:08:44.642 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_VERSION
2019-10-10 11:08:44.645 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Command Class COMMAND_CLASS_VERSION is NOT required to be secured
2019-10-10 11:08:44.648 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@6d0ff3
2019-10-10 11:08:44.650 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Bump transaction 192 priority from Config to Immediate
2019-10-10 11:08:44.653 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Adding to device queue
2019-10-10 11:08:44.656 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Added 192 to queue - size 2
2019-10-10 11:09:11.872 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:VERSION)
2019-10-10 11:09:11.875 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-10-10 11:09:11.877 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_ALARM
2019-10-10 11:09:11.879 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_ALARM V0 NOTIFICATION_REPORT
2019-10-10 11:09:11.882 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2019-10-10 11:09:11.884 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: Alarm Type = BURGLAR (0)
2019-10-10 11:09:11.887 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-10-10 11:09:11.889 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2019-10-10 11:09:11.892 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2019-10-10 11:09:11.894 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1ea625d.
2019-10-10 11:12:52.337 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Polling...
2019-10-10 11:12:52.341 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Polling deferred until initialisation complete
I’m afraid I have no experience with that so you will need to give me some time to figure that out.
I’m actually learning each minute!!
Grts
Paste the debug log information into a file. Go to the viewer page and point it to that file.
Observe the results in your web browser.
1 Like
It looks like the binding does think the device is waking up, but I’m not really sure what is then happening. Can you provide the full log from startup. Please don’t filter the log by the node number as this removes all received data from the device, so in the log above it’s impossible to see what is happening.
1 Like
Let me first clearly state what I have been doing the past few minutes:
1° shutdown rasp3
2° unplug usb Aeotec Z-stick Gen 5
3° exclude the Hank sensor
4° plug in Z-stick and restart rasp
5° check that the thing on node 7 is indeed gone and delete it from habmin
6° turn off rasp and unplug Z-stick
7° return Hank-sensor to factorystate by pressing the butten longer than 20 sec (led seem to confirm succes)
8° include the sensor on the Z-stick
9° plug the stick into rasp and restart
10° add newly found thing on node 8
Just so that we are clear on this and that from now on the sensor is on node 8!
Unfortunately, the thing’s manufacturer is still not recognized.
I know that the manuall says pressing one time to wake up but the only way to get a “Is awake with 1 messages in the queue” message on that node is by pressing three times. I’m open for every amount of presses 
I uploaded the debug log beginning at point 10 in my workflow above plus a one-time push of the z-button on the sensor(around 12.06h) and a three times pushed z-button on the sensor (around 12.17h)
completeLog.txt (96.2 KB)
From your log, it is:
Yes, the manual seems to be wrong then. If I where you I would not buy any Hank devices again.
So to come back to your original question: where is the problem? You are not able to change config parameters or the device does not send a flood alarm on the alarm_flood channel?
If the latter, the channel maybe needs to be reconfigured:
BTW, it is always best to exclude and include while the stick is plugged into your computer and trigger the controller through the binding. If you want to include devices securely, this is your only option.
Other than door locks what are the benefits of using security? I believe there can be issues deleting and re-adding related to the security key. I think I read that somewhere here.
I believe my devices support security but used insecure mode for simplicity especially after issues with other automation systems.
Same here. And I don’t have any zwave door locks 
You always need to be sure to save your key somewhere: you will need it if you change your stick or your operating system.
Thanks. No locks here either.
If I were in a college environment or a crowded city I might choose security to avoid somebody else controlling my network devices.
In PaperUI and Habmin the thing is still not recognized and without manufacturer.
This is the attributes section in Habmin:
If you have more questions or sugestions, don’t hesitate!!!
Grts
Mario
That only happens if the device is not fully discovered. The binding queries for the node information using a standard Z-Wave command that is required to be supported.
Battery operated devices can be a problem if they go to sleep before the initial association is complete. You need to wake them up repeatedly. You probably see (Requesting NIF) when looking at the Thing for that node to the left of the screen above.
Wake it up, wake it up, wake it up
If the xml is generated, you are fine.
And remember: you included the device outside of openHAB, that may cause problems.
1 Like
What sorts of problems?
I initially moved to OH that way. Home Assistant needs to see the inclusion because that is the only time it uses the device information for identification.