Correct device not available for association
Hello everybody,
I'm trying to associate a Zipato door/window sensor to a Fibaro single switch 2 (FGS213) to automatically turn on the light when I open the door.
I select device manager --> Zipato door/window sensor --> Settings --> Advanced --> Manage associations
In the first column, the only device available for association is the first level of the Fibaro group (Fibaro FGS213 Switch 2), but the automation does not work this way. The device that switches the light on, and that I should choose in the associations page, is the child of the first level (Switch corridoio).
Also in my rules it work this way. "Switch corridoio" is the sensor to be used to turn on lights.
Is there anyway to associate the right device (Switch corridoio), or maybe to "tell" to the first level (Fibaro FGS213 Switch 2) to switch the light on?
I know that I can easily achieve this throug a rule, but I think associations should be better in this case.
The same problem 
Have the same problem.
In my case I wish to associate MasterDevice.Group2 with SlaveDevice.Group2 but can only choose SlaveDevice.
Have the same problem.
In my case I wish to associate MasterDevice.Group2 with SlaveDevice.Group2 but can only choose SlaveDevice.
Have you actually tried to complete the assotiation by dragging the fibaro switch to the middle (whilst selected group 2) and the hit send? Then hit retrieve, does the fibaro come up? On your printscreen the middle part of the window is empty.
Did to actually try to complete the assotiation and then test if it works?
Different devices have different systems and firmwares an it might be the case that fibaro is always meant to appear in this assitiations manager the way it does.
Have you actually tried to complete the assotiation by dragging the fibaro switch to the middle (whilst selected group 2) and the hit send? Then hit retrieve, does the fibaro come up? On your printscreen the middle part of the window is empty.
Did to actually try to complete the assotiation and then test if it works?
Different devices have different systems and firmwares an it might be the case that fibaro is always meant to appear in this assitiations manager the way it does.
So you say that it is possbile to associate to a SlaveDevice.Group2,3,n on some devices?
So you say that it is possbile to associate to a SlaveDevice.Group2,3,n on some devices?
Different devices allow different amount of binded devices on a group. Usually the 1st group is used for.the controller and it supports only one device. The other groups are used for basic tasks (onoff in this case). Hence.why there is group 2 (on off). Give it a try
Different devices allow different amount of binded devices on a group. Usually the 1st group is used for.the controller and it supports only one device. The other groups are used for basic tasks (onoff in this case). Hence.why there is group 2 (on off). Give it a try
Attila, my problem is that I can't choose the right device in the first column.
The 1st level comes up in 1st column (fibaro fgs 213 switch 2 in my printscreen), but I should choose its child (switch corridoio in my printscreen).
Attila, my problem is that I can't choose the right device in the first column.
The 1st level comes up in 1st column (fibaro fgs 213 switch 2 in my printscreen), but I should choose its child (switch corridoio in my printscreen).
Greetings,
The association manager does not support multi channel association at the moment. That's why you can't select individual endpoints.
Greetings,
The association manager does not support multi channel association at the moment. That's why you can't select individual endpoints.
Replies have been locked on this page!