ABUS Z-Wave Doorlock HomeTec Pro CFA3010

Swiched back to openhab 2.5.
I tryed everything, but I am still stuck.

Here is the Log’s:

2020-12-30 21:06:38.851 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - NODE 132: Add Node: Protocol done.

2020-12-30 21:06:38.857 [DEBUG] [al.protocol.ZWaveInclusionController] - NODE 132: Inclusion protocol completed.

2020-12-30 21:06:38.858 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Creating new instance of command class COMMAND_CLASS_NO_OPERATION

2020-12-30 21:06:38.859 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Command class COMMAND_CLASS_NO_OPERATION, endpoint 0 created

2020-12-30 21:06:38.860 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Version = 1, version set. Enabling extra functionality.

2020-12-30 21:06:38.861 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Adding command class COMMAND_CLASS_NO_OPERATION to the list of supported command classes.

2020-12-30 21:06:38.862 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Creating new instance of command class COMMAND_CLASS_BASIC

2020-12-30 21:06:38.863 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Command class COMMAND_CLASS_BASIC, endpoint 0 created

2020-12-30 21:06:38.864 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Adding command class COMMAND_CLASS_BASIC to the list of supported command classes.

2020-12-30 21:06:38.865 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Creating new instance of command class COMMAND_CLASS_ZWAVEPLUS_INFO

2020-12-30 21:06:38.866 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Command class COMMAND_CLASS_ZWAVEPLUS_INFO, endpoint 0 created

2020-12-30 21:06:38.868 [DEBUG] [al.protocol.ZWaveInclusionController] - NODE 132: Inclusion is adding command class COMMAND_CLASS_ZWAVEPLUS_INFO.

2020-12-30 21:06:38.868 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Adding command class COMMAND_CLASS_ZWAVEPLUS_INFO to the list of supported command classes.

2020-12-30 21:06:38.869 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Unsupported command class COMMAND_CLASS_TRANSPORT_SERVICE

2020-12-30 21:06:38.870 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Creating new instance of command class COMMAND_CLASS_SECURITY

2020-12-30 21:06:38.871 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Command class COMMAND_CLASS_SECURITY, endpoint 0 created

2020-12-30 21:06:38.872 [DEBUG] [al.protocol.ZWaveInclusionController] - NODE 132: Inclusion is adding command class COMMAND_CLASS_SECURITY_2.

2020-12-30 21:06:38.873 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Adding command class COMMAND_CLASS_SECURITY to the list of supported command classes.

2020-12-30 21:06:38.874 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Unsupported command class COMMAND_CLASS_SUPERVISION

2020-12-30 21:06:38.875 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 132: ZWaveController include node

2020-12-30 21:06:38.876 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Starting initialisation from INCLUSION_START

2020-12-30 21:06:38.878 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node advancer: Node just included (2838302)

2020-12-30 21:06:38.879 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node advancer - advancing to IDENTIFY_NODE

2020-12-30 21:06:38.880 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node advancer: Initialisation starting from inclusion

2020-12-30 21:06:44.398 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 132: Device discovered

2020-12-30 21:06:44.401 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:8cc3e2eb:node132' to inbox.

2020-12-30 21:06:44.418 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: ProtocolInfo

2020-12-30 21:06:44.419 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Listening = false

2020-12-30 21:06:44.419 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Routing   = true

2020-12-30 21:06:44.419 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Beaming   = true

2020-12-30 21:06:44.420 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Version   = 4

2020-12-30 21:06:44.420 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: FLIRS     = true

2020-12-30 21:06:44.421 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Security  = false

2020-12-30 21:06:44.421 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Max Baud  = 40000

2020-12-30 21:06:44.422 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Basic    = BASIC_TYPE_ROUTING_SLAVE

2020-12-30 21:06:44.422 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Generic  = GENERIC_TYPE_ENTRY_CONTROL

