This object is in archive! 

Associating buttons on scene controller with actions

Ron Gerrans shared this question 8 years ago
Need Answer

I'm still learning the Zipato and am trying to setup my Cooper 5 button scene controller. I added the scene controller to the network and the only way I see to associate actions to buttons is through the rule creator. I've tried both of the attached rules just to turn on a light and neither rules work. I've also noticed that most of the buttons only turn on temporarily, button 4 is the only one that keeps it's on/off state.


Any suggestions would be appreciated.

Replies (5)

photo
1

Example of how you could do. To make a light toggle. You can also just make a scene turn on.


2a3d3525ef8ce67b32172748e3ba778a

photo
1

Jacob - thanks for the suggestion.


Unfortunately this configuration doesn't work either with the Cooper scene controller. I suspect the issue is how they set it up in the base code. Most of the buttons won't stay on, the same way in my Vera they would act prior to being assigning a scene. On the Vera the setup language reports that it's creating associations when I assign it an initial scene, which makes me think you have to do an association vs. a rule.


When I look at the association manager for the root scene controller device it shows 5 groups, all with the Zipato controller. If I receive the groups from the scene controller it drops the Zipato Controller. If I try to send any configuration (blank, just the zipato, the device I want to control) I get an error that too many devices are associated with that group.


So not sure these devices are setting up right in Zipato.

photo
1

Usually Group 1 is reserved for the main controller and can only accept 1 association (controller). You should use the other groups. You can refresh the info in the association manager (pull the info from the device), then you know what should be associated already. Hope this helps.

photo
1

If i remember correctly there are several Cooper 5 scene controllers on the market, what exact model is yours?

photo
1

Attila - I've been able to associate multiple controllers in Group 1 on other switches. I know with Cooper devices they can take up to 5 associations total whether in a single group or in multiple groups. http://goo.gl/Ku1WH9 (page 4)

That said, I did try other Groups on this one and am having the same issue that when I pull information from the device it wipes all 5 groups and any time I try to send associations back to the scene controller it gives me the "too may device error -24" no matter if there are no or 1 associations present. Which seems somehow related to that limit of 5 from above.


Marko - Actually there is only 1 that I'm aware of, the RFWC5 - http://goo.gl/g0DyKv (though they have 2 different physical button configurations they are basically the same device).

photo
1

Ok, then we are talking about the same device. The problem with association groups has been fixed and is available in the latest beta release.

photo
1

Thanks. I'll download that tonight and test.

photo
1

Marko,


So I installed the newest beta firmware. If I go to the scene controller I now see the bindings for the button sub-devices and associations for the root. I've tried setting associations to the various groups (Attila was right that it will only take one device per group); I've tried setting the bindings (both native and non-native) and I've tried creating rules. None allow the buttons to control a device. In addition, button 4 is the only one that will even stay in on status (no matter if it's part of one of the tests or not). The rest just turn off as soon as you push them on.


Any suggestions on what I'm not doing right?

photo
1

Marko,


Just wanted to follow-up to see if you had any more guidance. Thanks.

photo
Leave a Comment
 
Attach a file