Thom

Michel, one more thing about the two devices that show status ON after the all off. They are not actually on. It is only the status indication that has changed, and a log entry has been written. I believe that this is conclusive proof that it is not a program that is doing this. A program would actually turn the devices on. I assure you that I did not physically turn the two devices on. And, if I had done that, they would be on. I did not turn on the scene that contains these two devices. So I think we can eliminate all 3 ways you mention. And by the way, all three of those ways would have actually turned the devices on. But they were really off. Only the status reported on. Given the specific repeatable nature of this problem, it does not surprise me that you cannot repeat it. Something is broken here. I would like to determine if it is the ISY or the PLM. I am interested in this problem because there are so many flakey things going on on my system, I really want to attack and correct repeatable problems. To that end, I did a hard reset on the PLM and then restored it. The problem persists.

In the administrative console, when I do All On followed by All Off directed at My Lighting, two devices initially show a status of off, and then after a couple of seconds later show a status of on. For these two devices, the log shows the status of on after the web initiated fast on then a status of off after the web initiated fast off and then the status of on for each of the two devices for no apparent reason. Before the final On status events, there are only the predicted status events for all the devices. There are no scheduler events. When I communicated with you via email, you suggested: "there MUST be a program that turns on/off a "scene" that those two devices belong to ... a trigger based on some other device" The two devices are in two scenes. The first scene contains only those two devices. Both are controllers, they replace two 3-way switches. Neither the devices nor the scene are in ANY programs at all. The second scene contains these two devices and several other devices. The two devices are only responders for this scene. This scene is not in ANY program. Other devices in this scene are in other scenes that have time scheduled programs only. No triggers other than time. The only programs in my ISY that are based on device triggers are for bathroom and closet lights to turn them off after 15 minutes. None of those devices is in either of the two scenes that contain the two devices that report the erroneous On status. Neither of the two scenes containing the two devices nor the two devices has ever been in a program. I am finding the analysis of a program causing the On status events difficult to understand. If there is such a program, how did it accomplish this feat without a report in the log? If this is a program doing the deed, how might I find it?

Thanks again Mike, I already have one Access point on the PLM. I had a good talk with Steve Lee this morning. My house and equipment were specifically designed to interfere with Insteon signals. I have UPSes and Monster power strips on all my electronics, and I have a lot of computers and electronic equipment. Those act as sinks for the Insteon signals. Steve describes them as black holes sucking up the signals. I have a large numbers of low voltage lights. Any one of those transformers could generate a lot of noise. I have a bunch of fluorescent fixtures. Any one of the ballasts could be interfering. I have two whole house electrostatic air cleaners that could be injecting noise. The house would have been a disaster for X10. It is a testimony to Insteon that it is working as well as it is. I have ordered a pile of filterlincs. I am going to hope that the electronics are what is pushing the system over the edge. That is the easiest to fix. After that, it is a matter of shutting down parts of the house and seeing if reliability changes. Installing the noise filters would be more of a pain. Thom

I have 4 access points right now on different phases of different panels. I am considering adding a couple of receptacles right where the service comes into the house. I think that two of the access points right there would have the most effect. I have been talking to another user who had a similar set of problems. He believes that I am having noise issues and recommends some filterlincs and Leviton Noise filters. That makes sense, I did a couple of experiments. It seems that turning on an LED TV increase the failure rate. I went from the rare case of zero failures on a my lighting query to 4 or 5 when my wife cranked up the TV and some other electronics. I may have found the clue.

I have 57 devices installed, a combination of switchlincs, kepadlincs, lampLincs and applianceLincs. The house is new. There is a main circuit panel on the outside of the house that feeds 4 panels inside the house. One of the panels has nothing but AC equipment another has another AC plus a few new circuits with switchlincs that I just installed.. I have 4 access points, and I believe that I have them on each phase of the main two panels inside the house. Most of my automation works most of the time. But whenever the ISY boots or when I do a query of My Lighting. I get communication failures. A few circuits fail more than other, but if I query twice in a row, I am likely to get different results. When a device fails to communicate, I can usually turn it on and off several times from the admin console and get it communicating (for a while). I tried moving the ISY to a different location in the house on a different circuit. No difference. Moving the access points around has improved reliability some what.. I am down from 4 or 5 devices failing to communicate on a query of My Lighting to 1 or 2. When I do a query on my lighting, and I get a communication failure, I can go to that device and query it individually and it will work. Right now I have a lamplinc in my bathroom that is turned on by a timer. It always turns on correctly, but often appears as a communication failure. It always responds correctly to an individual query. I have some devices that appear to be working, but I cannot add them to a scene. I get a failure report. Often, if I wait, the device will go into the scene without a problem. Today, I attempted to swap a switchlinc and a keypadlinc. I could wire in the switchlinc, and it would work. I could then wire in the keypadlinc, and it was not recognized by the ISY, either linking or add a new device. So, it seems that whatever I do, it is a crap shoot. It may work, and it may not.