The openHAB xml for node 10 looks unusual to me and the device type & id do not match those submitted to the zwave alliance.
https://products.z-wavealliance.org/products/3230
What do you mean? the database uses the unedited xml file from openHAB as a starting point.
So I have to upload the node 10 xml with all its strangeness?
Strange to you but not to the binding & database. 
Its contents come directly from the device.
Looking at the XML, I doubt that the device is included correctly. Are you really sure that it completed the security handshake correctly?
I’d probably avoid uploading this at the moment as it doesn’t look correct.
So, work is done 
I was able to include the door lock so that it produced a better xml. I then uploaded it to the device data base, completed the database entry with data from the manual and the Z-Wave document ABUECFA3010S and requested a review. Hopefully the review will be positive and the device will be included in the next database release
But how can I use the xml I exported from the database in my openHAB installation? Where do I have to put it so that my door lock will be recognized correctly afte re-inclusion? I’m running openHABian 2.5 on a Raspberry Pi 4…
@Chris:
I used the device editor for the first time and it was fantastic. You did a great work 
You can either wait for the database export and snapshot binding or , if you are adventurous, there is a thread about rebuilding a binding jar file.
Modify a zwave binding jar to add/change a zwave device while waiting for a build - Tutorials & Examples - openHAB Community
Would you please remove the heading2 tags. I started editing it but you did use it on almost every entry and I don’t have time to finish this.
This is important for the documentation and its visual display.
Please have a look at the docs to verify how your html tags are looking (please use them sparely, if not at all).
Example: ZWave Thing | openHAB
You may also use the Export … MD Documentation button on the database side to have preview.
Thx.
Hi sihui,
to my mind all h2-tags are removed. I think they where included when I did copy and paste from the online manual of the manufacturer. Now I hope it satisfies the needs of the database.
Thx, looks good now. Approved.
A hint for your next database edit: copy content from online manuals or pdf to an ascii editor first (for example notepad++) and then to the database window.
This removes all those nasty tags.
Hi suhui,
thanks for the hint.
As always: afterwards you’re always smarter! Learning by doing 
But I’m looking for my next device
I can tell you that I was able to include the door lock successfully after:
Thanks for help adding this device to the database
I tryed to include the CFA3010 in openhab 2.5 and now on openhab 3.
I get: Device discovery could not resolve to a thingType! Manufacturer data not known
I swiched from S2 to S0. I did a exclude and a include, but still, openhab is not able to handle this device.
I found the XML here:
So I guess its in the Database. If I try to look at:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list
I get the response “File not found.” - Status 404…
So I am right now stuck and would be very happy if someone could give me a little hint, that would be very nice!
The database moved last year.
I believe it should work with OH3. The database entry is here.
That usually means a battery operated device has not been woken up enough to be fully discovered. Door locks in secure mode can be especially problematic due to tight timing constraints.
They need to be factory reset between secure attempts… Inclusion needs to be through the binding.
Thanks for the very fast reply, I wasn’t expecting to get a answer that quick.
What I did:
In the log I found this:
NODE 124: Device discovery could not resolve to a thingType! Manufacturer data not known.
And the thing (openhab UI):
Is there anything I can/should do now?
The Thing Properties are looking good to me (SPECIFIC_TYPE_SECURE_KEYPAD_DOOR_LOCK):
It seems to me that the binding is not communicating with the device if it doesn’t know the manufacturer information. It is however a bit hard to know what is happening without seeing what’s in the logs…
That’s not really important though, and doesn’t mean that there is communication with the device and the binding. It doesn’t mean that the device has securely included either.
If you can provide the log during the secure inclusion it might be useful.
I got the “aeotec z-wave stick gen5”, so for ex and include I unplug the stick. I guess there is no log about the inclusion, or?
Do I need to change something here because its a lock:
Well, that’s your problem. You cannot do that. It will not work and the secure inclusion will fail.
Okay, good to know.
I did everything again (Exclude, Reset, Switch from S2 to S0 & the include over openhab).
Now I found the Log:
2020-12-27 23:55:14.300 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 126: SECURITY_INC State=FAILED, Reason=GET_SCHEME
2020-12-27 23:55:14.307 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 126: Device discovery could not resolve to a thingType! Manufacturer data not known.
I can’t really add a lot - clearly the secure inclusion has not worked. Without seeing the full debug log, I can’t really comment much more. Take a look at the binding docs if you haven’t enabled debug logging (and maybe also read the part about secure inclusion ).
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