Room Lights: Scenes, Groups & Voice Assistants

Room Lights: Scenes, Groups & Voice Assistants

Room Lights can be used to create Groups and Scenes. Both Groups and Scenes involve the automation of a number of lighting devices intended to be Activated together. The differences between the two lie in how they are defined and how they are Activated. Both allow for Activation and control by Voice Assistants such as Amazon Echo and Google Home.

Scenes

In one sense every Room Lights automation defines a Scene, and possibly a number of Scenes if Modes or Alternate Means to Turn Off are used. Each Scene includes a number of lighting devices with specific settings for each to be established by Activation. A Scene is activated by one of the available Means to Activate available in Room Lights. The prior app Scene-1.2 was similar in that it too entailed a number of lighting devices, but had only a single means to activate -- the Activation Switch for the Scene-1.2. The Activation Switch was a virtual device child device created by the Scene-1.2 app.

It is possible to import a Scene-1.2 app into Room Lighting, creating an equivalent Room Lights app. This resulting app also has an Activation Device child device created for it, and established as the Means to Activate -- just like the original Scene-1.2. It's worth pointing out at this juncture that any switch could be an activator of a Room Lights Scene, along with a dozen other possible Means to Activate. When Activated, such a Scene sets each device to its predetermined setting. In order to use these Room Lights Scenes in other apps, it is only necessary to include its Activation Device in the other app, and cause it to Activate the Room Lights Scene (e.g. by turning on the Activation Device).

Groups

A Group is also comprised of a number of devices to be Activated together, and an Activation Device child device. The main difference between a Group and a Scene, is that for a Group the settings for the individual devices are not pre-determined as they are for a Scene. The settings upon Activation copy those of the Activation Device. Thus, when Activated by the Activation Device, each device in the Group is set the same way. Significantly, for Zigbee devices, this allows the use of Zigbee Group Commands, in which a single Zigbee command activates all of the Group Zigbee devices at the same instant. Groups do not have to only use Zigbee devices, they can use any type of device, and all will be activated to the settings of the Activation Device.

For a Group in Room Lights the Means to Activate is set to "Follow Activation Device". As it suggests, this form of Activation sets each device to the setting of the Activation Device. When a Group-2.1 is imported into Room Lighting, the Activation Device child device is created, and the Means to Activate set accordingly to "Follow Activation Device".

Groups as Building Blocks

One use of a Room Lights Group is to establish the collection of lighting devices that will be Activated together, along with their Activation Device. Then, by using the Activation Device in other apps, including other Room Lights apps, it is possible to achieve automations such as Per Mode use of a Group. In this use case, the Activation Device of the base building block Group is set to different settings depending on the Mode -- the Group devices follow along when Activated.

Hybrid Scenes and Groups

Because Room Lights allows multiple Means to Activate, it is possible to have a situation where in one instance, the devices Activated behave as a Group, when they are Activated by following the Activation Device -- and in another instance they behave as a Scene with pre-determined settings when Activated by some other Means to Activate.

Differences Between Room Lights and Group-2.1 / Scene-1.2

The primary differences between the prior Group-2.1 and Scene-1.2 apps and Room Lights with respect to Groups and Scenes are details concerning certain options. These include On/Off optimization, and metering.

On/Off Optimization

Room Lights incorporates On/Off optimization automatically. This means that Room Lights will not Activate the selected devices once they are already Activated, not Turn them Off if they are not Activated. There are means to overcome this provided. One is an option under Means to Activate Options that causes Activation even if Partially Activated. Another is a per device option to force a device to be Activated or Turned Off irrespective of its state. This is also an Option under Means to Activate Options called 'Allow devices on/off irrespective of reported state'. Selecting this option causes an addition column of checkboxes to be displayed in the Devices to Automate table. When checked, the device will be Activated or Turned Off irrespective of its state. This was the primary purpose of the On/Off Optimization option, for devices that don't reliably report their state.

Metering

Room Lights does not offer a Metering option because Release 2.3.2 incorporates new improvements to the Zigbee and Z-Wave stacks such that metering is not required for all devices to be commanded when many are commanded at the same time.

Voice Assistants

Whenever an Activation Device is created for Room Lights, whether it be from a Group, a Scene, or just from entering a name on the main page, that Activation Device can be added to Voice Assistant configurations. When added, the Voice Assistant can control the Room Lights automation. Just how that control happens, and what it means, depends on the specific Means to Activate in use for the Room Lights instance.

Groups

When "Follow Activation Device" is the Means to Activate, Room Lights acts as a Group. The Voice Assistant can set the Activation Device and doing so causes the Group to take on those settings. For example, if Room Lights has some RGB bulbs in a Group, and an Activation Device named "Bulbs", "Alexa, set Bulbs to Magenta" will set those bulbs' color accordingly.

Scenes

When the Activation Device is used as a switch in the Means to Activate, as it would for a Scene, The Voice Assistant can Activate the Room Lights automation when the switch is turned on. Likewise, it can Turn Off the Room Lights automation when the switch is turned off. Any other commands given to the Voice Assistant would have no effect. For example, if Room Lights is being used as a Scene, and its Activation Device is named "Kitchen", "Alexa, turn on Kitchen" will Activate that Scene.

Enhanced Control by Voice Assistant

It is possible to give the Voice Assistant more direct control over the Devices to Automate in the Room Lights automation, by listing devices on the Activate Lights Options page:

Any of the lighting devices in your system can be selected here, and doing so makes them available to the Voice Assistant for control. That control is exercised by commanding the Activation Device.

