arw01

SO If I understood correctly, this little program should reset the timer in the IF statement ANYTIME any of those items in the IF happen. Therefore the basement lights should not go off for 60 minutes after all these items have NOT occured for 60 minutes causing the wait to reset itself. If Status 'Motion_1-Sensor' is On Or Status 'Motion_2-Sensor' is On Or Control 'Basement_stairs_OH' is switched On Or Control 'Media_Exercise' is switched On Or Control 'Media_Middle' is switched On Or Control 'Basement_stairs_OH' is switched On Or Control 'Media_Popcorn' is switched On Or Control 'Media_Middle' is switched Off Then Wait 1 hour $OCC_basement_svr = 0 Set Scene 'Basement_Off' Off Else - No Actions - (To add one, press 'Action') 60 minute timer for any motion in the basement, if no motion, no switch activity, in that time, turn off all the basement lights

Much thanks to Apostolakis for the examples below. I will follow up with my interpretation and my attempt to put what has been so graciously shared into a real world application on my own system. Alan Nearly all of these things can be done using a "wait" command. You might need multiple programs depending on the details. I have illustrated this below separating all the different situations into individual programs, but many times they can be merged into a single program. The root timer program would be this: I have named it program 'x' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 300 minutes Set 'whatever you want' Off Run Program 'x' Else path Else - No Actions - (To add one, press 'Action') To expire the timer If - Put the condition here for expiring timer Then Run Program 'x' (Else Path) Else - No Actions - (To add one, press 'Action') To start (or restart) timer If - Put the condition here for starting (or restarting) timer Then Run Program 'x' (Then Path) Else - No Actions - (To add one, press 'Action') To do something if the timer is active If Whatever you want to cause ISY to check if timer is running And Program 'x' is True Then - Whatever you want to happen if timer active Else - No Actions - (To add one, press 'Action') To do something if the timer is inactive If Whatever you want to cause ISY to check if timer is running And Program 'x' is False Then - Whatever you want to happen if timer inactive Else - No Actions - (To add one, press 'Action') As far as I know, you can't compare the current location of a wait to anything else. Like if the wait had more than 60 minutes left versus less than 60 minutes. Many of the situations I listed above would not require multiple programs, but the multiple program best illustrates how you could make it do anything you want.

I too would love a nest, but without being able to talk to it directly etc I have been waiting. With the Honeywell lawsuit, who knows what "features" they will loose in the feature and just take away from you. Personally surprised there has not been an opensource kickstarter thermostat done yet with a full api.

Mark James, would you mind if your extemely excellent write was put into the Wiki? If it's there, I haven't found it yet in my many trips through there! Alan

Jeff, if you go slow about what you want to program. I am sure many of use would be happy to learn along with you and help as well where we are a few days ahead of you learning..

Silly question maybe, but did you put the switch, outlet, appliancelinc, whatever as a member of the scene itself?

Michael, sorry to be vague. Coming from misterhouse we used a timer object that let us do the following: set some_timer_variable_name 60*5 If expired some_timer_variable_name then turn off light if some event occurs restart some_timer_variable_name If some event occurs expire some_timer_variable_name We could do comparisons on the timer, e.g. If some_timer_variable_name < 300 then some action I want to occur If active some_timer_variable_name then do some other action For how the ISY does timers, I've not gotten my head around them yet. So for a occupancy timer you would just do something like this instead of the program calling a program that I haven't understood well yet: If motion_sensor State = "ON" Then restart house_empty_timer If some of the actual perl code would be more helpful, I can dig it out

Tonight, I deleted the other scenes, and re-added them to the kitchen scene. IF i use any of the keypad D buttons, OR the kitchen switchlinc, the keypads follow great. HOWEVER, if I turn the switch off with the ISY remotely, the keypads DO NOT follow. Therefore if I use the mobilinc, those keypads can be out of sync as well. Thoughts? Alan

As he indicated, the ISY can crash, hang, etc. If that happened then they thermostat program would continue to run and not cause his house to freeze..