2020-12-30 21:06:44.422 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 132: Specific = SPECIFIC_TYPE_SECURE_KEYPAD_DOOR_LOCK

2020-12-30 21:06:44.423 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Creating new instance of command class COMMAND_CLASS_NO_OPERATION

2020-12-30 21:06:44.423 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Command class COMMAND_CLASS_NO_OPERATION, endpoint 0 created

2020-12-30 21:06:44.424 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Version = 1, version set. Enabling extra functionality.

2020-12-30 21:06:44.425 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Adding command class COMMAND_CLASS_NO_OPERATION to the list of supported command classes.

2020-12-30 21:06:44.425 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Creating new instance of command class COMMAND_CLASS_BASIC

2020-12-30 21:06:44.426 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Command class COMMAND_CLASS_BASIC, endpoint 0 created

2020-12-30 21:06:44.426 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Adding command class COMMAND_CLASS_BASIC to the list of supported command classes.

2020-12-30 21:06:44.429 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@111453f

2020-12-30 21:06:44.430 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node Init transaction completed with response COMPLETE

2020-12-30 21:06:44.400 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:8cc3e2eb:node132' has been added.

2020-12-30 21:06:45.430 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node advancer - advancing to SECURITY_REPORT

2020-12-30 21:06:45.432 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 132: Updated networkKey

2020-12-30 21:06:45.433 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 132: setupNetworkKey useSchemeZero=false

2020-12-30 21:06:45.435 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Performing secure inclusion.

2020-12-30 21:06:45.436 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: SECURITY_INC State=GET_SCHEME

2020-12-30 21:06:45.437 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: ZWaveCommandClassTransactionPayload - send to node

2020-12-30 21:06:45.438 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: SECURITY check internal

2020-12-30 21:06:45.439 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Command Class COMMAND_CLASS_SECURITY is NOT required to be secured

2020-12-30 21:06:45.439 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@13c7f9

2020-12-30 21:06:45.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Bump transaction 8445 priority from Immediate to Immediate

2020-12-30 21:06:45.441 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Adding to device queue

2020-12-30 21:06:45.442 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Added 8445 to queue - size 97

2020-12-30 21:07:00.690 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 132: Sending REQUEST Message = 01 0A 00 13 84 03 98 04 00 25 1A C2 

2020-12-30 21:07:00.707 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: sentData successfully placed on stack.

2020-12-30 21:07:00.709 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8445: Transaction not completed

2020-12-30 21:07:01.863 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: SendData Request. CallBack ID = 26, Status = Transmission complete and ACK received(0)

2020-12-30 21:07:01.866 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8445: Transaction not completed

2020-12-30 21:07:06.866 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 132: TID 8445: Timeout at state WAIT_DATA. 3 retries remaining.

2020-12-30 21:07:06.868 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: notifyTransactionResponse TID:8445 CANCELLED

2020-12-30 21:07:06.871 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@2e0ee2

2020-12-30 21:07:06.872 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: No data from device, but it was ACK'd. Possibly not supported? (Try 0)

2020-12-30 21:07:06.873 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: timed out after 21435965781 / 20000000000

2020-12-30 21:07:06.874 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: SECURITY_INC State=FAILED, Reason=GET_SCHEME

2020-12-30 21:07:06.875 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node advancer - advancing to MANUFACTURER

2020-12-30 21:07:06.876 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Command class COMMAND_CLASS_MANUFACTURER_SPECIFIC not found, trying to add it.

2020-12-30 21:07:06.877 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Creating new instance of command class COMMAND_CLASS_MANUFACTURER_SPECIFIC

2020-12-30 21:07:06.878 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 132: Command class COMMAND_CLASS_MANUFACTURER_SPECIFIC, endpoint 0 created

2020-12-30 21:07:06.879 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Adding command class COMMAND_CLASS_MANUFACTURER_SPECIFIC to endpoint 0