One example of this use is to allow the Voice Assistant to control dimmer levels (or colors, color temperatures) of lighting devices used in the Room Lights instance. When Activated, those dimmer level values were set depending on the Device to Automate table settings for each device. By listing those devices for which after Activation adjustment is desired in the device selector shown above, their settings can be changed using voice commands.

There is a further option related to this adjustment of dimmer levels by a Voice Assistant, found on the Turn Off Lights Options page:

With this setting, "Alexa, set Kitchen to 60" will adjust the lights selected for Voice Assistant control to 60, and then prevent motion inactive from turning this automation off. This Turning Off disablement will end when the automation is Turned Off by some other means, including, "Alexa, turn off Kitchen." In this example, the Activation Device is named "Kitchen".

When selected this option will prevent the Automation from being Turned Off by motion inactive after a dimmer level is adjusted, possibly limited to physical changes only. Changes made by a Voice Assistant are not "physical". This Prevent Off option is not limited to level changes caused by a Voice Assistant, and can be caused by other means that change the selected dimmer levels.

6 Likes

I am confused that scenes is deprecated in 2.3.3.121. I am in the process of migrating from SmartThings and had used scenes with something like modes in my Webcore motion routines and with Alexa. For each room, I had four scenes, bright, scene, dark and off. I am also using "vary light settings per mode". I understand the idea of using an activator device to trigger from Alexa.

If I understand correctly, I need to create five instances per room, one for each scene each with an activator virtual device then a fifth that uses the activator devices as scenes.

Using an activator device with modes enabled in the main RL instance would result in some strange behavior.

What is the relationship between "bright, scene, dark and off" and modes? I don't believe that webCoRE had any access to Scenes, other that via its activator. So what is different?

Webcore activated a specific scene at a specific time of day on active and inactive. Is using five room lights instances per room the way to go?

I don't want to tackle this until I resolve the null pointer. It sounds like I may need to remove room lights and reinstall.

How was this done? By turning on the switch activator device? If so, the same approach will work for Room Lights.

If you have a specific instance of Room Lights that is messed up, you should only remove that particular instance.

How do I delete an orphan scene activator that is a child of one of room lights instances? If I delete the text in the "Command with:" box, it fills in again. It advises against deleting the device directly. I uninstalled groups and scenes since it is deprecated.

Command with: [Office evening scene Activator]
(http://172.16.0.99/device/edit/37)

You can simply delete the Activator Device from its device page. After doing that, RL will prompt you to either create a new one, or clear out the Activate Device name.

With Release 2.3.3.121 I see Groups and Scenes are being deprecated. Per the recommendation, I'm migrating my Groups to Room Lighting. I was able to create new Room Lighting child apps from the existing Groups. A lot of my Groups child devices are being used in other apps (e.g., dashboards, Amazon Echo, etc.). I was hoping to swap a legacy Group device with a replacement Room Lighting activator device, but the swap apps option in hub settings doesn't list Groups nor Room Lighting devices. Thoughts on how to make this part of the migration less tedious?

There is no way. Child devices cannot be swapped. Only migrate if you want. Please note the remark in the release notes:

So this warning message does not apply:

Remove it from the app first or they may be damaged by the device removal.

I have created a virtual switch to enable triggering the app by Alexa.

Only if it is in use by other apps. Those should be cleaned up. But simply removing the child device from its parent is harmless.

There is no need to do this. You can simply use the app's Activator Device for Alexa. Depending on what sort of lights you are using, this is better. Only the Activator Device can do things like set level, set color, etc., when commanded by Alexa.

My attempt to use room lights scenes with room lights for motion like I was doing in ST was a failure. Also, with ST, I could activate any scene in any sequence using Alexa. How can I do this with RL?

The level of the activator device called from RL motion overrides the levels that I had set for the devices in my RL scene. If the activator device was set to 100%, all the devices in my "dark" scene were set to 100 %. I now have to set all the devices directly in my RL motion app. I could activate the same scenes from my Webcore motion routines.

The activator devices appear to be stateful as switches. If the activator device is already turned on, turning it on again via Alexa does not work. I have to turn it off first, then turn it back on. I have not been able to nail down exactly how/where this is happening. I want the behaviour to be like a button, but virtual buttons do not map over to Alexa.

The activator device for RL is stateless, it will send ON command to the app even if already on. It would help understand what's going on if you would post a screenshot of your RL setup that isn't working as you expect.



If the Activator for the scene is set to 100%, it overrides the levels set in the scene. The scenes do not always activate either.

To activate a scene, only turning ON the activator will do that. Once you start giving it other commands, such as setLevel, that will override the table settings.

Since the scene activator has the properties of a color dimmer, when I check the “Act” box in my motion instance of RL, it gets level and color attributes. The activator should be a button which is stateless. With Alexa, I can only get scenes to activate if I turn them off first.

Where it says CT, you can make a different selection. RL doesn't know anything about a device a priori. Presumably, Family Scene is the activator for some other RL instance, right?

I just noticed that a couple of the Room Lights Activator drivers lack the button capability. Will fix that. In the meantime, you can change the driver to Room Lights Activator, and that will give you the button capability.

1 Like

The type of the activator was a key point I was missing. Why is a button type not available? Should button or switch not be the default for an automation? If I am to understand correctly, when the type is dimmer, RGB or CT, it behaves like a group, overriding all the scene device parameters.
Screen Shot 2022-10-05 at 8.49.08 AM

When the activator is created, before being used, it has all the attributes of a color bulb.