ZWave New COMMAND_CLASS Requests

Hi @chris,

I wanted to throw out a requests for two command classes.

  1. The “Indicator” command class ( 0x87) which I think just needs to support (0) off and (255) on. This gives me the ability to completely turn off the blue and yellow LEDs on my Cooper switches. The lights are a just bit bright and would be nice to darken the bedrooms. I think this was supported in a highly customized form in the openhab 1 binding targeted mainly at a scene controller, but it never worked well for me.

  2. The “Protection” command class (0x75) allows to lock out local control (Child protection). There are three supported settings:
    (0) Unprotected
    (1) Protection by sequence
    (2) No operation possible


 *** Protection Mode -- Child Protection per manufacturer:
    Child protection is a way to prevent local control of an Aspire RF switch, dimmer or receptacle. There are three settings:
    - No protections allows the device to work normally
    - Sequence Control requires the user to tap the device three times to make it work
    - Remote Only completely locks out the face of the device (but Panic Mode will still be turned off with switch press)

I’d be happy to have a stab at adding them myself, but I’m not even sure where to start.

Ref:
-Most of my cooper switches RF9540-N

-I hope this is not a faux pas, but another smart hub seems to have a customized support for the protection command class, I’ll include a link in case it sheds any light on the interface: Protection Command Class

I believe both command classes are supported at the moment. I also think that protection has a converter already written but indicator currently doesn’t. I’ll look at doing the indicator one in a few weeks - there’s currently an open issue about this already.

1 Like

That’s great! How can I add a protection channel to the database? It looks as though for my case it should be “protection_local”, but I’m missing a little green +.

Is there another way to access the converter outside of a channel. I can’t find anything in the forums about it.

I added the following to the jsondb to test it and it works great!

{
          "acceptedItemType": "Decimal",
          "kind": "STATE",
          "uid": {
            "segments": [
              "zwave",
              "device",
              "zwavedev",
              "node22",
              "protection_local"
            ]
          },
          "channelTypeUID": {
            "segments": [
              "zwave",
              "protection_local"
            ]
          },
          "label": "Local Protection",
          "description": "Activates Local Protection",
          "configuration": {
            "properties": {}
          },
          "properties": {
            "binding:*:DecimalType": "COMMAND_CLASS_PROTECTION;type\u003dPROTECTION_LOCAL"
          },
          "defaultTags": []
		  },

My Item definition:

Number	Dimmer_22_slide_protection	"Living Room Ceiling Protection [%d]"	(LR_Lights) {channel="zwave:device:zwavedev:node22:protection_local" }

@chris, is it possible to add the protection_local channel under protection on your site? The little green plus sign isn’t available for protection.

I’ve hopefully added it to the list of classes, but it still won’t export - I’ll look at that tomorrow. Can you add the channel to a device and I’ll look at the exporter in the morning (let me know what device you update).

Great, thanks!

I’ve updated the RF9540-N
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/16

Thanks. Note that you need the type= in the options (just FYI in case you are going to add this to other devices :wink: ).

I’ve updated the exporter so this should be available in future database updates.

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/16?layout=openhab2new

If you spot any issues, please let me know…

Excellent, I’m looking forward to testing on the next build.

I’ve just updated the security build - let me know how it looks…

Cheers
Chris

I can successfully update parameter=8 through the habmin gui and the device goes into the correct operating mode, but when I use a bound item to the channel it does not affect the device. It does reflect the correct value in habmin when I update the channel directly.

Here is the debug log when I send number 0 to the channel: (node 96)

