I have a room lighting app setup as follows:
All the switches and levels are set as expected, but my activator device "Living Room Lights" is OFF, not ON as expected since everything is set as per the scene.
Any idea why?
The activator device is just another way to turn on this room lighting instance. In some ways it is equivalent to your buttons. For this Room Lighting, it activates when either button 1 is pushed or the activator device is turned on.
The activator device does not turn on when Room Lighting turns on; however, room lighting will turn on when the activator device turns on.
Does this make sense?
1 Like
That makes sense when room lighting is NOT being used as an indicator. But based on the description of "Indicator on Scene Set", if my lights were turned on with the activator (via Alexa) the activator should remain ON unless one of the lights is turned off or level doesn't match. This feature doesn't seem to be working for me since the switch always turns OFF automatically after a few seconds, despite no changes to listed devices.
Is the Living Room Overhead on when you activate the scene? Do you see this same behavior if the Overhead is already off when you activate the scene? You might need to post the logs to show the exact timing, but I wonder if there is a timing issue with that light.
One thing you could try is to uncheck the ACT box for the Overhead and see if you get the same issue.
It seems to happen reproducibly, not only in my living room but in other rooms as well. I turn everything off, turn on the activator switch, and then after a few seconds it will turn back off.
Everything is still set according to the the activation settings
I suspect what you need to look at is this option under the Activation section:
To get here, click on Means to Activate:
Activate Lights Options:
Ideally I'd like to this to behave as a scene. If the lights are set based on the table, switch is ON and I can turn OFF. If not, switch is OFF and I can turn it ON to get everything to table settings. The issue is that even when everything is set to the table settings, the switch is OFF and I can't turn the lights OFF, they also don't change when changing through modes.
Edit: the behavior persists even with "Group: Indicator if any are on", logs from activator device:
logs from online device supposed to be on:
activation table:
Then I suspect you want this option, "All Set Per Table...."
Using "If Any are On" and it not working is odd...
"If any are on" works
But based on the docs, it seems to me that the app isn't working as expected for "only if some are on" and "all set per table"...but I can't seem to find anyone else with similar behavior.
Then it must be you... 
(joking)
It is odd.... It might be worth:
- Posting a full screenshot(s) of the RL setup
- Turning on debug logging for the RL App
- Posting screenshots for the RL App
What type of device driver is your room lighting activator switch using? Because all of your table are lights, it might be set to a bulb or dimmer. Trying changing the device type to switch so that on/off are the only commands that the activator can receive.
2 Likes
The activator device should be able to use whatever driver the app automatically assigns, @user3636 shouldn't need to change the driver for a built-in device generated from a built-in app...
That sounds little more grandiose that it needed to be...
It was originally using the "Room Lights Dimmer Activator" but same behavior with "Room Lights Switch Activator".
It seems its something with the groupState variable, it is never set to allOn always someOn or allOff
1 Like
Realy, there is a difference...?
Yes. The activator device will send all settings if it is a bulb or dimmer. This can have unexpected results. If a person wants just on/off commands for the table, I have found that setting the device to a switch significantly helps. It eliminates the possibility of setLevel and setColor commands that might inadvertently change the setting.
2 Likes
Wow.... I feel a feature request coming on.... but in the meantime, a good suggestion @user3636 by @JB10 ....
It's likely a mixture of driver and/or your setting I mentioned earlier....
Thanks, @JB10 is likely on the right track... as much as the info I asked for is important, that is likely the path to pursue....
