TJF1960

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

Hello oskrypuch, It should trigger. The only problem I see may be (depending on the programs it is calling) that everytime weatherbug updates status, it will cause the program(s) to re-evaluate. Tim

Hello detrotdr, I would think changing status to control would do the trick. If Control 'ControlLincA-5' is Switched OFF Or Control 'ControlLincB-5' is Switched OFF Then set 'Master Light' OFF Else No Action Tim

I like it! In fact early on in the thread I was going to suggest it was a ghost or poltergeist but you beat me to it. Or how about “the poltergeist effect.†I wonder if this switch were a controller of a scene if the scene would turn on. I guess that it probably would. I guess at this point anything and everything you do and try will be a step forward in figuring this all out.

Illusion, I was just going to ask if the new switch was "Replaced" via the ISY or if it was "built from scratch." Since the problem followed thru to the new device this does seem to be a logical next step. Although if that fixes it the root cause may never be known. Lee, I was wondering if all of the reported cases were using 2412S plm's? I too am following this with fascination! Thanks, Tim

I believe you can delete the stop and change "Run Program 'Kitchen Timer' (If)" to "Run Program 'Kitchen Timer' (Then)." I also believe you do need 2 programs because of the "And Status 'Lighting / Kitchen:Light' is Off." If it were all in one program once the program turned the light on the status would change and the program would turn false thus killing the wait. So the light would not get turned off. Great job on programming! Tim

Hi Michel, I have sent a request to the developers of AtHome. When a socket is opened, what is the timeout period until the error message? Does the ISY then close the opened socket when the error message is logged? Are all sockets in a closed state after rebooting the ISY or does it retain memory from pre reboot status? Thanks, Tim

Hi Michel, Thank you for asking me to make sure the iPad/iPods were off. I remember turning them off but when I checked the iPod was indeed just asleep (I had forgotten my wife had borrowed it and must have left it on). I turned it off and since then I haven't had any -170001 errors like before. I did leave DSCLink running just to see if the errors continued after I turned the iPod off. All has been fine. So my next question is how do I fix it, short of turning it off all of the time? If the iPod is sleeping why is it affecting the ISY 2 to 3 times a day which in most cases requires me to reboot the ISY? Thanks, Tim

No problem, I will let you know. Thanks, Tim

Hi Michel, Am using AtHome with iPad and iPod but both are powered off completely. Also am using DSCLink on a dedicated desktop only used for that program, with XP. Thanks, Tim

Hi Michel, When I get the error -17001 it is usually in groups and can last until I have to reboot the ISY. For instance last night at 5:27:09 PM and lasted until I rebooted at 6:07:42 PM The interesting thing is that for the most part the times recorded in the error log all end in multiples of 10 seconds. for instances 5:27:09 next is 5:27:19 then 29 then maybe 59 etc. Here is a shortened list of the error log: 2011/01/12 05:00:38 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:00:47 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:11:38 PM System -140005 CLI-WBug Wed 2011/01/12 05:27:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:27:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:27:59 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:09 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:19 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:29 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:39 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:39 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:28:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:49 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:49 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:28:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:28:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:28:59 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:28:59 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:09 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:09 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:19 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:19 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:29 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:29 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:39 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:39 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:49 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:49 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:29:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:29:59 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:29:59 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:09 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:09 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:09 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:19 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:19 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:19 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:29 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:29 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:29 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:39 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:39 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:39 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:49 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:49 PM System -170001 [uDSockets] 27 active/error 6 Wed 2011/01/12 05:30:49 PM System -170001 [uDSockets] 33 active/error 6 Wed 2011/01/12 05:30:59 PM System -170001 [uDSockets] 26 active/error 6 Wed 2011/01/12 05:30:59 PM System -170001 [uDSockets] 27 active/error 6 Wed Again, this is just a short snippet of the error log, it continues this way until I reboot it During this period programs don't run. At least not that I could tell. Lights that should have turned on or off by programs didn't. However Insteon communication was fine as the motion sensors still turned lights on and off. Also during this period I am unable to log into the admin console. I have tried to log in via the desktop icon and thru the web. So I physically have to go to the ISY and power cycle it. I need to get this fixed. It is occurring at least twice a day now and always requires power cycling the ISY. What am I looking for? I am assuming this is something on my network that is communicating with the ISY? At first I thought perhaps it was my computer which had the admin console open but last nights problem occurred when all of my computers were off so there were no open admin consoles. Any suggestions would be greatly appreciated. Thanks, Tim

What exactly does this error mean? It is not listed in the wiki and a search of the forum didn't provide any explainations other than some sort of network problem. Thu 2011/01/06 05:39:42 PM System -170001 [uDSockets] 33 active/error 6 I had about a half hour worth yesterday during which time the ISY seemed sluggish. After reboot it seemed ok. I had another of the same error at about the time of the nightly query all program running. I do have athome on an ipad and ipod but both have been asleep for days. And I am using DSCLink which has been working great for almost a week now. Also I have noticed since upgrading to 2.8.10 that a few notifications are not sent per day. I typically receive about 5 emails from the ISY a day. Since the upgrade I will usually miss 1 or 2 emails and its never the same ones that are missing. Not sure if this could be related or not. 2.8.10 with a static ip. Thanks, Tim

I didn't get the memo if they did. But then they replaced all of mine because of the lack of low battery alert to the ISY. Tim

Right on! Glad you got it going.

Newer versions will automatically fix the programs so you don't have to use find/fix and newer version will reboot automatically when everything is completed.

What model is your ISY? What version does it report in the admin console (admin console>Help>about)?