OH2 Z-Wave refactoring and testing... and SECURITY

5iver · October 14, 2017, 1:12pm

Thank you for the guess! Removing the xml and restarting OH seems to have cleared it up.

shorty707 · October 14, 2017, 6:17pm

Is a new Build with currrent db changes planned?
Cheers

chris · October 14, 2017, 6:48pm

Yes - I’ll do one tonight or tomorrow.

sihui · October 15, 2017, 5:58am

Updated this morning to 2.2.0.201710142330 (openHAB #1061), unfortunately still the same problem with association groups for lifeline: NPE in openhab.log, not much in zwave debug log:

tried setting the lifeline assocation group from a mains powered Fibaro rollershutter to openHAB controller:

and a battery powered D-Link motion sensor:

:

Edit: after restarting openHAB I often see a

2017-10-15 07:49:34.058 [WARN ] [ig.xml.osgi.XmlDocumentBundleTracker] - The XML document '/ESH-INF/binding/binding.xml' in module 'org.openhab.binding.zwave' could not be parsed: The XmlConfigDescriptionProvider must not be null!
java.lang.IllegalArgumentException: The XmlConfigDescriptionProvider must not be null!
	at org.eclipse.smarthome.core.binding.xml.internal.BindingInfoXmlProvider.<init>(BindingInfoXmlProvider.java:55) [102:org.eclipse.smarthome.core.binding.xml:0.9.0.201710101404]
	at org.eclipse.smarthome.core.binding.xml.internal.XmlBindingInfoProvider.createDocumentProvider(XmlBindingInfoProvider.java:136) [102:org.eclipse.smarthome.core.binding.xml:0.9.0.201710101404]
	at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.acquireXmlDocumentProvider(XmlDocumentBundleTracker.java:176) [98:org.eclipse.smarthome.config.xml:0.9.0.201710101404]
	at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.addingObject(XmlDocumentBundleTracker.java:201) [98:org.eclipse.smarthome.config.xml:0.9.0.201710101404]
	at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.parseDocuments(XmlDocumentBundleTracker.java:345) [98:org.eclipse.smarthome.config.xml:0.9.0.201710101404]
	at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.processBundle(XmlDocumentBundleTracker.java:331) [98:org.eclipse.smarthome.config.xml:0.9.0.201710101404]
	at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.access$3(XmlDocumentBundleTracker.java:326) [98:org.eclipse.smarthome.config.xml:0.9.0.201710101404]
	at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker$2.run(XmlDocumentBundleTracker.java:302) [98:org.eclipse.smarthome.config.xml:0.9.0.201710101404]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]

Matt77 · October 15, 2017, 6:21am

