Adding Associations not possible since 2.3.0

[joergs-git]

Since my Update to 2.3.0. it's not possible to create new Basic Associations anymore.
I tried it with several battery devices (e.g. Coolcam Door/Window sensor) and woke up the devices a dozen times without any effect. The selected association device simply disappears again.

So I also tried it with mains powered devices (so to avoid any wake-up issues) and the effect is the same.
Any idea how to solve this?

[joergs-git]

Quickly did another little test:
Setting associations doesnt work with Expert 1.2.0 so I downloaded and tried it with the previous version 1.1.0 where it works fine.

[devTechi]

Yes. I've got that problem too.

But I don't want to do a rollback if it isn't really necessary.

[joergs-git]

You don't need to do a full rollback. You can simply branch the old Expert-Part to get it this way working again.... as a temporary solution.

[devTechi]

Right. I know. I'll give it a try and download the 1.1.0 release and replace the ui under /opt/z-way-server/htdocs/epxert

Thanks @klaasjoerg

[devTechi]

So I did the downgrade but cannot test it, because I'm not physically around my devices. Will test it later.
Right now the behaviour is the same. The new association came up for a few seconds and gets deleted after that. But without waking up the device no association can be set.

Will report here later.

[devTechi]

It worked 👍

Just had to wait for the device to wakeup. So with v1.1.0 it is working again.

[aivs]

At first, see description, interface of associations should works according this description:
ORANGE - Selected in UI but not active in device yet
GRAY - Active in device but not selected in UI
BLUE -Selected in UI and active in device

Problems:

1. All devices that added into association group become GRAY, should be BLUE.
2. All associations has exclamation mark, what this mean?
3. After adding new device into association group, it instantly disappears. Then I wake up device and device appears into association group.

In fact, Association work, but ui works not correctly.

See GIF (7mb, wait loading)

[vades]

This happens because:

1. Info about associations are (should be) stored in the /config/Configuration.xml
2. If this file is missing assoc are not stored in configuration but only in the device:
3. If /config/Configuration.xml is present on your BOX then UI sends correct request. API response is: 200 OK but Configuration.xml is not updated and is empty.
   Because of this the ASSOC does not work correctly.
   This have to be fixed in the backend API

[aivs]

I see the requests to Configuration.xml, but it empty.

[vades]

This have to be fixed in the back-end API. Serguei?

[ronie-z-wave]

Please see also:
Z-Wave-Me/home-automation#423
#225

It is not working - maybe it's something that relies on webserver?

[PoltoS]

I confirm that the problem with POST of Configuration.xml is present. We try to nderstand from which version this started to find the porblem.

[aivs]

In 2.3.2 can't add Z-Way to associations

Want to add

After 1 second Z-Way disappeared

[vades]

Because of #225
See my comment:
This happens because..........

[Kosta-Github]

any news on this? I would really like to set/tweak some parameters of my devices...

[michaelhq]

same her with 2.3.6, any workaround or progress on this bug?

[zwave-mke]

tested on 2.3.7 and is working

[PoltoS]

Associations do not work if there is an unknown node in the group. For example explicitly add node 232 to a group.

In our old blue UI we were showing it as strikedout to emphasize that it is not in the network.

Please fix that as the full UI stops working with an unknown node in the list