2020-12-30 21:07:06.880 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node advancer: MANUFACTURER - send ManufacturerSpecific

2020-12-30 21:07:06.881 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 132: Creating new message for command MANUFACTURER_SPECIFIC_GET

2020-12-30 21:07:06.882 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: ZWaveCommandClassTransactionPayload - send to node

2020-12-30 21:07:06.883 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: SECURITY NOT required on COMMAND_CLASS_MANUFACTURER_SPECIFIC

2020-12-30 21:07:06.884 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Command Class COMMAND_CLASS_MANUFACTURER_SPECIFIC is NOT required to be secured

2020-12-30 21:07:06.885 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1798338

2020-12-30 21:07:06.886 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Bump transaction 8446 priority from Config to Immediate

2020-12-30 21:07:06.887 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Adding to device queue

2020-12-30 21:07:06.888 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Added 8446 to queue - size 95

2020-12-30 21:07:06.943 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 132: Sending REQUEST Message = 01 09 00 13 84 02 72 04 25 1C 2C 

2020-12-30 21:07:06.958 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: sentData successfully placed on stack.

2020-12-30 21:07:06.959 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8446: Transaction not completed

2020-12-30 21:07:08.250 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: SendData Request. CallBack ID = 28, Status = Transmission complete and ACK received(0)

2020-12-30 21:07:08.253 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8446: Transaction not completed

2020-12-30 21:07:10.038 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:8cc3e2eb:node132.

2020-12-30 21:07:10.041 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: MANUFACTURER not set

2020-12-30 21:07:10.041 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Controller status changed to ONLINE.

2020-12-30 21:07:10.042 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Controller is ONLINE. Starting device initialisation.

2020-12-30 21:07:10.047 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Updating node properties.

2020-12-30 21:07:10.047 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Updating node properties. MAN=2147483647

2020-12-30 21:07:10.048 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Properties synchronised

2020-12-30 21:07:10.253 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Initialising Thing Node...

2020-12-30 21:07:10.255 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Polling initialised at 1800 seconds - start in 167400 milliseconds.

2020-12-30 21:07:10.256 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Device initialisation complete.

2020-12-30 21:07:09.997 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:8cc3e2eb:node132' has been removed.

2020-12-30 21:07:10.026 [hingStatusInfoChangedEvent] - 'zwave:device:8cc3e2eb:node132' changed from UNINITIALIZED to INITIALIZING

2020-12-30 21:07:10.041 [hingStatusInfoChangedEvent] - 'zwave:device:8cc3e2eb:node132' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2020-12-30 21:07:10.050 [hingStatusInfoChangedEvent] - 'zwave:device:8cc3e2eb:node132' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2020-12-30 21:07:10.052 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:8cc3e2eb:node132' has been updated.

2020-12-30 21:07:10.252 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:8cc3e2eb:node132' has been updated.

2020-12-30 21:07:13.254 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 132: TID 8446: Timeout at state WAIT_DATA. 3 retries remaining.

2020-12-30 21:07:13.257 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2020-12-30 21:07:13.257 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: notifyTransactionResponse TID:8446 CANCELLED

2020-12-30 21:07:13.274 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@ae1495

2020-12-30 21:07:13.275 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: No data from device, but it was ACK'd. Possibly not supported? (Try 0)

2020-12-30 21:07:14.037 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: ZWaveCommandClassTransactionPayload - send to node

2020-12-30 21:07:14.038 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: SECURITY NOT required on COMMAND_CLASS_MANUFACTURER_SPECIFIC

2020-12-30 21:07:14.039 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Command Class COMMAND_CLASS_MANUFACTURER_SPECIFIC is NOT required to be secured

2020-12-30 21:07:14.040 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1798338

2020-12-30 21:07:14.041 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Bump transaction 8447 priority from Config to Immediate

2020-12-30 21:07:14.042 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Adding to device queue

2020-12-30 21:07:14.043 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Added 8447 to queue - size 93