Hi,
just got my first Z-Wave device (DanaLock v3) with Security and thought to give it a try to include it in the network.
i’m currently running on the latest snapshot (Build #1061) am i right that i still need to manuall install the JAR file from the link above to get the security part up and running?

i actually triert that, removed all my z-Wave things, uninstalled the old binding and removed the old XMLs and installed the JAR file.
i got all nodes back running except my battery devices, they lost permanently the connection to the controller. even after excluding and re-including them.
went back to the binding included in the snapshot and all devices are back to normal.
however in both versions i did not get the Danalock by some reason fully initialized.

sorry if any of this was already covert earlier, but i could not find anything what helped to solve this problem.

shorty707 · October 15, 2017, 6:33am

build failed I think :

sihui · October 15, 2017, 6:33am

Yes.

That should almost never be necessary. After switching to the dev version you need to delete your things, delete any old xml files and then readd your things again.

You can only get them to work with the dev version. I don’t use any secure devices, but from what I have read above you need to do the device inclusion within the first couple of seconds (15s if I remember correctly) after inclusion mode of the controller has started and the secure device must be near the controller.
Also backup your network security key in case you need to include the secure devices again.

Matt77 · October 15, 2017, 7:56am

new try with new results,

after changing back to the dev version i have now even problems with 2 of my thermostats.
by some reason they are now listed as “failed by the controller”

2017-10-15 11:52:28.701 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Controller status changed to ONLINE.
2017-10-15 11:52:28.703 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Controller is ONLINE. Starting device initialisation.
2017-10-15 11:52:28.707 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating node properties.
2017-10-15 11:52:28.712 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating node properties. MAN=351
2017-10-15 11:52:28.714 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating node properties. MAN=351. SET. Was 351
2017-10-15 11:52:28.718 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Properties synchronised
2017-10-15 11:52:28.721 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Update ASSOCIATION group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@dfdc87: Adding node_1_null
2017-10-15 11:52:28.722 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Configuration synchronised
2017-10-15 11:52:33.743 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising Thing Node...
2017-10-15 11:52:33.745 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:15f1ee0619b:node20:sensor_temperature for DecimalType
2017-10-15 11:52:33.746 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:15f1ee0619b:node20:sensor_temperature for DecimalType
2017-10-15 11:52:33.748 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:15f1ee0619b:node20:thermostat_mode for DecimalType
2017-10-15 11:52:33.750 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:15f1ee0619b:node20:thermostat_mode for DecimalType
2017-10-15 11:52:33.753 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:15f1ee0619b:node20:thermostat_state for DecimalType
2017-10-15 11:52:33.756 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:15f1ee0619b:node20:thermostat_state for DecimalType
2017-10-15 11:52:33.760 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:15f1ee0619b:node20:thermostat_setpoint_cooling for DecimalType
2017-10-15 11:52:33.763 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:15f1ee0619b:node20:thermostat_setpoint_cooling for DecimalType
2017-10-15 11:52:33.765 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:15f1ee0619b:node20:thermostat_setpoint_heating for DecimalType
2017-10-15 11:52:33.768 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:15f1ee0619b:node20:thermostat_setpoint_heating for DecimalType
2017-10-15 11:52:33.771 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:15f1ee0619b:node20:thermostat_fanmode for DecimalType
2017-10-15 11:52:33.773 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:15f1ee0619b:node20:thermostat_fanmode for DecimalType
2017-10-15 11:52:33.776 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:15f1ee0619b:node20:thermostat_fanstate for DecimalType
2017-10-15 11:52:33.778 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:15f1ee0619b:node20:thermostat_fanstate for DecimalType
2017-10-15 11:52:33.780 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Polling intialised at 1800 seconds - start in 1800000 milliseconds.
2017-10-15 11:52:33.783 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Device initialisation complete.
2017-10-15 11:52:37.311 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 20: Requesting IsFailedNode status from controller.
2017-10-15 11:52:37.388 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 20: Is currently marked as failed by the controller!
2017-10-15 11:52:37.414 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node Init response (0) COMPLETE
2017-10-15 11:52:37.416 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node Init transaction completed with response COMPLETE
2017-10-15 11:53:07.418 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 20: Requesting IsFailedNode status from controller.
2017-10-15 11:53:07.509 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 20: Is currently marked as failed by the controller!
2017-10-15 11:53:07.532 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node Init response (0) COMPLETE
2017-10-15 11:53:07.533 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node Init transaction completed with response COMPLETE
2017-10-15 11:53:37.534 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 20: Requesting IsFailedNode status from controller.
2017-10-15 11:53:37.596 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 20: Is currently marked as failed by the controller!
2017-10-15 11:53:37.632 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node Init response (0) COMPLETE
2017-10-15 11:53:37.633 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node Init transaction completed with response COMPLETE

any idea ?

chris · October 15, 2017, 8:51am

No - I did the update.

sihui · October 15, 2017, 9:00am

Wake them up

chris · October 15, 2017, 9:00am

Well, that’s not surprising. As I said earlier, we need more debug information and until this is fixed I’m a bit stuck. My current guess is that the problem isn’t in the binding, but I just don’t know. I have two tests that test the setting of associations, and both work. I know the framework does other tests and I guess that this is throwing up the problem

The issue isn’t with the setting of associations, so logs here don’t help .

The reading of XML files is all done in the framework core so I’m not sure what this is about. The binding doesn’t have anything to do with this.

sihui · October 15, 2017, 9:02am

It’s not too big of a problem because all devices are working and I also can change the config parameter settings without any problems …

Matt77 · October 15, 2017, 9:05am

@sihui

ok that worked
did not thought of that since they aren’t battery devices.

shorty707 · October 15, 2017, 9:51am

ah but at least the build non security version failed ?
https://openhab.ci.cloudbees.com/job/openHAB2-Bundles/lastFailedBuild/

chris · October 15, 2017, 9:53am

Yes, that build seems to have a problem, but nothing to do with ZWave as far as I can tell. Since this thread is the secure thread I try not to confuse things as that build is very different.

stevenazari · October 15, 2017, 11:57am

All locks need to be added securely or won’t have full / any functionality.

You will need to clear your module because once registered, z wave module automatically picks it up, even if not added securely.

Matt77 · October 15, 2017, 3:23pm

i got all of my none secure devices back running except one, my Fibaro FGK101 door/window contact.
even after several wake-up its not recognition that its open.

2017-10-15 18:35:40.553 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 1C 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 0E 
2017-10-15 18:35:40.563 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-10-15 18:35:40.573 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=28, callback=0, payload=00 1C 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 
2017-10-15 18:35:40.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=28, callback=0, payload=00 1C 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 
2017-10-15 18:35:40.594 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=28, callback=0, payload=00 1C 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 
2017-10-15 18:35:40.596 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-10-15 18:35:40.600 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Application Command Request (ALIVE:DONE)
2017-10-15 18:35:40.603 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: resetResendCount initComplete=true isDead=false
2017-10-15 18:35:40.607 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-10-15 18:35:40.611 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: COMMAND_CLASS_MULTI_CHANNEL not found
2017-10-15 18:35:40.614 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-10-15 18:35:40.617 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2017-10-15 18:35:40.621 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: listening == false, frequentlyListening == false, awake == false
2017-10-15 18:35:40.624 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Node not awake!
2017-10-15 18:35:40.628 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 26: listening == false, frequentlyListening == false, awake == false
2017-10-15 18:35:40.631 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 26: Node not awake!
2017-10-15 18:35:40.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
2017-10-15 18:35:40.638 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing

stevenazari · October 15, 2017, 3:55pm

Just a couple of questions:

Is a window contact considered a security device?
Is the device listed in Chris’ Database?
When adding the thing to zwave binding, is your log confirming it added securely?

if 1 of these are true, all must be true to work properly and if 3 is true, it should be working as intended.

Matt77 · October 15, 2017, 5:16pm

@stevenazari

no
yes (its working with the binding form the snapshot)
no (its not a secure device)

i removed an re added the device to the zwave network. now im getting an error that one Command_clase_multi_channel not found.

2017-10-15 21:12:39.644 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Incoming command class COMMAND_CLASS_WAKE_UP, endpoint 0
2017-10-15 21:12:39.646 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: SECURITY NOT required on COMMAND_CLASS_WAKE_UP
2017-10-15 21:12:39.648 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 31: Received COMMAND_CLASS_WAKE_UP V2 WAKE_UP_NOTIFICATION
2017-10-15 21:12:39.649 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Is awake with 0 messages in the queue
2017-10-15 21:12:39.650 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Creating WakeupTimerTask
2017-10-15 21:12:39.651 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Creating WakeupTimerTask
2017-10-15 21:12:39.654 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2017-10-15 21:12:39.656 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 31: Node Status event - Node is AWAKE
2017-10-15 21:12:39.658 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Commands processed 1.
2017-10-15 21:12:39.659 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@11b5ecd.
2017-10-15 21:12:40.152 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: listening == false, frequentlyListening == false, awake == true
2017-10-15 21:12:40.155 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: WakeupTimerTask 0 Messages waiting, state DONE
2017-10-15 21:12:40.157 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: WakeupTimerTask First iteration
2017-10-15 21:12:40.653 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: listening == false, frequentlyListening == false, awake == true
2017-10-15 21:12:40.657 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: WakeupTimerTask 0 Messages waiting, state DONE
2017-10-15 21:12:40.660 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: No more messages, go back to sleep
2017-10-15 21:12:40.663 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 31: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2017-10-15 21:12:40.670 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Encapsulating message, endpoint 0
2017-10-15 21:12:40.673 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: SECURITY NOT required on COMMAND_CLASS_WAKE_UP
2017-10-15 21:12:40.676 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2017-10-15 21:12:40.679 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1fe4342
2017-10-15 21:12:40.683 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Adding to device queue
2017-10-15 21:12:40.687 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Added to queue - size 0
2017-10-15 21:12:40.694 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: listening == false, frequentlyListening == false, awake == true
2017-10-15 21:12:40.710 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 31: Sending REQUEST Message = 01 09 00 13 1F 02 84 08 25 A4 F5 
2017-10-15 21:12:40.779 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 31: sentData successfully placed on stack.
2017-10-15 21:12:40.787 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: TID 200: Transaction not completed
2017-10-15 21:12:40.798 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 31: SendData Request. CallBack ID = 164, Status = Transmission complete and ACK received(0)
2017-10-15 21:12:40.799 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: resetResendCount initComplete=true isDead=false
2017-10-15 21:12:40.807 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Response processed after 79ms
2017-10-15 21:12:40.808 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: TID 200: Transaction completed
2017-10-15 21:12:40.809 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: notifyTransactionResponse TID:200 DONE
2017-10-15 21:12:40.812 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-10-15 21:12:40.813 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: -- To notify -- COMPLETE
2017-10-15 21:12:40.815 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Went to sleep COMPLETE
2017-10-15 21:12:59.907 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Application Command Request (ALIVE:DONE)
2017-10-15 21:12:59.909 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: resetResendCount initComplete=true isDead=false
2017-10-15 21:12:59.911 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-10-15 21:12:59.913 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: COMMAND_CLASS_MULTI_CHANNEL not found
2017-10-15 21:13:01.239 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Application Command Request (ALIVE:DONE)
2017-10-15 21:13:01.241 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: resetResendCount initComplete=true isDead=false
2017-10-15 21:13:01.243 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-10-15 21:13:01.245 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: COMMAND_CLASS_MULTI_CHANNEL not found
2017-10-15 21:13:30.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Application Command Request (ALIVE:DONE)
2017-10-15 21:13:30.441 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: resetResendCount initComplete=true isDead=false
2017-10-15 21:13:30.444 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-10-15 21:13:30.447 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: COMMAND_CLASS_MULTI_CHANNEL not found

one more log entrie

2017-10-15 21:17:49.118 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 1F 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 0C 
2017-10-15 21:17:49.121 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-10-15 21:17:49.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=31, callback=0, payload=00 1F 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 
2017-10-15 21:17:49.126 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=31, callback=0, payload=00 1F 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 
2017-10-15 21:17:49.129 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=31, callback=0, payload=00 1F 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 
2017-10-15 21:17:49.130 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-10-15 21:17:49.132 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 31: Application Command Request (ALIVE:DONE)
2017-10-15 21:17:49.134 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: resetResendCount initComplete=true isDead=false
2017-10-15 21:17:49.136 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2017-10-15 21:17:49.137 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 31: COMMAND_CLASS_MULTI_CHANNEL not found

Matt77 · October 15, 2017, 5:51pm

@chris
Hi Chris,
i got my lock integrated and everything seems to be OK that it’s using a secured connection.

it also shows it in the DB but its not getting updated in HABmin. is it maybe not yet in the latest snapshot integrated?