Community, I need help getting this rule to work. I'm not 100% sure what I'm missing. I want the light to come on at 7:45 and slowly ramp up in a red color.
This is a Sengled RBG bulb if that matters.
Is something in particular not working? Your rule looks fine to me, and I tested something similar with a Hue bulb and got the expected results. Since you're using a Sengled, I'm going to guess: is it just not turning on at all? If so, what driver are you using? If you're not depending on any of the Sengled-driver-specific features, try changing to the "Generic Zigbee RGBW Light" driver instead of the dedicated Sengled driver (assuming that's what you're using). I'm not sure if the Sengled driver is still considered experimental, but I do know some people have noticed odd quirks with it on occasion. And either way, either make sure that color and level prestaging are disabled or consider adding a separate "On" action in your rule before any of the above.
If you want to test any of the above but not wait until 7:45 AM to see, try the "Run Actions" button in your rule--just a tip in case you weren't aware! You could also consider lowering the time it takes to ramp up (unless that was part of your problem; you didn't say what the problem was) for the purposes of testing and then set it back when you've got something that works.
Good luck!
1 Like
Thank you for the response, I should have notated that the bulb doesn't turn on during the schedule. But if I run the rule under run actions it works after I set color level to 2. I am using the Sengled driver and also have color and level prestaging enabled, should I not use that, what is best practice?
If you want to use color and level prestaging, you'll need an explicit "on" command somewhere. The point of prestaging is that it lets you send color and level commands to the device without turning it on, with the goal being that the next time you issue an on() command it will turn on to those settings right away (without prestaging, a color or level command will immediately turn the bulb on to that color or level). I'm actually surprised that running the rule as-is worked, though I don't know if RM secretly issues its own on() command to the bulb behind the scenes with any of those actions.
If your rule runs with the actions but not at your trigger time, I'd guess something is wrong with that instead. I see you have logging enabled. Shortly after it should run, if it doesn't, check your logs and see what the rule says it's doing. Also, make sure that your location, time zone, and time are correct in Settings > Location and Modes.
Ok say I want to leave pre-staging on how would I go about issuing the on command without it coming on at a much higher level than I want before the slow rise to full brightness?
I just looked up this post and looks like I have my settings right except I'm not sure how to.issue the on command with the fade up to 100%
Try using setLevel instead of on. Setting the bulb level will always bring it up to the level you order with the Sengled RGBW driver.
Will the setLevel allow for a gradual fade up to the final level like the Fade up to command?
What fade up command? Do you mean the start raising level command?
Fade Dimmer Level over Time is what I'm currently trying to use to slowly bring the brightness up. In this case 0-100% over the course of 15 minutes.
Wll, I would first use setLevel to 1 to barely turn the bulb on and then fade up over time like you were.
Yeah I have it configured to set the color to red and a level value of 2 then run the fade over time but the rule just isn't working.
You have to issue the setlevel separately if you have color prestaging turned on. just set the color, not the level. Then set the level. Then fade over time.
setLevel still won't turn the bulb on if you have level prestaging (a separate option from color prestaging; the poster said both were on) enabled. But I'm not sure what commands RM is really issuing behind the scenes here.
You could try putting an "on" second in your rule instead of first as I originally suggested; that way, if your color and level get prestaged only, the on() should turn them on to that color and level.
He said he wanted color prestaging on. If you want level prestaging on, which I don't understand why you would since setLevel does the same thing with the Sengled, you would do setLevel to 1 then on then fade over time.
But why in the name of all that's holy would you want to fade a red light up over 15 minutes anyway?!?!
LOL @Ryan780 I know it is a bizarre one. Our daughter is now a toddler and we are trying to slowly turn on a color lamp prior to her waking up to a particular color (red in this case) so that when she does wake up she knows it isn't time to get up yet. We will then have another rule that will change the color to green when it is time to get up for the day.
1 Like
I just want to say thank you to @bertabcd1234 and @Ryan780 for assisting with this rule last night. Checked it this morning and it is working as it should be.
Final working rule:
Logs from Rule:
Logs from Lamp:
1 Like
Community,
I am revisiting this RM rule and trying to add a wait/delay after the bulb goes 100% red for 15 minutes before changing color to blue. Right now the rule isn't working correctly as soon as it turns 8:00am the bulb immediately turns blue instead of waiting 15 minutes.
You need to edit the set color: Nursery Lamp Blue and scroll down to the bottom and toggle delay and set the 15 minute delay there.