2018-01-21 21:20:28.732 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 96: Command received zwave:device:de0bde91:node96:config_decimal_param8 --> 0
2018-01-21 21:20:28.740 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 96: Creating new message for application command CONFIGURATION_SET
2018-01-21 21:20:28.743 [DEBUG] [ommandClassTransactionPayloadBuilder] - At build null
2018-01-21 21:20:28.745 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 96: Creating new message for application command CONFIGURATIONCMD_GET
2018-01-21 21:20:28.747 [DEBUG] [ommandClassTransactionPayloadBuilder] - At build COMMAND_CLASS_CONFIGURATION
2018-01-21 21:20:28.749 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: Adding to device queue
2018-01-21 21:20:28.751 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: Added to queue - size 4
2018-01-21 21:20:28.753 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-01-21 21:20:28.755 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 62: listening == false, frequentlyListening == false, awake == false
2018-01-21 21:20:28.757 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 62: Node not awake!
2018-01-21 21:20:28.759 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: listening == false, frequentlyListening == false, awake == false
2018-01-21 21:20:28.761 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Node not awake!
2018-01-21 21:20:28.763 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 89: listening == false, frequentlyListening == false, awake == false
2018-01-21 21:20:28.765 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 89: Node not awake!
2018-01-21 21:20:28.766 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 96: listening == false, frequentlyListening == true, awake == false
2018-01-21 21:20:28.768 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from sendQueue
2018-01-21 21:20:28.770 [DEBUG] [nal.protocol.ZWaveTransactionManager] - getTransactionToSend 6
2018-01-21 21:20:28.779 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-01-21 21:20:28.780 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-01-21 21:20:28.780 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-01-21 21:20:28.781 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-01-21 21:20:28.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-01-21 21:20:28.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-01-21 21:20:28.783 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-01-21 21:20:28.784 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-01-21 21:20:28.800 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-01-21 21:20:28.803 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: Transaction Start type SendData 
2018-01-21 21:20:28.805 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1354: [WAIT_RESPONSE] requiresResponse=false callback: 136
2018-01-21 21:20:28.807 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd class: null
2018-01-21 21:20:28.809 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd: 0
2018-01-21 21:20:28.811 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage Transactions outstanding: 1
2018-01-21 21:20:28.813 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:30 EST 2018 - 2000ms
2018-01-21 21:20:28.816 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage lastTransaction: TID 1354: [WAIT_RESPONSE] requiresResponse=false callback: 136
2018-01-21 21:20:28.818 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:28.820 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:30 EST 2018 - 1993ms
2018-01-21 21:20:28.822 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction lastTransaction outstanding...
2018-01-21 21:20:28.823 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:28.824 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:30 EST 2018 - 1990ms
2018-01-21 21:20:28.824 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: Adding to device queue
2018-01-21 21:20:28.825 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: Added to queue - size 4
2018-01-21 21:20:28.826 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start
2018-01-21 21:20:28.827 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction lastTransaction outstanding...
2018-01-21 21:20:28.828 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:28.829 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:30 EST 2018 - 1984ms
2018-01-21 21:20:28.831 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:28.831 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:28.832 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:28.833 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1354: [WAIT_RESPONSE] requiresResponse=false callback: 136
2018-01-21 21:20:28.834 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-01-21 21:20:28.834 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1354: [WAIT_RESPONSE] requiresResponse=false callback: 136
2018-01-21 21:20:28.835 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:28.836 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 96: sentData successfully placed on stack.
2018-01-21 21:20:28.836 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance ST: WAIT_RESPONSE
2018-01-21 21:20:28.837 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance WT: null {}
2018-01-21 21:20:28.838 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance RX: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:28.838 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance TO: WAIT_REQUEST
2018-01-21 21:20:28.839 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1354: Advanced to WAIT_REQUEST
2018-01-21 21:20:28.840 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: TID 1354: Transaction not completed
2018-01-21 21:20:28.906 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-01-21 21:20:28.908 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start
2018-01-21 21:20:28.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction lastTransaction outstanding...
2018-01-21 21:20:28.911 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:28.913 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:33 EST 2018 - 4927ms
2018-01-21 21:20:30.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=136, payload=88 00 00 83 
2018-01-21 21:20:30.122 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=SendData[19], type=Request[0], dest=0, callback=136, payload=88 00 00 83 
2018-01-21 21:20:30.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=136, payload=88 00 00 83 
2018-01-21 21:20:30.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1354: [WAIT_REQUEST] requiresResponse=false callback: 136
2018-01-21 21:20:30.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-01-21 21:20:30.126 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1354: [WAIT_REQUEST] requiresResponse=false callback: 136
2018-01-21 21:20:30.126 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 1354: (Callback 136)
2018-01-21 21:20:30.127 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2018-01-21 21:20:30.128 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 1354: callback 136
2018-01-21 21:20:30.129 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=136, payload=88 00 00 83 
2018-01-21 21:20:30.130 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 96: SendData Request. CallBack ID = 136, Status = Transmission complete and ACK received(0)
2018-01-21 21:20:30.131 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 96: resetResendCount initComplete=true isDead=false
2018-01-21 21:20:30.131 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: Transaction COMPLETED
2018-01-21 21:20:30.132 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance ST: DONE
2018-01-21 21:20:30.132 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance WT: null {}
2018-01-21 21:20:30.133 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance RX: Message: class=SendData[19], type=Request[0], dest=0, callback=136, payload=88 00 00 83 
2018-01-21 21:20:30.134 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1354: TransactionAdvance TO: DONE
2018-01-21 21:20:30.134 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: Response processed after 1332ms
2018-01-21 21:20:30.135 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: TID 1354: Transaction completed
2018-01-21 21:20:30.136 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: notifyTransactionResponse TID:1354 DONE
2018-01-21 21:20:30.136 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2018-01-21 21:20:30.137 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 96: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-01-21 21:20:30.138 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-01-21 21:20:30.138 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-01-21 21:20:30.139 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 62: listening == false, frequentlyListening == false, awake == false
2018-01-21 21:20:30.140 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 62: Node not awake!
2018-01-21 21:20:30.141 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: listening == false, frequentlyListening == false, awake == false
2018-01-21 21:20:30.141 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Node not awake!
2018-01-21 21:20:30.142 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 89: listening == false, frequentlyListening == false, awake == false
2018-01-21 21:20:30.142 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 89: Node not awake!
2018-01-21 21:20:30.143 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 96: listening == false, frequentlyListening == true, awake == false
2018-01-21 21:20:30.144 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from sendQueue
2018-01-21 21:20:30.144 [DEBUG] [nal.protocol.ZWaveTransactionManager] - getTransactionToSend 6
2018-01-21 21:20:30.145 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = redacted
2018-01-21 21:20:30.146 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 96: Sending REQUEST Message = redacted
2018-01-21 21:20:30.149 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-01-21 21:20:30.151 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-01-21 21:20:30.153 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-01-21 21:20:30.155 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = redacted
2018-01-21 21:20:30.170 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-01-21 21:20:30.171 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: Transaction Start type SendData 
2018-01-21 21:20:30.172 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1355: [WAIT_RESPONSE] requiresResponse=false callback: 137
2018-01-21 21:20:30.173 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd class: COMMAND_CLASS_CONFIGURATION
2018-01-21 21:20:30.174 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd: 6
2018-01-21 21:20:30.175 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage Transactions outstanding: 1
2018-01-21 21:20:30.175 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:30.176 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:32 EST 2018 - 1999ms
2018-01-21 21:20:30.177 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage lastTransaction: TID 1355: [WAIT_RESPONSE] requiresResponse=false callback: 137
2018-01-21 21:20:30.178 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:30.179 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:32 EST 2018 - 1996ms
2018-01-21 21:20:30.180 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-01-21 21:20:30.181 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1355: [WAIT_RESPONSE] requiresResponse=false callback: 137
2018-01-21 21:20:30.181 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-01-21 21:20:30.182 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-01-21 21:20:30.183 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start
2018-01-21 21:20:30.184 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction lastTransaction outstanding...
2018-01-21 21:20:30.184 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:30.185 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:32 EST 2018 - 1990ms
2018-01-21 21:20:30.200 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:30.202 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:30.204 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:30.205 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1355: [WAIT_RESPONSE] requiresResponse=false callback: 137
2018-01-21 21:20:30.205 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = redacted
2018-01-21 21:20:30.206 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-01-21 21:20:30.207 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1355: [WAIT_RESPONSE] requiresResponse=false callback: 137
2018-01-21 21:20:30.208 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:30.209 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 96: sentData successfully placed on stack.
2018-01-21 21:20:30.210 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance ST: WAIT_RESPONSE
2018-01-21 21:20:30.211 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance WT: ApplicationCommandHandler {}
2018-01-21 21:20:30.212 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance RX: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2018-01-21 21:20:30.212 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance TO: WAIT_REQUEST
2018-01-21 21:20:30.213 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1355: Advanced to WAIT_REQUEST
2018-01-21 21:20:30.214 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: TID 1355: Transaction not completed
2018-01-21 21:20:30.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-01-21 21:20:30.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start
2018-01-21 21:20:30.216 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction lastTransaction outstanding...
2018-01-21 21:20:30.217 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2018-01-21 21:20:30.218 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Sun Jan 21 21:20:35 EST 2018 - 4996ms
2018-01-21 21:20:30.230 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=137, payload=redacted
2018-01-21 21:20:30.233 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=SendData[19], type=Request[0], dest=0, callback=137, payload=redacted
2018-01-21 21:20:30.242 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=137, payload=redacted
2018-01-21 21:20:30.243 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1355: [WAIT_REQUEST] requiresResponse=false callback: 137
2018-01-21 21:20:30.244 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-01-21 21:20:30.245 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1355: [WAIT_REQUEST] requiresResponse=false callback: 137
2018-01-21 21:20:30.246 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 1355: (Callback 137)
2018-01-21 21:20:30.247 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2018-01-21 21:20:30.248 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 1355: callback 137
2018-01-21 21:20:30.249 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=137, payload=89 00 00 02 
2018-01-21 21:20:30.251 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 96: SendData Request. CallBack ID = 137, Status = Transmission complete and ACK received(0)
2018-01-21 21:20:30.252 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 96: resetResendCount initComplete=true isDead=false
2018-01-21 21:20:30.253 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance ST: WAIT_REQUEST
2018-01-21 21:20:30.254 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance WT: ApplicationCommandHandler {}
2018-01-21 21:20:30.255 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance RX: Message: class=SendData[19], type=Request[0], dest=0, callback=137, payload=redacted
2018-01-21 21:20:30.256 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance RQ: RREQ=false, RCLS=ApplicationCommandHandler
2018-01-21 21:20:30.257 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1355: TransactionAdvance TO: DONE
2018-01-21 21:20:30.258 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1355: Advanced to DONE
2018-01-21 21:20:30.259 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: Response processed after 88ms
2018-01-21 21:20:30.260 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: TID 1355: Transaction completed
2018-01-21 21:20:30.261 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 96: notifyTransactionResponse TID:1355 DONE
2018-01-21 21:20:30.263 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2018-01-21 21:20:30.265 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 96: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-01-21 21:20:30.266 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-01-21 21:20:30.268 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2018-01-21 21:20:30.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
2018-01-21 21:20:30.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
2018-01-21 21:20:30.281 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer

Here is the log while I update directly from the habmin configuration paramaters field to “vacation” (2):

From the short log it looks like the packets are being created ok, but without the fully log it’s hard to say. Can you open a ticket on my site and provide the full log (ie without the redacted packet information)?

I just submitted 2 full log files, see ticket w2zBfGW9NFZ.

It seems that the configuration converter may not be utilizing the same security checks. I don’t see any of the security logging happening when updating via the channel:

Command Class COMMAND_CLASS_CONFIGURATION is required to be secured

@chris, I don’t mean to pester. Is there any more information I can get you for this, are the logs sufficient?

The protection command class works swimmingly! Thank you for that.

Sorry for the delay - I see the problem and I’ve made a fix. I’ll probably do a binding update later tonight (UK time).

It works perfectly now, thank you!

1 Like