@sburke781 , here is the screenshot under the device:
I should also mention that my hardware is Fibaro RGBW but I'm using Zooz RGBW Dimmer driver as I had a lot of issues with Fibaro drivers.
The effect numbers that work for me are 1 to 5.
I suspect you won't be able to call the setEffect directly from within Room Lighting. If I'm correct, the best I can suggest is to:
Create a Virtual Button with 5 buttons
Setup an instance of Button Controller that runs the setEffect command when any of the 5 buttons are pressed, passing in the equivalent effect number that corresponds to the button number
Add the Virtual Button to the Room Lighting setup to press the appropriate button
Thank you. It worked like a charm but it's easier to do it with Rule Machine, considering all the things that I had to do. But this solution is probably more flexible for future expansion or modification.
I was answering a question about bulbs that use the Wiz driver, which don't work the same as the Zooz driver. Glad you figured it out. I use button pushes in lots of my Room Lighting instances.
Would it be possible, and would it make sense, to be able to use the same switch used to determine that all the lights are off, when determining if the lights are on? So in my example below, instead of "Indicator for Group Any On", I could use the same Living Room CH Group switch used in the Other Turning Off Options.
I'm not following what you are asking. The indicator is the Activation Device. Its driver has special commands that affect its displayed state without commanding the app. So it has two functions, one to command the app (the Activation device) and another to display group state (indicator any on, all on, scene set).
Using any of the indicator options causes the individual light states to determine the indicated state. That is effectuated with the special commands. Another aspect of the Activator device is that even if it indicates 'on', it will still treat an on command as an activation command -- the overloading of its state for indication purposes does not effect it's use as an activation device.
This functionality of indicator status was done to mimic the same behavior of a Lutron keypad button, where its LED may indicate group/scene state, while the button itself still commands the programmed lights.
If I turn the group / room off in the Hue App on my phone, the status of the scene device in HE does not change, but the Coco-Hue group device for that room does.
I was hoping to use the group device from Coco-Hue as the indicator for the RL setup being "active", like I am in detecting the off state, but based on your description of how the activation works in RL and the fact (I believe) I have tested that issuing an on command to the scene device in HE while it is on, does not turn on the scene on the Hue bridge, I don't expect my request would have made a difference.
I have setup a rule to keep the scene devices in HE in sync with the group device when it turns off, which is, I believe the solution to my issue.
I do a very similar thing in use Hue scenes in Room Lighting, though, I’ve got a few differences that might help. I activate my scenes as buttons but it could work as a switch too. The key is to have your scene switch automatically turn off in its device preferences. This means that any time I send an on command to the Room Lighting activator, it will always turn on the scene.
The other key thing I do is that I have a switch binding pairing of the activator device and the Hue group. This way if I turn on the group from the Hue app, it will activate the Room Lighting instance and set the scene correctly.
Thanks for those, I'll have to give them a go. Perhaps I'll keep what I setup this morning for now, but I am interested to give number 2 a go. When you say:
[RELEASE] Switch Bindings is what I use to bind the Room Lighting activator and the Hue group. It would be similar to using the built in Mirror Me app.
Hmm... It is a good idea, but unfortunately I do also set the scenes outside of RL / HE... I'll move any discussion of this outside of this topic if I explore it in more detail, not strictly just an RL topic.
Those buttons simulate being triggered on or off. If you want the automation to pause you would use the PAUSE button at the top of the main page of the app. The app showing it's active doesn't mean the devices are on or off, it just shows that it's running.
I'm using this app to control a set of shades and I also created a "Room Lights Activator Shade" device. Everything seems to work fine, except that open and close commands are reversed (i.e. the shades close when I hit open and the other way around). Is there an easy way to fix this (without creating another virtual device and rules to control the activator device) ?