TJF1960

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)?

Hi Michel, Yes, no problem. I am just really glad that I can powercycle the ISY/PLM and walk away knowing full well that it will reboot fully now! I am going to send it in for repair once you are finished with it, but not in a huge hurry so take all the time you need. Thanks, Tim

Thanks LeeG for the FYI. It actually prompted me to work on the device a little more to figure out exactly why the 1 second transmissions were occurring and why 1 day it seemed the ezeye were causing the problem and the next day it wasn’t. Turns out the broadcast messages must have been coming from input 4 and not the analog inputs as I previously thought. I wired the ezio back into position. It immediately started broadcasting once a second. I removed each input until it stopped broadcasting. It stopped at input 4. I connected everything but input 4 back up and no broadcasts. Hooked up input 4 and broadcasts started again. I unhooked input 4 wires and wired them to input 3. No broadcast. Hooked up the wires from input 3 originally to input 4 and it started broadcasting. Turns out that any of the inputs connected to input 4 cause it to broadcast. I checked all the inputs with a dmm, all but input 4 measured the same (5mv or so). Input 4 measurement kept varying and when the LED would blink the dmm measured over 1 volt. On the bench I connected a dmm set to resistance and measured input 1. The minute the probes hit the input terminals the device broadcast once. Removed the probes and it broadcast once more. Reversed the probes and reconnected and did not get a broadcast (which makes sense). Same results on inputs 2 and 3. Input 4 would broadcast with the probes in either position (forward or reversed) and as long as the probes were connected to input 4 it resumed its broadcast every second. After removing the probes it would take 10 or so seconds for it to stop broadcasting. I haven’t yet figured out why the other day I was able to unplug it from the utility closet and walk out to my workroom and plug it in and it continued to broadcast every second or so and not today but at least I can send it to SHN with an accurate description of the problem and have some faith that they will be able to reproduce it and fix it. Thanks as always, Tim

Hi Lee, I agree, that is what it seemed like. I was using the analog output of the EZEye’s connected to the analog 1 and 2 respectively of the EZIO6. Analog 1 trip point was 265/250 and 15/0 for analog 2. I did have some trouble in the beginning with closer set points as the ambient light levels would vary which would produce multiple night/day trips. Once I set them to the above figures I would only get 1 or 2 false trips on analog 2. I wired a 47k ohm resistor in series with the analog input with a 47mfd cap from ground to analog 1 input to help slow down the input. Worked great for 6 or 8 months then this problem started. One of the last things I did with the EZIO6 was factory reset it then linked it back into the ISY. The problem started again. At that point I used SHN utility suite and turned off the analog inputs and wired them to ground. The problem continued. The interesting thing is these last couple of days there was no log of any of the communication from the EZIO in SHN utility or the ISY event viewer. So I don’t know if it was just sending out random noise or actual data. These EZEye’s are now wired to a EZIO2x4 same configuration as before and is working flawlessly. Thanks, Tim

Looks like an EZIO6 I recently was having problems with may have been the cause of, or at least contributed to this problem. Since removing the ez I have not had one single lock up after rebooting. Pretty strange right. I cant explain it but am happy with the outcome. Thanks Tim

Well, the next day the phantom blinking on all AL and LL returned. This time they were blinking at a rate of about 1 per second, continuously! Put the old EZEye back in and the problem cleared up. Later that day the phantom returned. The long and short of it: The EZIO6 is defective/intermittent. Even when I turned off the analog inputs via SHN utility suite the powerline transmission continued. Factory reset it and restored, same problem. Once it was removed from the system all was fine. I wired up the EZEyes to a EZIO2x4 and everything for over a day has been working great. Tim

Thank Lee, If it happens again I will try creating a scene then removing it. If that doesn't work I will try restoring the plm. Both will be a lot easier that all the relinking and fixing all of the programs. Thanks again, Tim