To piggy back on this thread. How about a ISY capable thermostat for a tile radiant floor in a bathroom?

Could you guys expand on that a bit more.. Do we need the network module? And so you have your tasker do what when you get into the area or out of the area?

Do we just cut and past that whole url in place of the pool.ntp.org, or need to put something else in there?

what mail provider are you using as the relay?

Looks like I accidently set this up this way, the program may not even by necessary so I dis-abled it and see what's up.

Probably didn't have my head around scenes at the time. I will check back into my scenes and see what I have as a controller. It does, however, work pretty well. Alan

OK, maybe it will sink in if I ready it a few more times.. Control let you tell HOW it gets done, status just watches for changes... I use fast off control for the basement dark scene.

Your experience will help me with a similar issue soon, my iolinc should be coming soon as smarthome showed it back in stock. That was the application I purchased it for exactly. Do they come with the reed switches already?

I think that is fixed now, haven't noticed it being out of sync anymore. However, looking at another program I use to keep KPL buttons synced up, I wonder if I am causing the ISY extra work because of the method I choose in this: If Status 'Kitchen_oh' is On Then Wait 2 seconds Set Scene 'Media_Keypad_D' On Set Scene 'Garage_Keypad_D' On Set Scene 'Frontdoor_Keypad_D' On Else Wait 2 seconds Set Scene 'Media_Keypad_D' Off Set Scene 'Garage_Keypad_D' Off Set Scene 'Frontdoor_Keypad_D' Off I would think this runs all the time? However, the details on the program tab say it only seems to run with switch operation. I guess I don't totally understand the difference between status and control obviously. Is the ISY smart enough to just run this once until the status changes again on the switch and then it runs. What is the difference to control then..

The portsever idea sounds intriguing, as I suffer the same problems with the kids leaving things on all over the house... Be nice to turn off a few things downstairs that routinely get left on.

Oh, that Roomie remote might cause apple envy here. I am down the farm with android at my house, only a couple of ipod touch's around here... I emailed them that i was an ideal testing environment though Anyone know of a similiar android program that has come a long ways with that level of integration?

a scene with the kpl buttons in it. Then you query the io linc to see if the door is closed. if the door is open you turn that scene back on. I'd maybe put a timer program running to go off about 1 minute after the door is to have closed.

Have had it rattling around in my head for a couple of weeks about how best to handle occupancy sensing. If I use a state variable, it can trigger programs. But are you better to make a massive if or tree listing a bunch of common devices around the house? e.g. kitchen light, bathroom light, motion sensor here or there, stair lights, a bedroom light, etc. and run down the whole tree. Or on other programs that do something, make them set the occupancy variable? Anyone doing anything interesting besides just turning out the lights in 30 minutes of no activity around the house? Alan

I'm on the same quest at some point, but I just bought a ribbon of warm led lights off ebay and are using those currently with a directly wired power supply. This spring, Meanwell (sp), will have a 2amp triac dimmable power supply 12v for LED lights that is pretty inexpensive from comparisons to others in their catalog. (I am expecting under $30.00 from Jameco)

Your KPL STAYS ON when you press fast off? Yes, it sounds like there might be some interesting (and unexpected) interractions between the scenes and programs. Yes it was staying on, but I was not pressing the kpl button twice, the switch that has the fast off program was what I was pushing. I will monitor it now that the button is part of the fast off scene I was using. Now I need to figure out how I could delay the stairs as part of the movie scene I have. May have to do that only in a program. It's a on/off 2 wire kit, and it turns off before the other lights can even be noticed dimming.

I think your question has prompted me the find the culprit. The button toggles when I use the control-linc or the switch at the stairs, but was always out of sync when I happen to be downstairs as I often don't use the stair lights anymore since we put LED lights on the stair risers themselves. I did NOT have it as a member of a basement off scene that I use in a program from a fast off on the switch on the stairs. Since the KPL doesn't directly follow the device, I think it was out of sync because I would use this fast off and the kpl light would remain on as a result. I will check that shortly when the programming routine finishes writing it out.