Zwave Configuration Updates Ignored

Hardware Home Automation
1

Hi All: I purchased the ADC-T 2000 (alarm.com) thermostat, and i’m trying to calibrate the temperature ,as it’s currently off almost 3 degrees, and many of the other parameters. However, setting are not being accepted. For example, values that I enter into the calibrate temperature parameter (parameter 5) do not take effect. I’ve noted the below debug log entries. Anybody have any thoughts or guidance? Thanks a million!

(The device currently responds to all other commands and is otherwise functional)

2020-03-03 23:04:31.322 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update received

2020-03-03 23:04:31.330 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_30_1 to 0 (BigDecimal)

2020-03-03 23:04:31.334 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored binding_cmdrepollperiod to 1500 (BigDecimal)

2020-03-03 23:04:31.338 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_11_1 to 0 (BigDecimal)

2020-03-03 23:04:31.342 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored group_1 to [controller] (ArrayList)

2020-03-03 23:04:31.346 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored action_reinit to false (Boolean)

2020-03-03 23:04:31.350 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_17_4 to 950 (BigDecimal)

2020-03-03 23:04:31.354 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_18_4 to 500 (BigDecimal)

2020-03-03 23:04:31.358 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_10_4 to 350 (BigDecimal)

2020-03-03 23:04:31.362 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_15_4 to 950 (BigDecimal)

2020-03-03 23:04:31.365 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_12_1 to 20 (BigDecimal)

2020-03-03 23:04:31.369 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_16_4 to 350 (BigDecimal)

2020-03-03 23:04:31.373 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_19_1 to 0 (BigDecimal)

2020-03-03 23:04:31.377 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_31_4 to 30 (BigDecimal)

2020-03-03 23:04:31.381 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_34_1 to 1 (BigDecimal)

2020-03-03 23:04:31.385 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_13_1 to 25 (BigDecimal)

2020-03-03 23:04:31.389 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_32_4 to 30 (BigDecimal)

2020-03-03 23:04:31.393 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_35_1 to 0 (BigDecimal)

2020-03-03 23:04:31.397 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_33_4 to 10 (BigDecimal)

2020-03-03 23:04:31.401 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_14_2 to 120 (BigDecimal)

2020-03-03 23:04:31.405 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_20_1 to 5 (BigDecimal)

2020-03-03 23:04:31.409 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_21_1 to 10 (BigDecimal)

2020-03-03 23:04:31.412 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_22_1 to 25 (BigDecimal)

2020-03-03 23:04:31.416 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored action_failed to false (Boolean)

2020-03-03 23:04:31.420 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored action_remove to false (Boolean)

2020-03-03 23:04:31.424 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored binding_pollperiod to 86400 (BigDecimal)

2020-03-03 23:04:31.428 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored action_heal to false (Boolean)

2020-03-03 23:04:31.432 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_1_1 to 0 (BigDecimal)

2020-03-03 23:04:31.435 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_2_1 to 1 (BigDecimal)

2020-03-03 23:04:31.439 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update ignored config_27_1 to 30 (BigDecimal)

2020-03-03 23:04:31.443 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update set config_5_4 to -15 (BigDecimal)

2020-03-03 23:04:31.447 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 82: Creating new message for application command CONFIGURATION_SET
2

Hmm. Not completely sure what’s going on.

I think the binding generates this message when it thinks the configuration parameter has not changed. I’m wondering if you’re using PaperUI to make the configuration changes. I ask this because when a config parameter is changed, PaperUI sends all configuration parameters to the binding, not just the one that was changed.

If you’re using Paper UI, can you try using HABmin to make the config changes. At least that will eliminate one potential reason for all the “ignored” messages.

In these last two log lines, it does appears that the binding is setting config parameter 5 to -15.

2020-03-03 23:04:31.443 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Configuration update set config_5_4 to -15 (BigDecimal)
2020-03-03 23:04:31.447 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 82: Creating new message for application command CONFIGURATION_SET
3

So that was a great point - Thanks @mhilbush . I applied the setting in habmin, and the ignores did not appear. However, that leads me to my next question: The config setting that was properly applied in this case happens to be the temperature calibration value (in tenths of a degree) I was attempting to change in the first place.

As in my example above and when applied via habmin, the temperature on the unit does not change, as it does with other thermostats. I can put “40” in there as the value, and the temperature on the unit does not increase at all. Does anyone have experience with this?

4

This seems to have forked into a device specific question. As such, i’ll start a new thread. Thanks!