2020-12-30 21:07:15.385 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 132: Sending REQUEST Message = 01 09 00 13 84 02 72 04 25 1E 2E 

2020-12-30 21:07:15.542 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: notifyTransactionResponse TID:8447 WAIT_RESPONSE

2020-12-30 21:07:15.543 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Adding to device queue

2020-12-30 21:07:15.543 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Added 8447 to queue - size 93

2020-12-30 21:07:15.544 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node Init response (1) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@3c38b6

2020-12-30 21:07:15.793 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 132: Sending REQUEST Message = 01 09 00 13 84 02 72 04 25 1E 2E 

2020-12-30 21:07:15.808 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: sentData successfully placed on stack.

2020-12-30 21:07:15.810 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8447: Transaction not completed

2020-12-30 21:07:17.688 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: ZWaveCommandClassTransactionPayload - send to node

2020-12-30 21:07:17.690 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: SECURITY NOT required on COMMAND_CLASS_MANUFACTURER_SPECIFIC

2020-12-30 21:07:17.691 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Command Class COMMAND_CLASS_MANUFACTURER_SPECIFIC is NOT required to be secured

2020-12-30 21:07:17.692 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1798338

2020-12-30 21:07:17.693 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Bump transaction 8449 priority from Config to Immediate

2020-12-30 21:07:17.695 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Adding to device queue

2020-12-30 21:07:17.696 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Added 8449 to queue - size 94

2020-12-30 21:07:20.810 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 132: TID 8447: Timeout at state WAIT_REQUEST. 3 retries remaining.

2020-12-30 21:07:32.813 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 132: TID 8447: Timeout at state ABORTED. 3 retries remaining.

2020-12-30 21:07:32.817 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2020-12-30 21:07:32.818 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: notifyTransactionResponse TID:8447 CANCELLED

2020-12-30 21:07:32.824 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 132: Sending REQUEST Message = 01 09 00 13 84 02 72 04 25 1F 2F 

2020-12-30 21:07:32.855 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: sentData successfully placed on stack.

2020-12-30 21:07:32.857 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8449: Transaction not completed

2020-12-30 21:07:33.613 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: SendData Request. CallBack ID = 31, Status = Transmission complete and ACK received(0)

2020-12-30 21:07:33.615 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8449: Transaction not completed

2020-12-30 21:07:33.632 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 132: SendData Request. CallBack ID = 31, Status = Transmission complete and ACK received(0)

2020-12-30 21:07:33.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: TID 8449: Transaction not completed

2020-12-30 21:07:38.616 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 132: TID 8449: Timeout at state WAIT_DATA. 3 retries remaining.

2020-12-30 21:07:38.618 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 132: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2020-12-30 21:07:38.620 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: notifyTransactionResponse TID:8449 CANCELLED

2020-12-30 21:07:38.623 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: Node Init response (1) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@93674d

2020-12-30 21:07:38.624 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: No data from device, but it was ACK'd. Possibly not supported? (Try 1)

2020-12-30 21:07:43.222 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 132: ZWaveCommandClassTransactionPayload - send to node

2020-12-30 21:07:43.223 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: SECURITY NOT required on COMMAND_CLASS_MANUFACTURER_SPECIFIC

2020-12-30 21:07:43.224 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 132: Command Class COMMAND_CLASS_MANUFACTURER_SPECIFIC is NOT required to be secured

2020-12-30 21:07:43.225 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1798338

2020-12-30 21:07:43.226 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Bump transaction 8450 priority from Config to Immediate

2020-12-30 21:07:43.228 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Adding to device queue

2020-12-30 21:07:43.229 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 132: Added 8450 to queue - size 92

It would bei awesome if someone has one more ideas what I could do to make that thing work. I have read also some other threats, but I haven’t found anything about a special secure inclusion process. The only thing: Don’t unplug the stick for the inclusion.

