Good news! I have a new version of the app working that allows multiple new ways of controlling it, including turning off switches manually. I’m just polishing the layout of settings and the language to describe how everything works. I’ll be testing it thoroughly over the next few days, and will hopefully get it published early next week.
Stay tuned!
Awesome. Looking forward to it.
Great… I always enjoy the updates to this. My wife had me turn it off in our room, but its been very effective in waking up the kids.
I installed Genle Wake Up two weeks ago, and I haven’t gotten it to run yet. It performs the “Completion Actions,” but never actually ramps the primary bulb up. I’ve reconfigured it a dozen times to no avail. The scheduledstart is even listed correctly in the IDE. shrugs
Let us know when the new version goes out, and I’ll see if I have the problem then. I look forward to using it. 
Thanks!
@brianjlambert, I have a few questions for you. As long as I’m updating it, I might as well fix some bugs 
When you look at your settings, what does the first page say your dimming settings are? 0% - 99%, current value to 99%, or something else entirely?
How long is your dimming duration?
When the completion executes, is it around the time that dimming is supposed to start or closer to when you’d expect the completion to execute?
What are you trying to dim? A Jasco in-wall switch, a hue bulb, a centralite dimmer, etc.?
Hopefully, I’ll be able to reproduce what you’re seeing. Thanks.
When you look at your settings, what does the first page say your dimming settings are? 0% - 99%, current value to 99%, or something else entirely?
How long is your dimming duration?
“All dimmers will dim for 30 minutes from Current Level to 99%”
When the completion executes, is it around the time that dimming is supposed to start or closer to when you’d expect the completion to execute?
I actually don’t know this answer. I disabled the completion action several days ago as part of my tweaking the settings and I forgot to look. I just know the completion light was on. I couldn’t find the answer in the logs (it does a health check a several times an hour which makes the log very long).
What are you trying to dim? A Jasco in-wall switch, a hue bulb, a centralite dimmer, etc.?
OSRAM LIGHTIFY LED Tunable White 60W bulb
Hopefully, I’ll be able to reproduce what you’re seeing. Thanks.
No, thank you 
Try changing your option to 0% to 99% instead of current value to 99%. If the bulb was at 99% when it was turned off last, then the bulb might still think its level is 99%, so it just comes on.
And in particular, the Osram bulbs had a firmware issue where they would forget their current level when turned off (unless you updated it via the Lightify gateway) that could be causing issues.
Which is exactly why I asked that question 
There’s a weird bug where setting 0 sometimes turns into current value because 0 equates to false somewhere along the line. It doesn’t happen every time, but I’ll make sure I figure that out.
Thanks. I changed it to 1. So i’ll see how that works.
Update: It appears to be working now when I press the start button (which it never did before). So, changing it from 0 to 1 was the key (and the bug).
Thanks!
Sweet! I’ll definitely fix that bug, and maybe I’ll add a paragraph element explaining the pitfalls of using current value.
Thanks @Sticks18 for your help.
Thanks Steve - I’m looking forward to seeing how this works when you are done.
In the meantime - re previous discussions with @DrHill - I’ve manage to get this working exactly as required using rule machine
Ok. So, one last issue, which may be unrelated to the actual app code. The App triggered exactly on time this morning (7:15 AM) Yay! 
, but it only ramped up to 17% before stopping. 
According to the IDE, the next increment was scheduled at 7:21:16 AM CST, but never fired. 
This is probably due to the ongoing bugs where scheduled actions fail to perform, but I figured I’d let you know in case it was something that can be fixed. Thanks.
Hi Adam, would you mind showing how you did this with Rule Machine, maybe in that thread so as not to hijack this one? Thanks.
sigh. That’s very frustrating. I have a backup schedule that runs less often to make sure dimming keeps going even if the main schedule fails. It’s rare that both schedules fail, but not impossible. Let me know if it happens again, and I’ll try to improve the scheduling logic.
An update on my testing: 
Everything seems to be working exactly as I would expect. However, stopping the dimming process with lights that are actively being dimmed does not always work due to Gentle Wake Up sending them a new command before they get a chance to report an off state. It’s especially bad if you use the Hue app to shut off a Hue Bulb. However, the Jasco in-wall dimmers that I have are pretty good about it.
As for releasing this version, I was hoping to do it this week, but we’re pretty busy with CES so I don’t think it’ll go out until next week. Which might be better anyway, because I found a way to make Hue bulbs way more efficient. With this new way, I’ll also be able to stop dimming using a Hue bulb.
I’ve also been thinking about how to allow custom colors to be set, but I don’t think I’ll get that in this release, unfortunately.
Awesome news. Have fun at CES.
Gentle Wake Up worked flawlessly this morning, so it must have just been a one-off glitch. I will report back if I have any more failures.
Yes:
There are multiple rules needed but this way offers a lot of flexibility
1 Start Rule
This is basically a trigger only that starts the process off. For me it is at a set time (5:15am), only on weekdays, and only when the mode is home. This way it wont trigger if we are away. It is set to have the lights come on at a certain colour at 5% brightness
the main Rule
Then there is the main rule: That has the following conditions:
Mode is Home (same reason as with the trigger)
Time is between 5:20 and 06:02 (this is the period of waking up that I am interested in)
Only on Weekdays (same reason as with the trigger)
Lights that I am interested in are on (this is the clever bit that ensures that if at some point in the sequence I turn the lights off manually, the Gentle wakeup is canceled)
and the only action
adjust the lights by x amount (10 in my case)
The increment rules
These re just increment rules that cause the rule above to be re-evaluated. So I make 10 of these spread across the time frame that I am interested in. Importantly all they do is have the above rule re-evaluated.
Trigger: the increment time
action: re-evaluated main rule
Thats it
Gentle Wake Up in Rule Machine
Thanks @AdamV for your method. I will try it out starting tomorrow morning. I really do like the idea that it is cancellable (WAF brownie points there!) and that it is so flexible. i guess the only drawback is that the dimming won’t be as smooth and gradual.
It is a drawback - but to be honest when you are asleep for most of it you really don’t notice all that much !! and it really works - I get up much easier with this
Also - just to add… I’ve made a further improvement (Good for WAF!):
For the start trigger I’ve set it to disable when an on/off tile (called “Gentle WakeUp Alarm”) button is off.
and I’ve linked that button to a Gentle Wakeup Alarm tile in Smarttiles. We have a tablet in the room with smarttiles for control of everything in the room. So in the rare event that we are going to sleep on a weekday and know that we wont need to get up early (on holiday / ill / whatever the reason) - just tap the button and the alarm is disabled. Once the our routine is back to normal wakeup - just tap the button again to re-enable the alarm