LeeG

That is the correct way to code the Adjust Scene statement. Was the Program functional at 11 PM? The Then clause can be tested by clicking on the Program name and selecting Run Then. What type of switch is it and what is its firmware level?

It changes the static attributes which will remain until changed. It does not affect what the Program will accomplish at 11 PM and 5 AM. The Program will change the Local On Level of the switch if the Adjust Scene statement is coded correctly.

The UDI Wiki has some excellent material on Programs and Programming. The following is an excerpt from the Wiki… The 'Run program' command causes the specified program to begin execution. The target program's state will become True or False as the program's Then or Else clause is executed. All normal conditions and restrictions apply; i.e. the target program will begin execution regardless of the state of its Enabled checkbox, and the target program will not begin execution if it resides within a folder tree any of whose folder's conditions are false.

Program 1 calls Program 2 to close the door. Program 2 being Disabled does not stop that. Program 2 being Disabled only stops it from being triggered independently by a change in Sensor status. A Disabled Program can still be called by another Program. Program 1 will still call Program 2 every hour even with Program 2 Disabled.

Igdixon Post your Program. Right click on Program name and select Copy to clipboard. That way you can paste the actual Program. It sounds like the Scene name rather than the switch name was used in the Adjust Scene statement. Also, was the Program complete Changes Saved and Enabled at 11 PM. Otherwise it would not have changed to 50%. Check Programs | Summary tab. Does the Program Last Run TIme show it ran at 11 PM and is the Status True. If it is past 5 AM at your location it will now show Last Run Time of 5 AM with a Status of False.

Michel I don't think it is LED Brightness per see. The event trace shows 3.1.17 uses I2 extended commands to update the configuration. 3.2.0 uses I1 Peek/Poke for the same configuration change for the same device. Does look like something checking if I2CS might have resulted in using I1 when not I2CS rather than use I2 if not I2CS. Just a guess.

Skripo That works on 3.1.17. Does not work on 3.2.0. Don't know about 3.2.1 yet.

Martinefski This topic has an example of the Programs that are needed to cycle the FanLinc through the 4 settings with a single KPL button. viewtopic.php?f=27&t=8334&hilit=fanlinc

Disable the second Program. It will still close if the door happens to be opened on the hour but Program 2 will not trigger on its own when it is Disabled. EDIT: actually depending on how close to the hour the door is commanded to open, Program 2 driven on the hour could stop the door movement in the middle of the open movement. Most openers will stop door movement as a safety feature if a second button press is done while the door is moving.

Regarding the Fan speed, the Responder On Level of the Fan indicates speed. Move the Scene On Level slider to the Fan speed (Off, Low Med High) desired for the Scene..

I don't know why a Program would not run. Just ran this simple Program with the Run At Startup option. The SwitchLinc was turned On during reboot. The Last Run Time matches the reboot time and Status is True. Perhaps there is something associated with a true power outage that affects the results. If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'SwitchLinc Dimmer' On Else - No Actions - (To add one, press 'Action')

I can turn mechanical switches off before leaving a residence that has lost power. I cannot turn Insteon devices Off. Perhaps it had nothing to do with safety. Perhaps it was just simpler, cheaper.

Brian I think I was repeating what you had already posted either here or another OP. Don't know if applies to all devices but did that change not start some time ago. I assumed it had to do with safety, not returning a circuit to powered after a power drop.

That is correct. A Schedule From/To causes the Program to trigger at the From time and the To time. The clause that runs is determined by the True/False of the If conditions. If that is not what is needed put the Else logic in another Program in the Then clause with positive (True) is conditioning.

Insteon devices no longer return to state before power drop. Just about all the new devices I have read the User Guide for now return to an Off state after a power drop. The Start2 Program ran after reboot without the Run At Startup option. I believe this is the ISY attempt to catch up on things that should have run since midnight but may not have because of the power outage. The Program with the Sunset trigger would not run the Then clause because Sunset had not yet occurred when power came back. EDIT: As Brian mentioned in an earlier post the Configuration option "Catchup schedules at Restart" can be turned Off which will stop the Programs from running again at reboot.

"what i want to accomplish is if mike or kristas keypad g is pressed between sunset and 10:30pm i want the all off night program to run. if mike or kristas keypad g is pressed any other time i want the all off day program to run." That is what I would expect to happen. Is that not what is happening?

The Else will run at 10 PM and when either of the two KPL buttons are pressed On and not within the time range. If that is not the desired result put the Else Action statement in another Program that triggers specifically at 10 PM.

I made an arbitrary choice of 10 hours for this to run. Adjust as needed. Also assumed the I/O Linc Sensor is On when door is open. Adjust as needed. Also assumed the I/O Linc Relay is operating in one of the Momentary modes which is normal for a garage application. Program CloseGarage1 If From Sunset For 10 hours Then Repeat Every 1 hour Run Program 'CloseGarage2' (If) Else - No Actions - (To add one, press 'Action') Program CloseGarage2 If Status 'IO Linc1-Sensor' is On Then Set 'IO Linc1-Sensor / IO Linc1-Relay' On Else - No Actions - (To add one, press 'Action')

Yes that can be done. Define an ISY Scene with the bathroom switch as a Controller. Use the Adjust Scene Action statement with the switch name in both parameters. Set the On Level to whatever is desired in a particular time range. If From 11:00:00PM To 5:00:00AM (next day) Then In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 50% (On Level) Else In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 100% (On Level) The Adjust Scene statement is changing the On Level (applied locally) value in the switch. This value controls what happens at the switch when the local paddle is pressed. At 11 PM the Program triggers True setting the On Level to 50%. At 5 AM the Program triggers False and sets the On Level to 100%.

The SwitchLinc event trace shows an I1 Peek/Poke sequence is being used for LED Brightness as well. Actually that is probably good news. Looks like a common glitch that will be resolved with a single fix.

TJF1960 Thanks again for traces. I see the same result on 3.2.0, a v.36 KPL is using I1 Peek/Poke. And my Advanced Options is set to Automatic.

That is very odd. 3.1.17 is using the more advanced I2 method for setting the configuration. For some reason 3.2.0 is using the old I1 Peek/Poke method. Not surprising it is not working. Is this the same configuration, just different ISY images? Is the KeypadLinc firmware level displayed at 3.2.0. (not v.00)? Does the Link Management | Advanced Optoions show Automatic at 3.2.0?

TJF1960 Thanks for that info. I had a recollection of doing it in the past but tried on 3.2.0. When it did not work I assumed bad memory. Looks like something for UDI to look into. Did you run an event trace to compare what 3.1.17 is doing versus 3.2.0

Put each RemoteLinc into linking mode (Dim/Bright buttons at the same time) but only ONE at a time. Right click and select Write Updates to Device. That should clear any pending activity.

There is method of putting the OFF button in something like a non-toggle Off mode. The OFF button is not illuminated when the KeypadLinc is Off. It is a KeypadLinc Set button sequence that I think is described in the KeypadLinc User Guide. If not there the Smarthome forum should have posts that describe the sequence as this question does come up. Don't think that special OFF not illuminated mode can be defined with the ISY.