Is there anything I miss? I am getting a bit frustrated but on the other hand I have read that other people where able to include it. I believe I am very close but one little thing is probably just not perfect…

My USB Stick and the Door-Look is Smart Start compatible, would this be a better possibility to do the inclusion part?

No, because the binding does not support that.

In openhab 3 there are some options for the inclusion:

“Entry Control Devices” seems to me the right one or would you choose “All Devices”. Would that effect the conectivity to the other Devices?

@chris is likely the only one with the answer to your question.

It won’t change anything for any device that is included. This setting just sets what type of devices the binding will attempt to include securely - but it’s only relating to inclusion and won’t impact anything that is included.

Locks obviously must be included securely. Generally, most people probably don’t use security on other devices, and of course it’s up to you to decide if you are happy with that or not :slight_smile: . Security does increase traffic on the network by roughly twice, so it does tend to slow things down a very small amount, and might increase battery usage a very small amount, but likely you won’t notice either.

I hope that helps.

1 Like

Sorry @hofie81 - I missed that you’d posted the log - if you don’t reply to me, or mention me, then the forum doesn’t notify me and as I’m busy trying to move house, I’m not reading everything as closely as normal.

Looking at the above log, it has been filtered to only show certain lines. Unfortunately this then can’t be displayed with the log viewer as information needed is missing. Additionally, there are some long delays in the logs - I guess that maybe other traffic is going on to other devices, but it’s missing, so I can’t really say for sure.

1 Like

Hi Chris,
no problem, I am not expecting that anybody is helping. I would like to thank you guys for helping me, doing that in your free time!!!
I am trying very hard to get that door look working.
In openhab3 I choosed “All divices”. But still the same problems…

Would the following setting make sence to the main Controller:

The device must be included securely through the OH binding to work in OH. The security key is in the OH binding.

Yes I know, inclusion over OH :white_check_mark:
I guess you mean this key (it’s a bit longer -> Just for the screenshot):

I understood that I need to change from S2 to S0 Security, is that right?

S2 security devices are backward compatible, yes. OH does not support S2

Hi @chris ,

I made a reset, switched again to S0. Inclusion over OH.
“Secure Inclusion Mode” was set to “All Devices”.

The first log I have posted, I tryed to clean up the log for you, I guess that was not smart. I just did that to make it a bit more readable for you…

So here is a new log without any cleanup from my side:
events.log (8.4 KB)

OH3 -> Thing Properties:

Uh, I like the Z-Wave Network Map in OH3 (but I guess that is not helpfull…):
image

The setting was fine already - it was performing the inclusion.

The controller doesn’t support any command classes. All the commands on the “controller” side are managed in the binding alone.

What do you mean by this? I’m not really aware of a way to switch - the binding will resolve this normally. Or does the device maybe have a way to prevent S0 being used?

This log doesn’t have debug enabled so is unfortunately not of any use. The previous log had debug enabled, but you’d grep’d it and removed stuff that was needed…

If you want to look while waiting for Chris, here is the log viewer.

1 Like

I made a reset, switched again to S0
-> Reset of the Door Look and Switched on the Door Look from S2 to S0

… log doesn’t have debug enabled…
I did this: log:set DEBUG org.openhab.binding.zwave

So this is a configuration in the lock? I’m not really sure what that does to be honest, but it’s probably best left on S0. I could guess that it prevents S0 being used if you select S2, although S2 is required to fallback to S0 anyway…

1 Like

I’m not sure what to say. I double checked, and I don’t think I’m mistaken - the log is very short (maybe 50 lines or so) and I don’t see any debug entries. Am I looking at the wrong file? I don’t think so - even the forum says it’s only 8.4k which is clearly not very long.

Maybe events are wrong…
One sec…

So here are more details and this file was very very big, so I just have the part where the inclusion took part. I hope now this is what you where asking for:
openhab_Node137.log (265.7 KB)

THX, I am taking a look at it!