ADC-T 2000 Thermostat (ADT, Alarm.com) Config Parameters Non-Responsive

Hardware Home Automation
1

Does anyone have any experience with the configuration parameters of this device, or have any ideas on my issue? I was trying to adjust the configuration temperature and the swing setting, but those settings don’t seem work. For example, if I provide a calibration value, it appears to save, but the temperature on the unit does not change. The swing setting also seems to update correctly, but it operates as if still on its default value. Here is a debug log after updating parameter 7 (Swing) to 15, with the intention of setting the swing to 1.5 degrees:

2020-03-05 15:09:27.258 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update received
2020-03-05 15:09:27.269 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update set config_7_4 to 15 (BigDecimal)
2020-03-05 15:09:27.272 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 82: Creating new message for application command CONFIGURATION_SET
2020-03-05 15:09:27.275 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: SECURITY not supported
2020-03-05 15:09:27.278 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured
2020-03-05 15:09:27.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Adding to device queue
2020-03-05 15:09:27.283 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Added 6026 to queue - size 29
2020-03-05 15:09:27.286 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-03-05 15:09:27.292 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 13 52 08 70 04 07 04 00 00 00 0F 25 85 61 
2020-03-05 15:09:27.296 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 82: Sending REQUEST Message = 01 0F 00 13 52 08 70 04 07 04 00 00 00 0F 25 85 61 
2020-03-05 15:09:27.299 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2020-03-05 15:09:27.302 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2020-03-05 15:09:27.302 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 6026: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 133
2020-03-05 15:09:27.307 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-03-05 15:09:27.309 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-03-05 15:09:27.308 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 82: Creating new message for application command CONFIGURATIONCMD_GET
2020-03-05 15:09:27.311 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 6026: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 133
2020-03-05 15:09:27.310 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2020-03-05 15:09:27.312 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2020-03-05 15:09:27.312 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: SECURITY not supported
2020-03-05 15:09:27.314 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-03-05 15:09:27.314 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2020-03-05 15:09:27.315 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-03-05 15:09:27.316 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured
2020-03-05 15:09:27.318 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2020-03-05 15:09:27.319 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 6026: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 133
2020-03-05 15:09:27.319 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Adding to device queue
2020-03-05 15:09:27.322 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Added 6027 to queue - size 29
2020-03-05 15:09:27.325 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-03-05 15:09:27.328 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2020-03-05 15:09:27.330 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 6026: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 133
2020-03-05 15:09:27.332 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2020-03-05 15:09:27.335 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: sentData successfully placed on stack.
2020-03-05 15:09:27.337 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 6026: Advanced to WAIT_REQUEST
2020-03-05 15:09:27.340 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 6026: Transaction not completed
2020-03-05 15:09:27.342 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-03-05 15:09:27.344 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-03-05 15:09:27.355 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 85 00 00 05 6B 
2020-03-05 15:09:27.359 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=133, payload=85 00 00 05 
2020-03-05 15:09:27.364 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=133, payload=85 00 00 05 
2020-03-05 15:09:27.369 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 6026: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 133
2020-03-05 15:09:27.375 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2020-03-05 15:09:27.377 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 6026: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 133
2020-03-05 15:09:27.379 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 6026: (Callback 133)
2020-03-05 15:09:27.381 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2020-03-05 15:09:27.383 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 6026: callback 133
2020-03-05 15:09:27.385 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=133, payload=85 00 00 05 
2020-03-05 15:09:27.387 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: SendData Request. CallBack ID = 133, Status = Transmission complete and ACK received(0)
2020-03-05 15:09:27.389 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2020-03-05 15:09:27.391 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 6026: Transaction COMPLETED
2020-03-05 15:09:27.393 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Response processed after 90ms
2020-03-05 15:09:27.394 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 6026: Transaction completed
2020-03-05 15:09:27.396 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: notifyTransactionResponse TID:6026 DONE
2020-03-05 15:09:27.399 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-03-05 15:09:27.401 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-03-05 15:09:27.402 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-03-05 15:09:27.406 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 52 03 70 05 07 25 86 66 
2020-03-05 15:09:27.409 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 82: Sending REQUEST Message = 01 0A 00 13 52 03 70 05 07 25 86 66 
2020-03-05 15:09:27.411 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2020-03-05 15:09:27.412 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 6027: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 134
2020-03-05 15:09:27.412 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2020-03-05 15:09:27.414 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-03-05 15:09:27.416 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-03-05 15:09:27.417 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 6027: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 134
2020-03-05 15:09:27.419 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2020-03-05 15:09:27.419 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2020-03-05 15:09:27.420 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-03-05 15:09:27.422 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2020-03-05 15:09:27.422 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-03-05 15:09:27.424 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2020-03-05 15:09:27.425 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 6027: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 134
2020-03-05 15:09:27.427 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2020-03-05 15:09:27.428 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 6027: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 134
2020-03-05 15:09:27.430 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2020-03-05 15:09:27.432 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: sentData successfully placed on stack.
2020-03-05 15:09:27.433 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 6027: Advanced to WAIT_REQUEST
2020-03-05 15:09:27.435 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 6027: Transaction not completed
2020-03-05 15:09:27.436 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-03-05 15:09:27.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-03-05 15:09:27.462 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 86 00 00 04 69 
2020-03-05 15:09:27.465 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=134, payload=86 00 00 04 
2020-03-05 15:09:27.467 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=134, payload=86 00 00 04 
2020-03-05 15:09:27.468 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 6027: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 134
2020-03-05 15:09:27.476 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2020-03-05 15:09:27.477 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 6027: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 134
2020-03-05 15:09:27.479 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 6027: (Callback 134)
2020-03-05 15:09:27.483 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2020-03-05 15:09:27.485 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 6027: callback 134
2020-03-05 15:09:27.487 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=134, payload=86 00 00 04 
2020-03-05 15:09:27.488 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: SendData Request. CallBack ID = 134, Status = Transmission complete and ACK received(0)
2020-03-05 15:09:27.490 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2020-03-05 15:09:27.491 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 6027: Advanced to WAIT_DATA
2020-03-05 15:09:27.492 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 6027: Transaction not completed
2020-03-05 15:09:27.493 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-03-05 15:09:27.495 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-03-05 15:09:27.539 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 52 08 70 06 07 04 2A 00 00 00 F0 
2020-03-05 15:09:27.544 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 08 70 06 07 04 2A 00 00 00 
2020-03-05 15:09:27.547 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 08 70 06 07 04 2A 00 00 00 
2020-03-05 15:09:27.548 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-03-05 15:09:27.550 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Application Command Request (ALIVE:DONE)
2020-03-05 15:09:27.551 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2020-03-05 15:09:27.553 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Incoming command class COMMAND_CLASS_CONFIGURATION, endpoint 0
2020-03-05 15:09:27.554 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: SECURITY not supported
2020-03-05 15:09:27.555 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 82: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT
2020-03-05 15:09:27.557 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 82: Node configuration report, parameter = 7, value = 704643072, size = 4
2020-03-05 15:09:27.558 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent
2020-03-05 15:09:27.560 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CONFIGURATION, value=org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@f1dd3f
2020-03-05 15:09:27.561 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Update CONFIGURATION 7/4 to 704643072
2020-03-05 15:09:27.563 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Commands processed 1.
2020-03-05 15:09:27.565 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6be648.
2020-03-05 15:09:27.567 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6be648.
2020-03-05 15:09:27.568 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: notifyTransactionResponse TID:6027 DONE
2020-03-05 15:09:27.570 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-03-05 15:09:27.572 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2020-03-05 15:09:27.573 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-03-05 15:09:27.574 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-03-05 15:09:27.575 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2 
2020-03-05 15:09:27.555 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 82: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT 2020-03-05 15:09:27.557 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 82: Node configuration report, parameter = 7, value = 704643072, size = 4 2020-03-05 15:09:27.558 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent 2020-03-05 15:09:27.560 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CONFIGURATION, value=org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@f1dd3f 2020-03-05 15:09:27.561 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Update CONFIGURATION 7/4 to 704643072

