TJF1960

I have one scene named Goodnight with all devices I want to turn off with various ramp rates etc., A program that runs true when I FastOn the kpl button by my bed. Works like a charm! Not sure why you need an upstairs scene and a downstairs scene but you can run both scenes in a program, might want to use a Wait 2 or 3 seconds between them though.

jnaiser60, If you can't say anything nice....... Michel, upgrade went perfectly. Thank You! Tim

Hello mzanni, Give it some time as there are just a handful of people fully up to speed on Elk that post here. I am sure they will offer suggestions.

Xathros, do you think the OP benefit from initializing the variable values in your examples in the event of a power failure and in the event the outletlincs for some reason stay on after power is restored?

Well, to quote LeeG "This option reverses the On/Off commands issued by the I/O Linc Sensor but does not reverse the Query response." It is used to issue an opposite command than what it would normally issue. Like Lee said though the biggest problem is when the I/O Linc is queried it will return its true state (not the reversed state). But since you are not using it that is not a problem. Based on your last post you may have some sort of communication error if the ISY wasn't showing the correct status of the Alarm sensor. First thing you should do is get that squared away then your program should work as you want it to. If the alarm sensor is part of a scene you can run a series of scene tests on it while monitoring the event viewer set to Level 3. If not then manually activate the I/O linc sensor input a series of times while monitoring the event viewer, again at level 3. Tim

I ran wire to each room, picked up some cheap small speaker boxes with wall/ceiling mounting included from a company called All Electronics http://www.allelectronics.com/make-a-store/item/SK-331/SATELLITE-SPEAKER-W/BRACKET/1.html I also picked up a small cheap amp which runs off of 12 Vdc and a pogoplug from eBay. Total cost about $100, but a lot of labor running the wires! Tim

LeeG, good point, I had forgotten about the trigger reverse query problem with the I/OLincs and I believe the OP is using one. It’s a new day and I have learned something new already this morning. After reading your post I ran a couple of more tests and found that a normal nightly query or a query on a specific device called by a program will in fact Not affect the conditional status in a program, unless the ISY has the wrong status (which is what I had originally thought). But as I tested last night if you right click the device node and select query it will affect the conditional status in a program…no matter if the status is correct or not! Barkster, are you using the I/OLinc with “trigger reverse†button checked? Tim

Well, tail between my legs..it goes to show you are never too old to learn something new. I am sorry barkster for steering you wrong on that one, you are 100% correct. I just set up a test and proved it. A query will run the Else on your program. That is the very reason I use very little programs with Else actions. Try changing "Status 'Alarm Sensor' is On" to: If Control 'Alarm Sensor' is Switched On and Control 'Alarm Sensor' is Not Switched Off This should fix the query problem and still run Then and Else as expected. Again I sorry for the bad info about the query. Tim

No, the else should only run when there is a change in the If condition. In this case if the Alarm Status is On then the Else will run when the Alarm Status switches to Off. So if/when the Alarm Status changes to Off then the Else will run. A query will not change the status of the device unless the ISY is out of sync with the device.

Well, that is a 1 part question with a 2 part answer! First let me preface by saying I copied your If conditions from your posted program…and was assuming if the alarm sensor is Off meant that the alarm was sounding or tripped. So if that is not the case and when the alarm sensor is On the alarm is sounding or tripped then you are correct. Change the If to alarm sensor is On. The second part of the answer is when using Status you do not have to duplicate the condition with a “Is Notâ€. That type of conditional programming is used when “Control†is used and provides the benefit of the program turning true or false depending upon whether the switch was turned on or off. I actually meant to leave it out of the example but forgot to remove it (darn copy and paste!) So basically if the Alarm Sensor turns On when the alarm is tripped and turns Off when the alarm is reset then that is why the program would not stop running, because the condition in the program was true. Had the alarm tripped again while the program was true the program would have turned false and stopped the flashing lights. Tim

Maybe something like this? If Status 'Feeders / Dog Feeder in Garage' is On Then Wait 2 seconds Set 'Feeders / Dog Feeder in Garage' Query Wait 30 seconds Set 'Feeders / Dog Feeder in Garage' Off Send Notification to Mark Set 'Feeders / Dog Feeder in Garage' Query Else Send Notification to Mark As long as the ISY knows the status of the device is On this program will run. If the status is actually Off the program will stop and turn False. If the status is indeed On then the program will wait 30 seconds during which if the status changes to False the program will stop. Otherwise it will turn Off the feeder, send a notification then run a final query to verify the status is Off. Question, is the ISY on a backup battery or UPS or generator? Or when the power goes out so does the ISY? The reason I ask is that if the ISY is not on backup power and the power goes out, the program may not run when power is back on even if the device status is On. The reason is once the ISY reboots all programs are set either true or false based on the conditions. While this program may be set to true depending on the conditions it may not run because there was not an event to trigger it after reboot. If this is the case there is a work around.

