Thanks for clarifying.
Should I also migrate my Simple Automation Rules to Room Lighting to simplify things and have most rules in one place or is it still recommended to try to use Simple Automation if possible for better performance.
It doesn't matter. None of these apps have performance issues, so it's really a matter of personal preference.
I must admit I'm struggling with room lighting.
This is my scenario.
I have a physical switch to turn the lights on. In the room I have a Zigbee PIR to detect movement.
When the lights go on I want to start a timer to tun them off, but if movement is detected I want to extend the timer.
This is my turn off rule:
Any ideas from that what is happening? It seems to ignore the PIR and just turn off after 15 mins, even if movement is detected.
Thanks in advance.
Paul
You should post the whole rule screen shot and the log when it turns off. Looks ok, otherwise.
OK, so I changed both the timers to be 5 mins for the test, and am confused. Neither of the triggers seem correct.
You can ignore the error, thats a problem with the driver for the Candeo dimmer, already identified, and scheduled for fixing.
I think your problem is your activation event. You only have one activation event and that is the dimmer turning on. Motion is not an activation event. So when the dimmer activates it turns off in 5 mins. The motion is activated during that time but since it is not a activation event it does not restart the last event activation timer.
I think if you just add motion as an activation event it will work as you expect. Since you do not have the Act radio button on for device control, motion will not turn on the light but it will restart the last event timer.
Here's a similar setup. The turning off options are all OR conditions. You need a "stays pending" under limit turning off. Not sure if it's strictly necessary, but you may want to add the sensor to the means to activate.
OK, but I dont need the motion to start it?
Must admit I find room lighting confusing, it can do so much, but confuses me totally.
2 Likes
But thanks both, I'll give it a go and see if it solves my issues.
As I said, I wasn't sure if you strictly needed to include in the activation. I ran a test. You don't. But it does no harm. You definitely do need a "stays pending" restriction.
Sorry Bill, can you explain the stays pending rule?
Thanks
There are some shortcuts in terminology within the UI that can make things not easy to follow. In the screen shot above it says 'Stays Pending'. The setup under 'Limit Turning Off under these Conditions' uses 'Stays Off Pending'. These stays both refer to the stays of 'Motion Sensors that All become and stay inactive'. As said before, the 'means to turn off' are OR events. The first to be true will turn off the lights. The 'stays pending' keeps the non-motion means from turning off the lights if there are motion sensors that have not timed out.
1 Like
@bravenel I think I’ve gathered that a group’s activator device cannot also function as the group’s indicator device, since any on/off for activation purposes overrides the indicator purpose. Would it make sense (as a feature request) to have the option of having two devices for a group; an activator device to control the group and an indicator device to indicate the group’s state?
Use case and discussion here
The app already works as you've described. The activator device can be controlled directly, but the switch state will automatically adjust based on how the RL app is configured. E.g. you have an 'any on' group, you turn the activator off. The RL app will turn the lights off. If any of them don't go off (and Hubitat believes they are on) or are turned back on, the activator switch state will be adjusted back to 'on' automatically.
Your issues in the linked thread indicate an issue with your particular setup. 'All off' with a lot of devices is a known potential performance issue and you should keep the conversation going there.
1 Like
Hmm. Ok, that's a fine way for RL to do it. I understand the activator needs to go off to trigger the event, so that makes sense. Good to know about it coming back on if not everything actually turned off. For my purposes, I'd like some indicator to stay on until everything in the group is confirmed off, so it sounds like I just need to create a duplicate group for that. Easy enough.
It has that as well, look at the device page and it has "group state" that will say all off, some on etc and it only goes to all off when they all report as off.
Hi Everyone,
Does anyone know if I can SetEffect for RGB LEDs through Room Lighting? I can't find any option other than turning them on/off and setting a colour.
Thanks
