I am trying to use this app to work as a wake up light for the morning. I can’t figure out how to associate it to a light? I have setup the scene, and added a schedule. For every weekday @ 5:45.
If you are using UI7, do the following:
Create a new scene by selecting the “Add Scene” button then select the trigger as “Schedule”, set the interval to weekly, set the weekdays, set the time as “At a day of time” and set it to 5:45 AM. To commit it select “Validate” and select the “Next Step”.
On Step 2: Add the selected light source and select the “Next” button. Select the “ON” then press the “Validate” button. I would highly recommend to input a delay action by adding “Waiting For…” then the amount of time then select the same light source above but this time set it to the “OFF” selection and “Validate” it.
Djrakso thanks for your response. I thought about it later I should have mentioned I’m on ui5. I had to downgrade last week because I couldn’t get 1/2 my devices to sync.
I’ve had a scene (called Reveiile) running for years during work days. It switches on my night stand light as well as my Yamaha receiver and sets that to tuner. After 15 minutes it switches off both.
Create a scene.
Device tab: Select the light you want to switch on by clicking on it’s ON button
Schedules tab: Create a schedule. Select the days you want this scene to run. For time make sure you select ’ At a certain time of day’ and enter the time you want it to run.
If you want it to switch off after a set time, go back to the Device tab and at the ton, to the right of the scene name, click immediate. Then click manage delays. Set up the delay and click the OFF button of the light you switched on above.
Save the scene and test it out.
Bofh, I somewhat understand how to scene like that. What I am looking to do is use this “wake up light” app. What it does is allows you to have the lights work like ex: 5:45am 10%, 5:46am 20% ane so on. Basically so it simulates the sun rise.
OK, I found the app you are talking about in the Vera app store. It’s help file with instructions is here http://www.antor.fr/apps/wakeup-light/ but unfortunately it is in French. Good news is that it has pictures. However, there may be an issue with it based on the 1 comment in English I can read.
Using delays you really do not need that app. More work programming though. Providing your light is on a dimmer, switch it on to 10% at 5:45, set a delay for 1 minute and set the light to 20%, set a delay for 2 minutes and set the light to 30% etc. (Delays are calculated from the time of scene start)
BoFh thank you very much. I don’t know how in the heck you found that, I’ve been searching for weeks. Also thanks for the backup plan.
Just incase anyone else ever needs this:
WakeUp Light
Description: Module to simulate a light alarm clock with your bedside lamp and a dimming Module
Install Support
To make the plugin, I left a very good plugin “WakeupRamp” of ZMaF you can find here on the forum Micasaverde . This plugin provides the ability to generate a gradual increase of light. This is a good start, but not enough to make light alarm.
Initially, I used the WakeupRamp coupled programmed scene. Not bad for beginners, but it had a major flaw: the time that it was programming on stage corresponded to the start time of the ramp while on this kind of awakening, is set the end time of the ramp is the time from sunrise … even if mental arithmetic is good for our brains, eventually it wears out and it’s not very WAF. Then I had the idea to create a plugin to match my personal use.
1 / Installation and plugin configuration
Just go in APPS and install applications on the VERA and download the module Wakeup light .
Once installation is complete, a new module has appeared on your interface:
Press the “Reload” button on your interface to restart the vera
After the restart (refresh page may be required), enter the advanced settings of the module.
The setup is fairly simple, you must set the following parameters:
Devices : ID List lights you want to control your alarm clock. (Eg 14.36)
Ramp Time Min : This parameter defines the default duration of the light rail (in minutes). You can then change the time for each of your timers. This is also the time that is taken if you activate the module in a scene.
maxLevel : This is the maximum position of the ramp
minInterval : This is the minimum time between two second light level increases (in seconds). If your drive module does not lift info, you should increase this setting to facilitate the detection of a manual shutdown.
inhibitingDevices (optional): the list of modules ID conditioning the alarm rings separated by commas. By default the module starts when all the modules in this list are off (off). If you want the module to launch only if the module is on (on) must be added at least one id. Example: 36 = -27.45 The alarm will not launch if the module 36 and module 45 are off (off) and the module 27 is on (on).
2 / Using the Module
2.1 Programming the alarm time
Because an alarm, it is primarily an alarm, after using for several months a scene, I found the programming mode schedule suitable for this use: Single alarm / Repeat Daily / etc … So I kept this principle for the plugin. So I kept a similar graph made even if the mechanics behind was fully developed for the occasion.
Some screenshots to illustrate:
Below the home screen of "Timer s "(for what we can put several :)). This screen shows a summary of each half. Since the check box, it is very easy to enable / disable one or more.
Add the Timer button to add new ones:
In this screen we choose the parameters of our “Timer”: name, duration, type (Interval / Weekdays / Days of the Month / Absolute) …
Nothing very complicated, since we find this principle in the programming of scenes with one difference: now that is selected is not the time to start the ramp but of the maximum reached .
2.2 The manual shutdown
As on the original plugin (with some additional bug fixes), it is possible to stop the ramp if you manually turn off your bedside lamp during the cycle.
For this to work as much as possible, I suggest you use the drive AEON Lab (which you will find here at Planet Home automation or here at Domadoo ). Indeed this module makes a info recovery immediately, while for others, it takes a poll … which can cause non-detection of your order by Vera, so consequently the plug-in.
2.3 Control via Scene
In addition Timers, it is still possible to use the plugin through your scenes. You can use it with the plug-in Google calendar, for example.
2.4 Trigger Condition
Via the setting of the plugin, it is possible to condition the alarm is triggered depending on the state of one or more modules. For example, if you like me a flag that lets you know if there’s someone at home, you can ensure that the alarm does not launch if this flag is active (or inactive noted) . We will see the settings in more detail in Chapter 2 of this article.
Simple really. 
Go to the app store, locate the Wake Up app and click on details. Then go to the rightmost tab that says HELP anc click it. For most apps, that brings up documentation or a FAQ at least.
Thank you for the translation. I speak multiple languages but French is not one of them…
Here is this LUUP code I found here years ago for a sunrise simulator, works great. just change your device id, start and end light levels and how long you want it to take from start to end.
[code]do
– the numbers of the devices to control
local device_numbers={6}
– the number of minutes to run the cycle over
local cycle_minutes=45
– the starting level for the cycle
local start_level=1
– the ending level for the cycle
local end_level=40
– minimum time between steps in seconds. To avoid too frequent updates
local minimum_time=30
local step_increment=math.ceil(minimum_time4/(cycle_minutes3))
local seconds_delay=step_increment * math.ceil(cycle_minutes*0.75)
local dimmingUp=true
local onDetected=false
function setLevel(percent)
-- convert the percentage through to a number
local percentNum=tonumber(percent)
-- check if the first light is on - abort if someone has turned it off when rising. Give it a couple of cycles to check
local lul_tmp = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", device_numbers[1])
if (onDetected and dimmingUp and lul_tmp == "0" ) then
luup.log("SUNRISE: device is off, so quitting")
return
end
-- calculate the dim level based on a sinusoidal curve
local dimLevel=start_level+ math.ceil((end_level-start_level)/(1+math.pow(2.71828183,((50-percentNum)*12/100) ) ))
luup.log("SUNRISE: percent="..percent..", dim level="..dimLevel)
local currentLevelNum=0
local currentLevel=""
for i,device_number in pairs(device_numbers) do
currentLevel=luup.variable_get("urn:upnp-org:serviceId:Dimming1", "LoadLevelStatus", device_number)
currentLevelNum=tonumber(currentLevel)
if( (dimmingUp and currentLevelNum<dimLevel) or (not dimmingUp and currentLevelNum>dimLevel)) then
luup.call_action("urn:upnp-org:serviceId:Dimming1", "SetLoadLevelTarget", {newLoadlevelTarget = dimLevel}, device_number)
else
if( dimmingUp and currentLevelNum>= end_level) then
-- the light is already beyond the final level, so stop
luup.log("SUNRISE: light already up to "..currentLevelNum.." out of "..end_level..". Quitting")
return
end
if( currentLevelNum<=end_level and not dimmingUp) then
-- the light is already beyond the final level, so stop
luup.log("SUNRISE: light already down to "..currentLevelNum.." out of "..end_level..". Quitting")
return
end
end
if(not onDetected) then
local currentLevel = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", device_number)
if(currentLevel=="1") then
onDetected=true
luup.log("SUNRISE: setting onDetected to true")
end
end
end
-- keep going until the dim level reaches the final level
if( (dimmingUp and dimLevel<end_level) or (not dimmingUp and dimLevel>end_level) ) then
percentNum=percentNum+step_increment;
luup.call_delay('setLevel', seconds_delay , percentNum,true)
end
end
local device_id_list="";
if (end_level<start_level) then
dimmingUp=false
end
for i,device_number in pairs(device_numbers) do
device_id_list=device_id_list…device_number…“,”
luup.call_action(“urn:upnp-org:serviceId:Dimming1”, “SetLoadLevelTarget”, {newLoadlevelTarget = start_level}, device_number)
end
luup.log("SUNRISE: starting for devices "..device_id_list.." starting from "..start_level.." going to "..end_level.." in "..(80/step_increment).." steps in "..cycle_minutes.." minutes, stepping every ".. seconds_delay.. " seconds.")
setLevel(10)
end[/code]
Stevez I think it is apparent how much of a noob I am at this and I don’t even know where to start with what you posted. I just got my vera about a month ago and I’m just getting into this. One thing I didn’t like about the wake up app, is it seems if the scene is running you can’t turn it off at the switch. So say for instance it activates a morning maybe I’m going in later. Everytime I turn it off at the switch, a few seconds later it starts the scene again because it is still active. Will this Luub code you have eliminate this?
Do I just copy and paste the entire code you sent and change the few parameters? Is all this done under the actual device settings?
I found the original thread it was posted [url=http://forum.micasaverde.com/index.php?topic=7997.0]http://forum.micasaverde.com/index.php?topic=7997.0[/url]
I do not have UI7 but I would imagine there is a way to add luup code to a scene. just create a new scene and schedule you would like this to happen at and paste the luup code in the luup tap, change the device id to the device id of your switch, can be found under the settings tab or advanced tab of the dimmer switch you want to control, in my post it is 6 so just replace the 6 with whatever yours is, and change the settings if you want. make sure you hit the save lua button on the bottom before hitting the main save button. I dont have UI7 but this is how its done in UI5, hopefully its similar. and yes if it is running and you turn it off at the switch it will turn off and stay off.
I have ui5 and the Luup code you sent works very well. Exactly what i was looking for.