Settings updates not accepted

I’ve tried to change settings for 4 different devices. An Aeotec NanoMote Quad (group association), an Aeotec Trisensor(motion reset timeout), a Dome motion sensor(motion reset timeout) and a Fibaro Sensor(motion reset timeout). For each device, in both cabman and paper, the settings revert to their previous values. I put the zwave binding in debug mode and I see this in the logs for each device:

 Configuration update ignored node_id to 'x' (BigDecimal)

Where ‘x’ refers to each device’s node id. I’m running version openHAB 2.5.7 Build #175 on an Rpi4.
I’ve been able to change settings on these devices before, so I’m not sure what’s happening here. There are some posts here on this issue, and for some, the solution was to use an updated version of the binding. But given I’ve been able to change settings before, I’m not sure this is a viable solution.
Any ideas?
Thanks

  1. You need to wake battery operated devices after the changes.
  2. You can’t edit the parameters for manual configured zwave things in files.

Thanks, I tried waking, but the settings still reverted to their original settings and none of the Things are manually configured. Habmin, I woke the device, then clicked “Save”. I closed the Association Group, then opened it again, and the Association Groups were gone. I even tried disabling the controller (Aeotec), stopped the service, cleaned the cache and restarted the service a couple of times. New settings still not retained.

What about the other way around? Change the setting, then wake the device. You may have to wake it multiple times.
If nothing helps restart openHAB.
If that does not help soft reset your controller: power down the server, remove the controller physically, reattach the controller, power up your server.

Soft resetting and rebooting did not work. Settings are not retained. Now in PaperUI, after changing the settings, I click the check to save. Then I wake the device. In the log, I still the “ignored” message. In Habmin, after changing the setting, I click the Save button and then wake the device. Same error in the log file. In either case, when I look at the setting again, the new value is not retained. I’ve done this any number of times over the last three years since I’ve been using OH and even if a device is not awakened, any new value is always retained. I get the same error in the log, even when changing a setting in a mains powered device:

NODE 58: Configuration update ignored

As you already tried HABmin I am out of ideas, sorry:

The “configuration ignored” message means it received a configuration update, but it is ignored as the value is the same as already set in the device. If that is wrong, as the value was changed outside of the binding for example, then you’ll need to change it to another value, and then back to the new value.

While HABmin only sends updates for parameters that the user changed, all other UIs send all configuration parameters. This can cause a lot of traffic for devices that have a lot of configuration. Since I couldn’t convince people to change the UIs, I had to add this to the ZWave binding to try and reduce traffic.

1 Like

Thanks for the reply. What I did this morning was to exclude/include the device and then change the settings. After saving and waking the device (Aeotec NanoMote Quad), I checked the settings and they were again blank.
Here is the debug output:

