TJF1960

jca001, I am old school with programs and haven’t done much with variables. As such I have been trying to figure out a program using variables to accomplish the same results as the 3 program examples above (Reboot Away KPL Off, Reboot Away KPL On and Reboot Away KPL Status). It seems to me, at least as far as I can see, it would still require 3 programs + variable. But I do not have the experience with variables as some of you do. I know it would be asking a lot but could you provide example programs and variables to demonstrate how you would replace the 3 programs mentioned? Thanks, Tim

After power is restored to the ISY what is the boot sequence (including Run at Startup commands) and now that variables have been introduced where exactly do they fall in the sequence? Thanks, Tim

aLF, Yes, set the program to “Run at Startup†Yes except, if I followed your original post correctly, you would want to turn the away scene "off" at start up (in your example above). The only problem is if you were home and the power cycled off-on the ISY would still turn the scene Away off even though you are home. If you want the ISY to remember the state of your Away program and scene after a reboot I would suggest the following: Program: Reboot Away KPL Status If Status 'KPL Button' is not On Or Status 'APL ' is not On Then Set Program 'Reboot Away KPL Off Set' To Run At Startup Set Program 'Reboot Away KPL On Set' To Not Run At Startup Else Set Program 'Reboot Away KPL On Set' To Run At Startup Set Program 'Reboot Away KPL Off Set' To Not Run At Startup Program: Reboot Away KPL Off Set If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'KPL Button and APL' Off Else - No Actions - (To add one, press 'Action') Program: Reboot Away KPL On Set If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'KPL Button and APL' On Else - No Actions - (To add one, press 'Action') I use these programs for my own Away programs, only I turn "On" the KPL buttons to indicate I am Away, and turn them "Off" when I am home. So I had to reverse the logic in these examples (hope I got them correct). Program: Reboot Email If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Program 'Reboot Email' To Run At Startup Wait 15 seconds Send Notification to 'Tim' Wait 1 minute Run Program 'Reboot Email' (Else Path) Else - No Actions - (To add one, press 'Action') This is the program I use to send notification of a reboot. Remember to initially set this program to "run at reboot." Tim

aLF, This might be what you need to restore the kpl button after a power failure. From the wiki: Darrell Peters wrote this set of programs to 'memorize' the state of a keypad button and restore it after a power loss. http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Programs_as_Variables:_ISY_Restores_KPL_State_After_Power_Loss Tim

That is a very good idea. Thanks for the suggestion kingwr. Looks like I have some studying to do!

It has been a while for this thread and I was wondering if anyone has taken the rfid or Bluetooth ideas any further and have actually integrated one or the other into their systems? Thanks, Tim

You are welcome, and I hope it works too or at least helps in figuring out what is going on. I should mention that I have 4 programs which email me everyday. Every once in a while one of the program notifications seems to get lost. Its not always the same one either, it could happen to anyone of the 4. And it doesn’t happen all the time, maybe once a week. I haven’t figured out why yet but I do know the programs executed fully. What concerned me with your situation was that you indicated it would work for maybe 2 days then stop completely. Please post back the results. Thanks, Tim

Yes, that looks right. Sorry, I wrote the example on the fly.

You may very well be right. The program itself may not be the issue. And I agree the from/to time isn’t needed, neither is the run Else. However I like to finish off my programs to false when they are not running. Makes skimming thru the summary looking for running programs easier. Plus by adding a wait (of say 10 seconds) after the notification, then running the Else on the program itself will let you know that the program did run in its entirety. Take the OP’s runtime of 7AM. If my suggested program runs completely the summary tab runtime/last Finish time will show 7:00:10 AM which will confirm that the program started at 7AM and ended 10 seconds later. If the OP didn’t receive an email he could look at the summary tab to verify the program executed completely at which point he could focus his attention elsewhere. Whereas your suggested program would list the last runtime/last finished time as 7AM but that wouldn’t guarantee the program ran completely, just that it evaluated – big difference.

I cannot answer why the notifications stop after a couple of days but perhaps changing the program to the following would help. If 7:00:00AM And Folder 'AWAY' is True Then Send Notification to 'ME' Run Else Else - No Actions - (To add one, press 'Action') At 7AM when the folder away is true the program will run and send notification 1 time after which the program will turn false until the next day. If you wanted to take it a step further you could add a wait between Send Notification to Me and Run Else. The benefit would be when you do not receive the notification you would be able to check in to the Summary tab and see the Last Run time to verify. If you use a 10 second wait then you will see 7:00:10 AM as the last run and last finish times which tells you that the ISY ran the program completely.

I don't know that I can explain what causes it, it but I do have one battery charger on an appliancelinc that would do the same exact thing. My battery charger is electronic not a transformer, and your LV light power supply is probably electronic as well. More than likely it is some sort of voltage spike created by turning the power off to the power supply which locks up the appliancelinc. I found by installing a filter (X10 filter part number XPPF available on ebay pretty cheap) between the power supply and the appliancelinc, the problem went away. Tim