I use a similar approach as sanders2222. However, I think the key will be breaking your program into 2 programs jmed999 to get rid of the else statement. Create another program with the current else in the then section and set up the conditions for when you want it to run. Having anything in the else section can be tricky, especially when you have more than 1 conditon. Most of the time it is just plain easier to have 2 programs instead.

Not sure which is the economy setting, the Then or the Else but the first thing that comes to mind is that when the ISY is finished upgrading it will reboot which will set all variables to 0 unless they are initialized. Could this be the cause?

I am assuming when your garage door is closed the Sensor is On. I see only 2 ways that program will run true (Then). 1) The program was called by another program (or manually thru the admin console) 2) The sensor status was "off" when sunset occured. Maybe go back thru your logs for the previous 24 hrs to see if the sensor turned off but not back on.

So just to clarify, When the scene is turned on the ceiling lights turn off but the load button "A" for those ceiling lights stay lit?

No prob., right click on "Master Bedroom Keypad" and select "+ Group Devices" then all of the nodes for that kpl should group together like your kitchen lights kpl.

pyroman175@yahoo.com are you saying that you cannot right click on the kpl node and select "Group Devices" or are you saying you are trying to group the kpl nodes but they will not group? You do have to manually group them, I just am unclear as to whether you haven't or can't.

Upgrade from 3.3.4 went well also. Thanks, Tim

I am just over 500 programs. 78 Insteon devices of which 14 are 6 or 8 button kpl's 47 Integer variables 193 State variables 197 Network Resources 15 email customizations As the programs grew so did the length of time to open the program tab. I don't have homeseer but I do have a pogoplug with dsclink for the alarm and caiwc for 3 webcontrol boards along with the 3m-50 tstat and some other programs all connecting to and updating the 994ir pro constantly. It just took 9.3 seconds for the admin console to open and populate with status for all nodes and another 24 seconds for the program tab to finish loading. I can't say its so long though that it has really ever bothered me. Yes, it takes some time but the way I look at it, the benefits of the ISY far outweigh minor stuff. Just my opinion. Tim

Under the Variable tab are 2 more tabs. The first tab is Integer, the 2nd tab is State. In order for your program to run either the Then or Else the variable has to be a State variable, which should be contained in the State variable tab.

Good point. Only problem is if there is no motion after 9:45 the light will not turn off because the status of the motion is already off. I see where you were headed though...did you mean to "Run Program 'Down Stairs Lite Motion' If path" instead? In which case he can leave the turn off time at 10PM and add in your addition.

After giving it some thought I think the basic programs listed above could be changed slightly to provide the desired results. I have not tested this, but give it a try. Create these two programs for every On Level you wish, modifying for the different On levels as needed. Program “Front Porch Lights Snapshot On 60%†If Status Front Porch Lights >= 51% Status Front Porch Lights <= 60% And Program Blink Run is True And State Variable Blink Run = 0 Then Integer variable Front Porch Lights = 60 Prgm “Front Porch Lights Back On 60%†If Integer variable Front Porch Lights = 60 And Program Blink Run is False And State variable Blink Run = 1 Then Wait 2 sec Set Front Porch Lights 60%

No, these programs will only turn the lights full on or off. You could have the programs turn them on to any % but it would always be the same. In order to store and restore the light to a % On would require many more programs per light. It would be possible but likely would be more work than most people would want to tackle.

Any change in status of either of your If conditions will force the program to be re-evaluated, unless the second condition is not a state variable. I would agree with the others that the program should run as is, as long as the second condition is a state variable. Please double check that a state variable is being used. What is Outdoor Temp Alarm? Is it a thermostat or weatherbug or what?

Two programs came to mind, depending on your set up these may or may not work for you: Important to set this first program to "Run at Startup" also, assuming motion detector is not linked to anything but the ISY PLM. Program: Down Stairs Lite Sched If From 6:00:00PM To 10:00:00PM (same day) Then Set 'Devices / Dwn Stairs Lite' On Disable Program 'Down Stairs Lite Motion' Else Set 'Devices / Dwn Stairs Lite' Off Enable Program 'Down Stairs Lite Motion' At 6PM the first program will run true and turn the downstairs light on and disable the second program from running. At 10PM the first program will turn false and turn the downstairs light off and enable the second program to run when motion is detected. Remember to set this first program to run at startup. Program: Down Stairs Lite Motion If Status 'Devices / Dwn Stairs Lite Motion' is On Then Set 'Devices / Dwn Stairs Lite' On Else Wait 15 min Set 'Devices / Dwn Stairs Lite' Off This second program if enabled will turn on the downstairs light when motion is detected and turn off 15 minutes after the motion sends the off signal.