Room Lighting - Adjust Lights on Mode Changes

Yet another question about Room Lighting... The following rule runs my bedroom lights. Basically, if there is motion:

  • When mode is Home turn on the ceiling lights if the lux is low. If lux is high leave them off.
  • When mode is Evening turn on the two side lamps (bed & other) at 100%.
  • When mode is Asleep turn on the Other lamp at 20%.
    Turn the lights out when no motion for 5 minutes, except Asleep when Bed lamp should be left on (it's turned off with a button press).

I have a "getting ready to go to bed" routine that turns the Bed and Other lamps on when the Mode is still evening. Then the Mode changes to Asleep. So the lights are on when I go into the bedroom.

I thought that using "Adjust lights on Mode changes" would mean that the Other lamp should dim to 20% when I enter the bedroom and the motion is detected — which is what I want. But that's not what's happening. The Other lamp stays at 100%. The RL app shows it set to 20% but at 100% currently — and sorry I didn't capture that or the logs but I was really tired and just told Alexa to turn the darn thing off. After 5 minutes of no motion, the light works as expected.

I swear this worked when I first set this RL app up. There have been a few changes since then, so I wonder if this has been impacted by the changes or if I'm just not understanding how this should work?


This just adjust devices that are already active when a mode change occurs (e.g. moving from 'Evening' to 'Asleep'). It does not change the mode.

As for your overall problem, my first assumption is that you're not in the 'Asleep' mode, but it's hard to say without seeing the log data. You can enable logging in the RL instance and capture the logs for an activation that doesn't work the way you want it to.

How are you managing your modes?

Yes, that's what I expect to have happen: The light will change from 100% to 20% when the mode changes from Evening to Asleep.

My modes are changing as expected. I get a notification on my phone when the modes change, and I can hear that notification when it comes in. I double checked. The mode was Asleep. The RL app showed Asleep as the current function. The light did not change, either when the mode changed or with later motion. Once there had been 5 minutes of no motion, then the light worked as expected.

Logging is enabled. I'll see if I can get better logs tonight. As I said, last night I just wanted to go to sleep.

There have been a couple of bugs in RL lately, and I was wondering if this was another one. @bravenel ?

I'm using transitions for several lighting instances without an issue. The fact that RL thinks the device is at 20% but you say it's still at 100% seems like the anomaly. Does the device page also report 20%?

I don't know. I'll check tonight. Or I might try to run some experiments when I get home. As I said, this worked at first, and the last couple of nights it didn't.

No idea. Without logs to document what is actually happening it's impossible to say.

OK sorry about not doing this earlier... or posting after instead of before. I have other RL apps of this type that work just fine. And the change from asleep to home, and from home to evening, appear to work fine in this app. It's just the "Other Lamp" that is having problems when it's on and the mode changes to asleep. If nobody can see anything wonky, I'm tempted to just delete this rule and recreate it.

I ran a test to mimic my normal go-to-bed routine. And the Other Lamp did not dim to 20% when the mode changed.

This is what the RL app looked like after the mode changed to Asleep:

Here is the device page:

This is the RL app after 5 minutes of inactivity have passed, the light was turned off, and then motion turned it back on at 20%:

And here is the log:

Your logs you posted are confusing with too much going on for me to tell what is happening. Where is the mode change that should have adjusted the Other Lamp but did not?

hope this is better or easier to understand

OK, that got messed up on a change made for 125. Will get that sorted out.

3 Likes

Awesome! Thanks so much!

Sorry again for the poor troubleshooting.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.