I agree with LeeG and Brian H. I also keep a couple of devices on hand for expanding my system and in the past have replaced older version with newer versions without any issues. Currently the only duplicate modules I keep for replacements are the plm and an ezflora as those are the two most important devices in my system. Tim

As I understood it, the v35 issue was only with Switchlinc relay (possibly some SL dimmers also?) but not with KPL's, can anyone confirm?

What is the timeout set for on the MS?

Good Catch fitzpatri8! I had just remembered reading that a long time ago and came back to post but you beat me to it! Tim

So it sounds like Program 1 is working fine and setting the on level and ramp rate of the SL properly depending on the time of day. It looks like something is wrong with either Program 2 or the scene settings of "Early AM MB Can Lights." Can you select the Early AM MB Can Lights scene (not the SL under the scene but the scene itself) in the devices / scene column in main admin console window. Verify the scene is set to 75% @ 9 minute ramp rate then press the On button at the bottom of the admin console to turn the scene on. The lights should slowly ramp up to 75%. If that works then turn the lights off and go back to the program summary tab and select Program 2, right click and select Run Then. The lights should ramp up to 75% over 9 minutes. Tim

Hi Avonlea22, I agree with LeeG, I think what Michel was referring to is to create a program which during 3-5am the program sets the local on rate to 35% @ .1second ramp, any other time outside of the 3-5am window the local on is set to 75% @ .3second ramp. The following is based upon my assumption that the lights you want to control are the load connected to the SL you are turning on and off locally. Also the following suggestions are pretty much put together from suggestions by Rand, fitzpatri8 and Michel early on in the thread. I have just tried to put it all together in one, hopefully, easy to read post. It seems to me using Michel's suggested program will satisfy the first part of your requirements. Create Program 1. Select the name of your SL for both “In Scene†and for “Set†and set the On Level and Ramp Rate.This first program will change the On level and Ramp rate of that scene (the local On of the SL) depending on the time of the day. Program 1 If On Mon, Tue, Wed, Thu, Fri From 3:00:00AM To 5:00:00AM (same day) Then In Scene ‘Your SwitchLinc’ Set 'Your SwitchLinc’ 35% (On Level) In Scene ‘Your SwitchLinc’ Set 'Your SwitchLinc’ 0.1 Sec (Ramp Rate) Else In Scene ‘Your SwitchLinc’ Set 'Your SwitchLinc’ 75% (On Level) In Scene ‘Your SwitchLinc’ Set 'Your SwitchLinc’ 0.3 Sec (Ramp Rate) Next create a scene with your SL as the controller (I think you have one called “Early Morning MB Lightsâ€) and set the scene On Level of that scene to 75% with a Ramp Rate of 9 minutes. Next create a 2nd program: Program 2 If On Mon, Tue, Wed, Thu, Fri From 3:00:00AM To 5:00:00AM (same day) And Control 'Master Bath Can Lights' is switched On And Control 'Master Bath Can Lights' is not switched Off Then Wait 1 second Set Scene 'Early Morning MB Lights' On Else - No Actions - (To add one, press 'Action') This program, between 3-5 am and when the SL is turned on, will activate the scene “Early Morning MB Lights†which will increase the lights from the 35% they are already on at to 75% over 9 minutes. Pressing the SL Off button (locally) will naturally turn the lights off (either at .1 or .3 seconds depending upon the time). If I have missed anything please let me know. Tim

Illusion, thanks for posting. Had you not posted I probably would have blown these events off and not looked any further. I had a similar thing happen this morning. My sprinklers didn't run. When I looked into the admin console>program summary many of the Last Run Time and Last Finished Time slots were not populated (much like I see after a reboot). I know for a fact quite a few of those programs did run yesterday and those time slots should have been populated. In fact I looked thru the logs this morning looking for a series of queries thinking perhaps we might have had a brief power outage sometime in the night which would have rebooted the ISY, but the only queries were the scheduled program run at 1:15AM. Edit: I just checked for the oldest last run time in the program summary and it was at 4:28 AM today, it has been at least 2 days since I have rebooted the ISY and some programs had been run yesterday that haven't run today yet. The plot thickens. The log shows no activity after the 1:15AM query until 4:08 AM this morning. My wife got up around 3:45 AM to let the dogs out at which time she turned a couple of KPL and SL lights on then off when she came back to bed. She said she got back up a little after 4 which would seem to correlate with the 4:08 logging. But there wasn’t any log activity before that. When I checked the time in the admin console this morning is was at the correct time. Also, I didn’t realize until after I posted that this is the 2.8.16 section, I am on 3.1.0 Thanks, Tim