This looks strange. You send a 15 for parameter 7, and then when the binding queries the value of parameter 7, it gets 704643072. Huh?

3

I noticed that as well, but it’s a bit over my expertise, and I want sure if there was a good reason for that. But it certainly explains why it’s not having the expected result.

4

I looked around for a spec that describes the config parameters - no luck so far. The user manual is pretty useless. Do you have any other docs on this device?

5

What I find a little curious is that the database entry defines a 4-byte value to represent a setting whose allowed range is 0-30.

6

Agreed. That appears to have come from the zwave alliance which should have come direct from the manufacturer. There are other suspect parameters like that too.

https://products.z-wavealliance.org/products/1161/configs

7

So the binding is sending 00 00 00 0F which is correct for 15. But the response to the GET is 2A 00 00 00, which looks whacky. But that’s definitely where the 704643072 is coming from.

8

Thanks guys for helping me track this down. So are you thinking maybe that the byte size in the binding (zwave alliance) is wrong? What can I do from here? Should I request something specific from the manufacturer? Can I test different values somehow? Thanks!

9

It’s hard to say whether the byte size is correct or not. I just thought it was odd that they were using a 4-byte field to represent a 1-byte value.

I would suggest you email the manufacturer. I would explain that you’re using the zwave binding in openHAB, and that you’re having trouble setting the values for config parameters 5 and 7. You could also include your debug log, as well as this screen snip showing the behavior you’re seeing.

log-viewer-node82
log-viewer-node82934×323 66.3 KB

10

Also include the firmware version of the device, which you can find in the Attributes panel in HABmin.

11

Looking at this log, the word size is correct at 4 bytes.

12

Try contacting the manufacturer’s support? If you are lucky you can get a definitive answer. Otherwise there may be some “Engineering Specs” or similar on their support site listing the configuration parameters.

13

What do you make of the response (704643072 ) to the CONFIGURATION GET when it was just set to 15?

1 Like
14

The SET was presumably rejected. I see the log viewer is incorrectly displaying the value, but either way, it’s not 15.

I would suggest to contact the manufacturer to see what they say in case the definition is completely wrong. The size I’m sure is correct as that is reported in the log here, but maybe the range is wrong (well - certainly the range is wrong!) since the value that is read back is outside of the allowable range.

1 Like
15

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.