2020-09-06 08:53:20.760 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Polling initialised at 1800 seconds - start in 1405800 milliseconds.
2020-09-06 08:53:20.760 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Device initialisation complete.
2020-09-06 08:54:49.349 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update received
2020-09-06 08:54:49.358 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored config_32_1 to 20 (BigDecimal)
2020-09-06 08:54:49.364 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set binding_cmdrepollperiod to 1500 (BigDecimal)
2020-09-06 08:54:49.372 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored config_43_1 to 0 (BigDecimal)
2020-09-06 08:54:49.374 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored group_9 to null (null)
2020-09-06 08:54:49.386 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Handler disposed. Unregistering listener.
2020-09-06 08:54:49.387 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored group_8 to null (null)
2020-09-06 08:54:49.389 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored group_5 to null (null)
2020-09-06 08:54:49.402 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set group_4 to [node_121, node_58] (ArrayList)
2020-09-06 08:54:49.410 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Association 4 consolidated to [node_121, node_58]
2020-09-06 08:54:49.412 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Unknown association group 4
2020-09-06 08:54:49.414 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored group_7 to null (null)
2020-09-06 08:54:49.416 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set action_failed to false (Boolean)
2020-09-06 08:54:49.421 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored wakeup_interval to 0 (BigDecimal)
2020-09-06 08:54:49.423 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set group_6 to [node_14] (ArrayList)
2020-09-06 08:54:49.427 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Association 6 consolidated to [node_14]
2020-09-06 08:54:49.428 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Unknown association group 6
2020-09-06 08:54:49.430 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored group_1 to null (null)
2020-09-06 08:54:49.432 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set action_remove to false (Boolean)
2020-09-06 08:54:49.434 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored group_3 to null (null)
2020-09-06 08:54:49.436 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set binding_pollperiod to 86400 (BigDecimal)
2020-09-06 08:54:49.437 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Polling initialised at 86400 seconds - start in 31795200 milliseconds.
2020-09-06 08:54:49.439 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set group_2 to [node_121, node_14, node_58] (ArrayList)
2020-09-06 08:54:49.449 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Association 2 consolidated to [node_121, node_14, node_58]
2020-09-06 08:54:49.451 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Unknown association group 2
2020-09-06 08:54:49.453 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set action_heal to false (Boolean)
2020-09-06 08:54:49.455 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update set wakeup_node to null (null)
2020-09-06 08:54:49.462 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 158: Serialise aborted as static stages not complete
2020-09-06 08:54:49.467 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Controller status changed to ONLINE.
2020-09-06 08:54:49.469 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Controller is ONLINE. Starting device initialisation.
2020-09-06 08:54:49.460 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Error converting wakeup value null
2020-09-06 08:54:49.472 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Updating node properties.
2020-09-06 08:54:49.473 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Updating node properties. MAN=881
2020-09-06 08:54:49.475 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Updating node properties. MAN=881. SET. Was 881
2020-09-06 08:54:49.476 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Properties synchronised
2020-09-06 08:54:49.472 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Configuration update ignored node_id to 158 (BigDecimal)
2020-09-06 08:54:49.663 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising Thing Node...
2020-09-06 08:54:49.664 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising cmd channel zwave:device:f21cd9de:node158:switch_dimmer for OnOffType
2020-09-06 08:54:49.666 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising cmd channel zwave:device:f21cd9de:node158:switch_dimmer for PercentType
2020-09-06 08:54:49.668 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising state channel zwave:device:f21cd9de:node158:switch_dimmer for PercentType
2020-09-06 08:54:49.670 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising state channel zwave:device:f21cd9de:node158:switch_dimmer for PercentType
2020-09-06 08:54:49.671 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising cmd channel zwave:device:f21cd9de:node158:scene_number for DecimalType
2020-09-06 08:54:49.673 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising state channel zwave:device:f21cd9de:node158:scene_number for DecimalType
2020-09-06 08:54:49.674 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising cmd channel zwave:device:f21cd9de:node158:battery-level for PercentType
2020-09-06 08:54:49.676 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Initialising state channel zwave:device:f21cd9de:node158:battery-level for PercentType
2020-09-06 08:54:49.678 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Polling initialised at 86400 seconds - start in 25401600 milliseconds.
2020-09-06 08:54:49.679 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Device initialisation complete.
2020-09-06 08:56:38.882 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Channel zwave:device:f21cd9de:node158:scene_number linked - polling started.
2020-09-06 08:56:45.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Channel zwave:device:f21cd9de:node158:battery-level linked - polling started.
2020-09-06 08:56:48.948 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 158: Channel zwave:device:f21cd9de:node158:switch_dimmer linked - polling started.

What are you trying to change - the associations? Or is it something else? Most of the other configs are ignored as they haven’t changed - as I said earlier, but I really don’t know what you are doing.

This also might just be an issue with the UI. It’s hard to tell from such a short log what is happening, and also understanding what you are trying to change.

I’m trying to change group associations. I’ve been working from habmin.

So as far as I’ve seen, the association updates are not being ignored. I guess also that the initial report you made above is not related to associations as it mentioned BigDecimal.

Are the associations being ignored? From what I see in the log, that’s not the case?

As I said, it could well be a problem with the UI - there is a known issue displaying multiple selections.

No, the associations are not being ignored. I see the in the logs now. But what does “Unknown association group” mean? I see that in the log.

@chris There is no xml file in /car/lib/openhab2/zwave. The same for another device that 'm having trouble changing its motion reset timeout, a Dome motion sensor. Both devices appea to be completely enumerated as I see the same settings as my other two NanoMote Quads, of the same type. The Dome in question displays the same settings as the problematic one. If the xml is required for changing settings and for group associations to work, then that’s probably the issue. I even cleaned the cache and restarted the service a couple of times along with excluding/including the quad a few times. I see there are lot of posts here about missing zwave xml files. I’ll go through some of those and see if I can find a solution.

I finally got things working. It took a few more exclusions/inclusions and multiple wakings for the two devices. One thing I hadn’t noticed was that when you change a setting in Habmin, there is “pending” just above the changed setting. That wasn’t there while I was having issue. But after my third cycle of exclude/include, it started to appear, and the devices are working as expected now.

This simply means that the discovery is not complete - the XML will be generated by the binding when the binding has discovered the devices features.

Maybe the device was not fully discovered then. If the binding doesn’t know that the device supported WAKEUP class, then it would try to send immediately and you would not have seen the PENDING flag.

Ok, got it. Thanks.