Associations and Group

[pelle 0]

Hi.

 

I'm trying to do some simple things using associations. But I'm not able to get it working the way I want.

 

Three relay switches are involved, one Double Switch and two Single Switches.

 

I managed to associate the first switch in the double-unit with the first single switch. Works as I expected. First button on the Double Switch will now also affect the first Single Switch.

 

Next I wanted to associate the second Single Switch with the second switch in the double-unit. Results are confusing. In 4.040 the settings would simply just not be saved. Now after upgrade to 4.042 the UI is behaving strange. I navigate to second Single-Switch and press the "Set Up" button for a Group-ID. I tick the unit that represent the second switch in the double-unit and then the UI will automatically tick the unit which represent the first switch in the double-unit as well. 

 

Is it not possible to make individual associations for the different buttons on a Double Switch? Or is this simply a bug?

 

Also, most of my units have Group Id associated with "1". But a few have three Group Id's associated with "1". Why does it differ? Which is correct?

 

Appreciate any clarifications.

 

 

[j.nowacki 5]

You can not associate anything with the slave device yet, since this functionality is not supported by HC so far, only 1st Relay can be controlled that way.

Associations to node ID '1' are for reporting device state to the controller. Usually only one group needs to be assigned to 1 (check the manual to determine which one), but if there are any issues with incorrect state in interface you can set all three like that.

[pelle 0]

Thanks for clarifying.

 

I was reading a little on the subject in the Advanced User's Guide - Section 3.3.4:

Please login or register to see this link.

 

So, this is not a limitation in z-wave protocol or the Double Relay device itself? Should I place a feature request in the bug tracker, or is it already on the backlog?

 

The ID 1 settings make sense. Thanks!

[j.nowacki 5]

It is related to controller rather than module.