Algorithm

Thanks to Chris Jahn for reminding me about slow-dim-to-off. When the above programs turn the bathroom light off, you may wish to have the light actually dim to off over a 30 second or one minute time period. This rate of change in light level is fast enough for the occupant to notice it, and to make some motion to retrigger the light, and is slow enough to give him plenty of time. This slow-dim-to-off is a technique I use widely where there are motion sensors/timers turning lights off. I have written it up as an edit to the original post.

Hello Tim, First, apologies for a very tardy reply. It is difficult finding the time to get everything done. Second, thanks so very much for your very kind words. You are absolutely correct that many of these techniques are useful in a broad variety of applications. I use many of them widely myself. Finally, I have created the wiki article as requested.

Hi Rich, Sorry for the delay; we have been very busy here at UDI. I've written up my programs as a tutorial and posted them in the topic Using motion sensors in bathrooms.

Some may prefer not to use motion sensors as occupancy sensors in bathrooms, on the grounds that in such a location one certainly doesn't want the lights going off unexpectedly--a valid concern. However, I find the bathroom to be a location which gains a high level of convenience through automation, as long as the sensors provide complete coverage and the programming is made sufficiently solid as to avoid the above scenario. Here I will attempt to present examples of such programming. These programs will be based on INSTEON motion sensors and door contacts (TriggerLinc), but could be easily modified for X-10 sensors and contacts (DS10A). Some background on motion sensor use may be found in the topic How-To: X-10 Motion Sensors with ISY. To have the light simply turn on when motion is sensed, and turn off when the motion sensor times out: 1. Program Motion 1 - Enabled If Control 'Main Bath Motion.1-Sensor' is switched On And Control 'Main Bath Motion.1-Sensor' is not switched Off Then Set 'Main Bath Lights' On Else Set 'Main Bath Lights' Off This is less than satisfactory for several reasons. First, rather than having the on time controlled entirely by the motion sensor, one may wish to allow ISY to determine the timeout, thereby allowing the on time to be changed programmatically: 2. Program Motion 2 - Enabled If Control 'Main Bath Motion.1-Sensor' is switched On And Control 'Main Bath Motion.1-Sensor' is not switched Off Then Set 'Main Bath Lights' On Else Wait 4 minutes Set 'Main Bath Lights' Off Here the Wait time occurs after the motion sensor has timed out and sent the Off command, so if the motion sensor's timer is set to the default of one minute, then the total timeout period of this program will be five minutes. Another improvement is to separate the on portion and the timer portion of the program, in order to allow having the INSTEON On command sent to the light switch only when the light is currently off, thereby reducing INSTEON traffic by not sending redundant On commands when the light is already on: 3. Program Main Bath Motion On - Enabled If Control 'Main Bath Motion.1-Sensor' is switched On And Status 'Main Bath Lights' is not On Then Set Scene 'sMain Bath Lights' On Else - No Actions - (To add one, press 'Action') 4. Program Main Bath Motion Timer - Enabled If Status 'Main Bath Motion.1-Sensor' is Off Then Wait 4 minutes Set 'Main Bath Lights' Off Else - No Actions - (To add one, press 'Action') Here program 3 turns the lights on in response to motion, if they are not already on. When the motion sensor stops sensing motion, times out, and sends the Off command, its status becomes False and program 4 begins the countdown to turning the lights off. If during this period motion is once again detected, the motion sensor sends another On command, the sensor's status becomes True, and program 4 halts. The motion sensor control of the lights may be programatically enabled and disabled by use of a flag: 5. Program Main Bath Motion On - Enabled If Control 'Main Bath Motion.1-Sensor' is switched On And Program 'Main Bath Motion Timer Enable' is True And Status 'Main Bath Lights' is not On Then Set Scene 'sMain Bath Lights' On Else - No Actions - (To add one, press 'Action') 6. Program Main Bath Motion Timer - Enabled If Status 'Main Bath Motion.1-Sensor' is Off And Program 'Main Bath Motion Timer Enable' is True Then Wait 4 minutes Set 'Main Bath Lights' Off Else - No Actions - (To add one, press 'Action') 7. Program Main Bath Motion Timer Enable - NOT Enabled If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Program 'Main Bath Motion Timer Enable' To Run At Startup Else Set Program 'Main Bath Motion Timer Enable' To Not Run At Startup Here we use a program (Main Bath Motion Timer Enable) as a flag to determine whether the motion sensor should turn the light on (program 5) and whether the timer should be allowed to turn the light off (program 6). To allow the motion sensor to turn the light on, but prevent the timer from turning the light off, add the And Program 'Main Bath Motion Timer Enable' is True line only to program 6 and not to program 5. Notice first that the flag program is not enabled (the Enabled box at the right side of the window is not checked). This means that the program will never run automatically in response to changing conditions in the If; it will run only when told to do so either by another program, or by manually running it from the Program Summary tab. [There is one other condition under which it will run, and that condition will be explained in the next paragraph.] In this case, since the program has no conditions, it will not run automatically in any case. But clearing the Enabled box for programs which shouldn't run automatically is a good habit to get in to. Notice also that when the flag is made True (the Then is executed), the flag program sets itself to run at startup, and when the flag is made False (the Else is executed), the program sets itself to not run at startup. This is the other time (mentioned in the previous paragraph) when a program may run even though the Enabled box is not checked. When ISY reboots, each program which is not set to run at startup has its status set to False. Programs set to run at startup will evaluate the If conditions and run either the Then path or the Else path (thus making the program's status either True for False respectively) depending on whether the conditions evaluate to True or False. When a program which has no conditions is run at startup, the Then path is executed. As a result, when the Main Bath Motion Timer Enable program is set to True, it configures itself to run at startup so that after an ISY reboot (for example after a power failure) it will once again have a True status. Likewise, when the program is set to False it configures itself to not run at startup and therefore will again have a False status after reboot. The effect is that ISY remembers the state of this program even across reboots. With this code in place, the motion sensor control may be enabled and disabled by any desired action or schedule. For example, turning the Main Bath Lights switch Fast On to disable sensor control, and Fast Off to reactivate control: 8. Program Main Bath Motion Timer Enable/Disable - Enabled If Control 'Main Bath Lights' is switched Fast On And Control 'Main Bath Lights' is not switched Fast Off Then Run Program 'Main Bath Motion Timer Enable' (Else Path) Else Run Program 'Main Bath Motion Timer Enable' (Then Path) Notice that if the timer is currently counting down to shutoff (program 6) when the Main Bath Motion Timer Enable flag is set to False, the countdown will be halted. Now we approach the question of how long the timer should be set for. In light of the concern mentioned at the beginning of this article, the timeout must not be made too short. On the other hand, making the timeout longer than necessary results in wasted electricity and reduced effectiveness and convenience. Earlier I mentioned changing the timeout programatically, and in fact a two-level timing paradigm is one answer to the previous question. For example, I have an interior (no windows) main bathroom which is completely covered by the motion sensor, except for the bath/shower, because the bath/shower has doors which the sensor cannot see through. Consider that if the bathroom is occupied (as indicated by the motion sensor) but the bathroom door is open, then it is likely that the occupant won't be too long (perhaps washing hands, etc.). If the door is closed, on the other hand (but please don't close the door on either of your hands), the occupant might be expected to be somewhat longer, especially if bathing/showering, the exact conditions under which the sensor cannot see. The solution: a two-level timer. When the door is open, time out and shut off the lights (and fan) five minutes after motion ceases. When the door is closed, increase that time to 45 minutes, to allow for a nice hot bath or a leisurely 20 minute shower. It could be set even longer for that matter. After all, if the door is closed and there is no motion for an hour, there is a more serious problem than the lights being left on! The open/closed status of the door may be determined using either an INSTEON TriggerLinc, or an X-10 DS10A. To implement the two-level timer, the triggering portion and the timing portion of the timer program are separated to allow for a conditional timing interval: 9. Program Main Bath Motion Re-Trigger - Enabled If Status 'Main Bath Motion.1-Sensor' is Off And Program 'Main Bath Motion Timer Enable' is True Then Run Program 'Main Bath Motion Timer' (If) Else Stop program 'Main Bath Motion Timer' 10. Program Main Bath Motion Timer - NOT Enabled If Status 'Main Bath Contact.1' is Off Then Wait 40 minutes Run Program 'Main Bath Motion Timer' (Else Path) Else Wait 5 minutes Set Scene 'sMain Bath All' Off When the motion sensor status becomes False, the re-trigger program (program 9) starts the timer program (program 10). Should new motion occur during the countdown (or the Main Bath Motion Timer Enable flag become False), the re-trigger program halts the timer program. When the timer program is started, it will run Then if the door is closed; if the door is open it will run Else. The Else provides the five minute interval, while the Then provides a 40 minute interval before calling the Else for the final five minutes, prior to turning the scene (lights and fan) off. Notice that program 10 is not enabled, and this fact is important since we don't want the program to run automatically, but only when called. Next we should give some thought to what occurs following a power interruption. Since ISY cannot poll the status of RF devices (motion sensor, door contact), should it default to assuming the door is open or closed? In the case of an interior bathroom, if the power fails while the bathroom is occupied and the door is closed, the occupant will likely open the door since there will be no light. During a power failure, should someone enter the bathroom it is unlikey he would shut the door, as there would be no light. So either way, when the power returns it is quite likely the door will be open. However, once power is restored and ISY reboots, it can take ISY five minutes to query the INSTEON network in a modest installation and much longer in a large installation. During that time someone may very well enter and close the door. Clearly it is safer to assume the door is closed, since that will provide the longer timeout period before shutting off the light. The downside is that if someone enters, thereby triggering the motion sensor, and then leaves without having ever shut the door and then opened it, the lights/fan will take much longer to time out than is necessary. This condition will persist until the door is closed and opened. As it turns out, when a device status is unkown, as in the case of RF devices following reboot, ISY defaults the status to Off with regards to programs. So in program 10 the door status will default to closed. There is a third possibility, and that is to remember the door status just as we remember the enable flag: 11. Program Main Bath Door Status Closed - NOT Enabled If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Program 'Main Bath Door Status Closed' To Run At Startup Else Set Program 'Main Bath Door Status Closed' To Not Run At Startup Next we need a program to set or clear the flag when the door closes or opens: 12. Program Main Bath Door Status Change - Enabled If Control 'Main Bath Contact.1' is switched Off And Control 'Main Bath Contact.1' is not switched On Then Run Program 'Main Bath Door Status Closed' (Then Path) Else Run Program 'Main Bath Door Status Closed' (Else Path) The reason for two separate programs is because the flag program which we wish to remember across reboots, should not have any conditions in the If clause to ensure that it assumes the proper state after power up. Were we to place the above conditions in the flag program, the flag would always be False (door open) after a reboot. Finally, we modify program 10 to test the flag: 13. Program Main Bath Motion Timer - NOT Enabled If Program 'Main Bath Door Status Closed' is True Then Wait 40 minutes Run Program 'Main Bath Motion Timer' (Else Path) Else Wait 5 minutes Set Scene 'sMain Bath All' Off One question we have not addressed to this point is what should happen if the door opens or closes during the countdown period? In the above programs, the timer will continue with whichever time period it is currently running. We can modify the Main Bath Door Status Change program (program 12) to restart (or stop) the timer when the door opens or closes: 14. Program Main Bath Door Status Change - Enabled If Control 'Main Bath Contact.1' is switched Off And Control 'Main Bath Contact.1' is not switched On Then Run Program 'Main Bath Door Status Closed' (Then Path) Run Program 'Main Bath Motion Re-Trigger' (If) Else Run Program 'Main Bath Door Status Closed' (Else Path) Run Program 'Main Bath Motion Re-Trigger' (If) Here, each time the door status changes, the re-trigger program (program 9) is called. If the motion status is On, or the enable flag is False, the timer will be stopped. Otherwise, the timer program (program 13) will be called again, will reevaluate the door status, and initiate the appropriate time interval. Another feature we could add is to have the fan turn on if the door is closed and the light is on: 15. Program Main Bath Door Status Closed Fan On Timer - Enabled If Program 'Main Bath Door Status Closed' is True And Status 'Main Bath Lights' is not Off Then Wait 5 minutes Set 'Main Bath Fan' On Else - No Actions - (To add one, press 'Action') If you wish to have the fan turn on immediately, simply remove the Wait. Finally, as with any INSTEON motion sensor application, we can take note of a low battery indication: 16. Program Main Bath Motion Low Battery - Enabled If Status 'Main Bath Motion.3-LowBattery' is On Then Repeat Every 24 hours Send Notification to All Else - No Actions - (To add one, press 'Action') Putting it all together, a complete program group (contained within a f_Main Bath Door/Motion folder for organizational purposes) may look like this: Program Main Bath Door Status Change - Enabled If Control 'Main Bath Contact.1' is switched Off And Control 'Main Bath Contact.1' is not switched On Then Run Program 'Main Bath Door Status Closed' (Then Path) Run Program 'Main Bath Motion Re-Trigger' (If) Else Run Program 'Main Bath Door Status Closed' (Else Path) Run Program 'Main Bath Motion Re-Trigger' (If) Program Main Bath Door Status Closed - NOT Enabled If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Program 'Main Bath Door Status Closed' To Run At Startup Else Set Program 'Main Bath Door Status Closed' To Not Run At Startup Program Main Bath Door Status Closed Fan On Timer - Enabled If Program 'Main Bath Door Status Closed' is True And Status 'Main Bath Lights' is not Off Then Wait 5 minutes Set 'Main Bath Fan' On Else - No Actions - (To add one, press 'Action') Program Main Bath Motion Low Battery - Enabled If Status 'Main Bath Motion.3-LowBattery' is On Then Repeat Every 24 hours Send Notification to All Else - No Actions - (To add one, press 'Action') Program Main Bath Motion On - Enabled If Control 'Main Bath Motion.1-Sensor' is switched On And Status 'Main Bath Lights' is not On Then Set Scene 'sMain Bath Lights' On Else - No Actions - (To add one, press 'Action') Program Main Bath Motion Re-Trigger - Enabled If Status 'Main Bath Motion.1-Sensor' is Off And Program 'Main Bath Motion Timer Enable' is True And ( Status 'Main Bath Lights' is not Off Or Status 'Main Bath Fan' is not Off ) Then Run Program 'Main Bath Motion Timer' (If) Else Stop program 'Main Bath Motion Timer' Program Main Bath Motion Timer - NOT Enabled If Program 'Main Bath Door Status Closed' is True Then Wait 40 minutes Run Program 'Main Bath Motion Timer' (Else Path) Else Wait 5 minutes Set Scene 'sMain Bath All' Off Program Main Bath Motion Timer Enable - NOT Enabled If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Program 'Main Bath Motion Timer Enable' To Run At Startup Else Set Program 'Main Bath Motion Timer Enable' To Not Run At Startup Program Main Bath Motion Timer Enable/Disable - Enabled If Control 'Main Bath Lights' is switched Fast On And Control 'Main Bath Lights' is not switched Fast Off Then Run Program 'Main Bath Motion Timer Enable' (Else Path) Else Run Program 'Main Bath Motion Timer Enable' (Then Path) ----EDIT------------------------ Thanks to Chris Jahn for reminding me about slow-dim-to-off. When the above programs turn the bathroom light off, you may wish to have the light actually dim to off over a 30 second or one minute time period. This rate of change in light level is fast enough for the occupant to notice it, and to make some motion to retrigger the light, and is slow enough to give him plenty of time. To do this, you can create two scenes for the lights; one with a quick ramp rate for turning the light on, and the other with the slow ramp rate for turning the light off. Alternately, you could use a single scene with a slow ramp rate for turning the light off, and then use Fast On with the same scene to turn it quickly on. My preference is to use two scenes, because using Fast On will cause the lights to come on to 100% with the fastest possible ramp rate (.1 seconds or nearly instantaneous). I usually set my lights to come on to 90% with a .5 second ramp rate. This slower ramp rate and reduced level reportedly should increase the life of the bulb significantly. This slow-dim-to-off is a technique I use widely where there are motion sensors/timers turning lights off. I don't use it in my main bathroom only because that location has CFL bulbs controlled by a relay switch rather than a dimmer, and I therefore forgot to make mention of it. In my master bedroom and ensuite I don't use motion sensors. Rather, there is a KeypadLinc in a pedestal on either side of the bed. Each has a button which causes both the lamp on the corresponding side of the bed, and the ensuite lights to do a slow fade up which is easy on the eyes in a dark room, to a low level sufficient for the purpose at hand but not bright enough to wake someone. ----END OF EDIT----------------- This is just one of many possible approaches to automating bathroom lights and fans. Please share your thoughts, comments, ideas, likes and dislikes.

Hi Rich, Definitely I would have motion turn the light on, yes. Then after a period of no motion, turn the light off. My main bath has a motion sensor which covers the room completely, except for the bath/shower, because the bath/shower has doors on it which the sensor can't see through. The main bath door also has a TriggerLinc (formerly a DS10a), so ISY knows whether the door is open or closed. The idea being that if the door is open, the occupant won't be too long (washing hands or whatever), but if the door is closed the occupant could be having a bath/shower and therefore not re-triggering the motion sensor. When the door is open, the lights (and fan) shut off after five minutes of no motion. When the door is closed, that time is increased to 45 minutes, to allow for a nice hot bath or a leisurely 20 minute shower . It could be set longer for that matter. After all, if the door is closed and there is no motion for an hour, there is a more serious problem than the lights being left on! But when the door is opened, the timer reverts from the long period to the short period, so the lights don't stay on for 45 minutes!

Hello Dave, My pleasure, and thanks so very much for your kind words. They really do mean a lot to all of us here at UDI, and are much appreciated! Darrell

It appears your ISY does not have a certificate (other than the default) installed (step 7 above). When you are on location, you should install a certificate (can't be done remotely). When your browser presents the certificate warnings, you can choose to accept the certificate permanently, after which you should no longer see the warnings.

In the beta, the motion sensors were going through batteries very quickly, because the sensors were never going to sleep (were always listening for RF signal). I experienced this myself. The problem was corrected for the production version. My production unit is still on its original battery. The beta version did send the low battery ON command; can't say from experience about the production unit. Could this be a regression?

Hi Richard, It has been my experience that most Linksys routers do not provide for DHCP reservations (some few do), while most D-Link routers do provide them. A static IP address should work fine in your ISY. From an earlier post of yours, your router's IP address is 192.168.1.1. Should you wish to try again to give ISY a static IP address outside the router's DHCP pool, configure ISY as follows: ISY IP: 192.168.1.x Subnet Mask: 255.255.255.0 Default Gateway: 192.168.1.1 (your router IP) DNS Server: 192.168.1.1 (your router IP) Remember to use upper-case 'Y' to answer each prompt. ISY will reboot. If you do, please let us know how it goes.

Hi Tim, In that case, create a program like you posted, but remove everything from the IF, and have the THEN activate the ALL OFF scene. Set the program to run at startup. Now, every time ISY reboots (whether following a power failure or when you reboot by updating firmware, etc.) the scene will be activated. When a run-at-startup program has an empty IF clause, the THEN is run.

Hi Tim, The firmware, and therefore the programs, should run identically on either an ISY-26 or an ISY-99i. The difference is not in the hardware, but in the fact that the firmware has been updated (probably several times) between the time you moved from ISY-26 to ISY-99i, and now. What firmware is in your ISY? If your program is set to run at startup, then it is running at startup. When it runs (at startup or at any other time), it evaluates the IF. If the IF is TRUE, the THEN is run; if the IF is FALSE, the ELSE is run. So in your program, if any of the KPL buttons is ON when the ISY is rebooted, the program will run the ELSE and therefore not turn off the scene. Is that what is happening (check program's last run time and true/false status)? And isn't that what you want?

Hi Indy! I was a beta tester for the motion sensor. My beta unit did generate a low-battery command. But, those betas would go through batteries very quickly... turns out they were not timing out, but were drawing full power continuously. My replacement unit (1.0) hasn't yet had the battery die, so can't answer your question directly. But, it is in about the most active location in the house. It sounds to me like your batteries are dying too quickly, though perhaps not as fast as the beta units!

This wiki article lists the userid/password requirements: * Both User ID and password must be entered. * User ID and passwords are case sensitive. * The ID and password are limited to 10 characters maximum. * The ID and password have a minimum of 3 characters. * These characters are not allowed: < > / ; &

Hello David, KPL dimmer firmware version .29 and lower require you to physically set the desired button state, as suggested by the message you are seeing. KPL dimmer firmware version .2c and above will allow you to set the state with the Admin Console, as per your screenshot from the wiki. I don't have a .2a or .2b KPL to test. There are other non-toggle differences as well between the firmware versions. See this thread.

I picked one of these up today. One more question: No indication on the ISY whether it should be tip-pos or tip-neg. Which? Thanks, --Mark Hi Mark, The spec. is for 5VDC centre positive @300mA min. I use a universal adapter set to six volts. MikeB has indicated that both 6V and 4.5V will work; not sure if he has a preference for one over the other.

Yes! On the Configuration tab, on the System sub-tab, in the System section, there is a Reboot button.

Thanks Rand . The problem is this: when you link or restore the RL, and then press one of the number buttons (either on or off) to exit linking mode, it seems that the link for that button is being corrupted--the first byte is changed to a 0x02! It's okay to press one of the All On/All Off/Bright/Dim buttons, or to just let the RL time out. After I ran across this problem myself (and discovered the link corruption), I started testing with customers who called with an RL problem, and have already talked to at least two with this problem (it seems natural to reach over and tap one of the number buttons to take the RL out of linking mode, right?). Joe makes three, and I think that's sufficient data that I'm going to send this off to Smarthome. Joe, thanks so much for the feedback; it is helpful and appreciated.

Hi CJ, Your idea of having ISY track mutually exclusive button presses is interesting. I'm not sure how difficult it would be, but you could post it in the Product Requests forum. Yes, with version 2.7.0 ISY does get the status of secondary buttons when the main button is queried, as you observed. Do you mean that you would like ISY to remember KPL buttons states through a power failure? ISY does query the network when it reboots (now including secondary buttons), so it should find the current true state of the buttons after a power failure.

to_lighter, First, Adjust Scene can only adjust a scene controlled by ISY; it will not adjust the same scene as controlled by another controller in the scene. Next, as Rand mentioned, it remains in force until it is once again changed, because it modifies the the links in the devices, and therefore it will result in significant INSTEON traffic for a large scene. Finally, it only changes the devices' links, so yes you would then have to activate the scene to have the new settings take effect. Depending on how often you wish to modify the scene, all of the above may be perfectly acceptable. However, if your reason for having two scenes is due to the fact that you make frequent use of both, then you would do better to keep both scenes, in my opinion, unless you are not using a long ramp rate for the 100% scene, in which case Rand's idea of using Fast On is an excellent one.

Hi CJ, Instead of switched Dim, try using switched Fade Down.

Hi Guys, The difficulty I see with Wayne's programs, though, is that once motion has turned the light on (and assuming there are no manual button presses), the light will always turn off in exactly four minutes, regardless of whether there is further motion. Was that the intent, Wayne? With Rand's programs, a motion sense turns the light on full (direct link), and then after one minute (again assuming no manual button presses) the light is turned on low (where someone else might have it turning off). If another motion on command is received, the timer will re-trigger. The problem, though, is that if there is continuous motion, the motion sensor will not send another on command, because the motion is causing its internal 30 second countdown timer to re-trigger. Therefore the programs will turn the light low or off after one minute even though there is continuous motion. The only way the ISY's timer will be re-triggered is if there is a 30 second period of no motion to allow the sensor's timer to time out, followed by new motion within the remaining 30 seconds of the ISY's one minute interval.

Hello sorka, The Program Summary tab has an Activity column which should display Idle, Running 'Then', or Running 'Else'. The Last Run Time, Last Finish Time and Next Scheduled Run columns are self-explanatory; from them you can tell when the program last ran. The Status column displays True or False as the program last executed the Then path or the Else path. When your security panel arms, you can have a program run the Then path of a state program, which will make that state program's status True; when the panel is disarmed, a program can run the state program's Else path, making the state program's status False.

Hello Ken, The RemoteLinc's address label should be found inside the battery compartment (you may need to remove one or more batteries).

Thanks, Rand!

Hi Doug, I like that idea! For now, though, the following workaround might help: Scene: sbGreen KPLg as responder Program: Green Status If Status 'KPLg' is not Off Then Set Program 'Green Startup On' To Run At Startup Set Program 'Green Startup Off' To Not Run At Startup Else Set Program 'Green Startup Off' To Run At Startup Set Program 'Green Startup On' To Not Run At Startup Program: Green Startup On If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'sbGreen' On Else - No Actions - (To add one, press 'Action') Program: Green Startup Off If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'sbGreen' Off Else - No Actions - (To add one, press 'Action')