TJF1960

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

I noticed button C on 1 KPL was not controlling a program. When the button was pressed there was no event viewer trace. The other 5 buttons produced a trace. I factory reset the KPL and restored via ISY. Still no trace on button C. I removed the device via ISY, factory restored the KPL and reinstalled it in ISY. Now pressing button C produces an event trace. I have had this happen in the past, 4 or 5 times, with various KPL's 6 or 8 button devices. Seems like it will occur after adding or changing other devices or heavy linking/relinking sessions (having nothing to do with the failed KPL). Its really not a huge deal, other than having to recreate all the links and programs. But I was wondering why a factory reset and restore doesn't fix the problem? Some sort of corruption in the ISY or PLM? Is there any way to prevent or repair without having to remove and reinstall? Thanks, Tim

Turned out to be a EZEye connected to an EZIO6 Analog input apparently is going bad. As soon as I unplugged the EZIO the flashing went away. Plugged it back in and the flashing started up again. Once I disconnected the EZEye the flashing went away again. Replaced the EZEye and all is good again. I should have opened my email sooner than later. My inbox was flooded with ISY emails created by a program to let me know the threshold changes of the EZEye. Unfortunately I didn’t open up my emails until I had replaced the EZEye. I guess the rapid changes caused by the failing EZEye were too rapid for the ISY to log or to appear on the event log? In fact now that I think about I did look in the program summary tab looking for programs running and last run times to see if a program was causing or reacting to the powerline comm.., but found none. Anyway it is fixed and I just wanted to wrap this thread up. Thanks as always, Tim

I noticed today all my lamplinc and appliancelinc LED's were flashing. They would double flash then wait about a second then double flash, then wait about a second then maybe a single flash then a double flash etc., no real pattern. I looked in the log but there was nothing logged other than normal turning devices on and off. I checked the event viewer and noted a number of logs which may seem to correspond to the flashing which are in Bold below. But there is flashing without any change to the event viewer too, so I am not sure if these events have anything to do with the flashing. Tue 12/28/2010 09:18:32 AM : CLI-WBug: Successfully Processed WBug Response Tue 12/28/2010 09:18:34 AM : [ Time] 09:18:33 0(0) Tue 12/28/2010 09:18:49 AM : [ Time] 09:18:48 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:50 0(0) Tue 12/28/2010 09:18:51 AM : [ Time] 09:18:51 0(0) Tue 12/28/2010 09:18:52 AM : [iNST-SRX ] 02 50 13.F1.E6 11.DD.F9 41 11 01 LTONRR (01) I checked the LED on the PLM and it is not flashing with the lamp/appliancelincs, but it does flash with device activations. Also the LED's on the ISY are not flashing other than when a device is activated as well. Any ideas? Thanks, Tim

Hi Michel, Ok, I will send my spare plm. Hi Rand, Tried your suggestion, still locked up. Thanks to both of you. Tim

Well, no such luck. I waited for an hour and the ISY still had the Pwr, TX and RX LED's stuck on. Was unable to enter the admin console at all. Once I rebooted again all was fine. Next Suggestion? Thanks, Tim

Right on, that will be a lot easier to try. THANK YOU! By the way, when you say "EZRains" you mean EZRain or EZFlora right, and not all of the EZxxx products. Thanks, Tim

Hi Michel, 1) PLM 2412S v3.3 (v.92) 2) Have had malfunction with and without the external power supply (doesn't seem to matter). 3) ISY 99ir pro v2.8.9 4) Yes, 1 EZFlora device with new updates from SHN. No, I haven't tried removing it (didn't know it could cause this problem). Do I have to remove from the ISY (a lot of work to reinstall) or can I simply unplug it? If it matters I have 1 EZIO6 and 1 EZIO2x4 as well. Thanks, Tim

I have had an ongoing problem since I purchased the ISY from SH about 2 years ago that I haven’t been able to rectify. The ISY was an 99i but have since upgraded it to 99ir pro with the addition of the ir module and online pro upgrade and is running v2.8.9. The plm is 2412s v.92 If I remove power from the plm (ISY’s plm) for more than 8-10 seconds then reconnect power there is a good chance that the ISY will freeze up during the boot process (seems like just before it would normally start to query devices). This happens probably 5 out of 10 times. Usually, but not always, if I cycle the power for less than 5 seconds the ISY will boot up properly. There has been no indication of any rhyme or reason to when or how it will freeze up, or why. The freeze up has been worse in the last 6 months than it was at first. When the ISY freezes up the Pwr, TX and RX LED’s are all lit solid. The wiki describes the condition of RX lit solid as a problem with the plm or cable, but it doesn’t describe the TX LED on solid or both RX and TX on solid. I have replaced the plm with my other new spare, no difference. I have also replaced the cable twice with no difference either. I also have added the wall power supply to feed the ISY power but that didn’t help either. The error log doesn't indicate a problem either. At first it seemed it would only occur when unplugging the plm, not when rebooting from the admin console but a couple of days ago it did freeze when I rebooted from the console. It hasn’t been a huge deal but my fear is one day when I am out of town and there is a power interruption……. Any suggestions? Thanks, Tim

Just upgraded, so far all is good. Odd is I was expecting to see v2.8.8 as others reported but the version in about and the backup I just did shows 2.8.9! Thanks UDI Team! Tim

mjtyson, Out of curiosity what was the solution? Thanks, Tim

Ditto. Thanks, Tim

tim2u, I would suggest checking with a couple of WB stations in your area to see how often they update their data. All of the stations in my area only update about once an hour (1 is even longer between updates). Lee, I like that idea of the radio with the output to trigger. Do you have it set up to trigger an IO or EZIO? Was the radio very expensive? Thanks Tim