Hey Illusion, Your ghost came to my house over the weekend! Well, kind of. I was wrapping up some things with programming and scenes and was in the midst of testing when the vent fan over my workbench turned on all by itself. I also noticed that the SL controllers and KPL buttons which were included in this new scene were randomly turning on then off a couple of times. This happened more times than not when activating the new scene, and was not part of the scene for the vent fan. I was in a bit of a hurry and didn’t think to fire up the event viewer. I have a program that monitors the devices in that scene and if the conditions are not right and the scene is manually turned on the program will immediately turn that scene off. If I disabled that program and activated the scene or ran the scene test everything was fine, as soon as the program was enabled and the scene was activated the malfunctions occurred. I figured what was happening was that when the scene was manually turned on, all controllers and responders of the scene turned on. Then 1 second later the program sent the scene Off command and all of the controllers and responders turned off but enough time hadn’t expired from when the scene On command was sent that when the devices reported they were off the scene on command was re-applied. I really never did figure out exactly why the vent fan turned on during this process (I kick myself for not starting the event viewer). I assumed I guess that with the data collisions occurring that the vent switch thought it received an On command or a scene On command. The fix was a 3 second wait before sending the scene Off command, which gave the scene On command enough time to finish its operation. In the last couple of days I have tried to duplicate the problem but haven’t been able to. I am not sure if it is because I had removed a couple of devices from that scene or what. So, the long of it is that this experience led me to wonder if a similar situation might be occurring in your system, where the motion sends the on or off command and there is for whatever reason some sort of data collision occurring and the resulting data is received by the bathroom SL. I don’t know why it would report as a local on though. But, also, keeping in mind that you have replaced the switch with a new one, and the old one is still in the system but just for monitoring purposes and has yet to ghost on, that the only real common denominator is the scene or scenes the SL is in. Out of curiosity how many scenes is the SL in and how many devices are in each of the scenes? Thanks, Tim

Same here.

It doesn't seem to me that with the addition of that last condition that the program will ever turn false, unless forced. Also,just to make sure, in the original program is the parenthesis an And or an Or statement? Tim

In Program Summary tab, what does ISY report the status of those three programs as? In the Configuration>Climate tab what is the current Rain Rate amount? And, did you want Rain Rate or Rain Today? In your original example you used Rain Today. I would look at the conditions in the first program. When you force the flag false, the first program must be turning true and running which in turn turns the flag true. Watch the run times in Program Summary tab for those 3 programs and run Else on the flag. Tim

Well, I believe the Rain Today program would turn false once the clock strikes 11:54PM and stay false until 12:10AM and WB reports rain today > 0". But now that I am thinking about it more though... I think that if WB reports rain today > 0" while the time is in the off period (11:54PM - 12:09:59AM) the two programs will cycle back and forth against each other. So it looks like 3 programs will be needed. Program Rain Today: If From 12:10:00AM For 23 hours 45 minutes and 59 seconds And Module 'Climate' Rain Today > 0 " And Program 'Rain Email Flag' is False Then Run Program 'Rain Email Flag' (Then Path) Else - No Actions - (To add one, press 'Action') Rain None Today: If From 12:10:00AM For 23 hours 45 minutes and 59 seconds And Module 'Climate' Rain Today is 0 " And Program 'Rain Email Flag' is True Then Run Program 'Rain Email Flag' (Else Path) Else - No Actions - (To add one, press 'Action') Program Rain Email Flag: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send Notification to 'Email' content 'default' Else - No Actions - (To add one, press 'Action') Tim

Hi smileyw, The trouble is every time WB updates status and rain today is > 0" your program turns true and runs. Having the Stop Program at the end doesn’t really do any good for future program runs. At first I was thinking you would need 3 programs, but I think these 2 might do the trick. Program Rain Today: If From 12:10:00AM For 23 hours 45 minutes and 59 seconds And Module 'Climate' Rain Today > 0 " And Program 'Rain Email Flag' is False Then Run Program 'Rain Email Flag' (Then Path) Else Run Program 'Rain Email Flag' (Else Path) Program Rain Email Flag: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send Notification to 'Email' content 'default' Else - No Actions - (To add one, press 'Action') Once the WB reports Rain Today > 0†then the program Rain Today will turn true (as long as it is within the time frame and Rain Email Flag is false). At which time Rain Today program will run Rain Email Flag program which will then email you. Once the flag program is turned true it will stay true until the program Rain Today turns false (or the ISY is rebooted). Then the process can start all over again the next day. This should work, but I haven’t tried it out so – use with caution . Tim

Hello oskrypuch, You need to wire the analog inputs AN1 and AN2 to the ground terminal of the ezio until they are being used. Connecting AN1 and AN2 to ground will turn on the nodes. If you would prefer them to report as off all of the time here is the SHN wiki page showing how to calculate resistance selections http://wiki.simplehomenet.com/index.php?title=Analog_as_digital Tim