I’m seeing exactly the same behavior that you describe below in my Cooper devices. I have decided to swap out the scene controllers with Leviton ones instead. Hopefully that addresses those particular issues (Turning on the scene light when executed from a different controller or phone. And being able to run code during scene deactivation.).
Have you come up with any solutions for the other issues? I called Cooper support a couple weeks ago, only got voicemail. No one has returned my call.
The fact that some of the led lights stop working is very troubling. The only solution is it to a hard-reset of the switch.
The accessory getting out of sync is driving my family crazy. Any thoughts on that one?
[quote=“maverickmt, post:11, topic:174307”]Well for what it is worth I have all sorts of problems with the cooper switches…
I have probably 50 of them between the ELV dimmers, and dimming accessories and the relay switches and accessory (all of mine require wireless accessory.) As well as several scene controllers.
Scene Controllers:
I am unable to update the status light remotely (if I execute a scene on my phone, the controller does not know it is executed and in turn the status light is not lit, therefore it will think a scene is not activated that is.)
The scene controller does not fire a trigger event to vera when a scene is de-activated (I want to run luup code… and can’t)
Dimmers (All of mine are the 600W ELV for LED’s):
Some of my switches will turn off their internal status led’s for no reason, and I will have to cut power to them to correct it… don’t know why…
Accessory Switches (All a wave based):
If I active a switch remotely the accessory switch loses awareness of the load, ie if I turn a light on via phone, the switch will be updated with the status of the load… the accessory switch will not (it will still think the light is off and have to be pressed twice to turn it off…)
Anyone else having these issues?[/quote]