Zwave 2.5.x Association Groups

devices will not save the Association Groups (Controller) in Paper UI. I can set it and save. then i go back to this setting and it is empty

2020-01-05 16:10:21.029 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update received
2020-01-05 16:10:21.048 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored binding_cmdrepollperiod to 1500 (BigDecimal)
2020-01-05 16:10:21.049 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored group_4 to null (null)
2020-01-05 16:10:21.049 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored action_failed to false (Boolean)
2020-01-05 16:10:21.051 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored wakeup_interval to 43200.0 (BigDecimal)
2020-01-05 16:10:21.052 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored action_remove to false (Boolean)
2020-01-05 16:10:21.052 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update set group_1 to [controller] (ArrayList)
2020-01-05 16:10:21.054 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Association 1 consolidated to [controller]
2020-01-05 16:10:21.062 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Unknown association group 1
2020-01-05 16:10:21.063 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored binding_pollperiod to 3600 (BigDecimal)
2020-01-05 16:10:21.063 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored group_3 to null (null)
2020-01-05 16:10:21.064 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored group_2 to null (null)
2020-01-05 16:10:21.064 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored action_heal to false (Boolean)
2020-01-05 16:10:21.064 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored config_1_2 to 0 (BigDecimal)
2020-01-05 16:10:21.065 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored config_2_1 to 255 (BigDecimal)
2020-01-05 16:10:21.065 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored wakeup_node to 0.0 (BigDecimal)
2020-01-05 16:10:21.066 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 14: Configuration update ignored node_id to 14 (BigDecimal)

OpenHAB, any any Z-Wave controller only uses the Lifeline group.
Any other association groups allowed my the manufacturer are for controlling devices peer to peer without a controller present. The manufacturer usually documents how to use those other groups. For known group information,
I know we usually define them in the zwave database but, I believe that is just for user documentation convenience.

There are known issues displaying associations in PaperUI.

What sort of devices are you configuring? Are they battery devices? Are you waking the devices up after setting the configuration to allow it to configure the device? Is the device fully initialised even (which might explain the unknown group error).

Please try to provide as much information about your system, configuration and problem as possible to allow us to help.

1 Like

I leave you in much more expert hands.

i have this problem with “NAS-DS01Z Door/Window Sensor”
my “MT02650 Devolo Thermostat” works without problems.

The Sensor doesn work since update from 2.4 - before all was fine

Is the device initialised completely? If not, then you could have this issue as mentioned earlier.

Are you waking up the device? If not, configuration will not be transferred to the device.

Please provide a detailed debug log showing the startup of the binding for 5 or 10 minutes at least afterwards, and please wake up one of the devices a few times in this time. This might allow me to answer some of the above questions.

2 Likes

hi Chris,
after remove everything and start at zero. now it works. i thing one of the problems was the multible pushing of connect buttons.
now it work everything like before.

Thanks for yout help and a goog sunday evening

2 Likes