Illusion

The original switch that displayed this problem has been factory reset and has been powered up for months without an errant ghost on. It is not connected to a load however.

Bathroom vanity ghosted on again today. So, completely deleting it and adding it back in did not fix the issue. I am out of ideas. I have 162 nodes in my Insteon install and this is the only one with this issue. Down right baffling.

Posting mostly for record keeping here. Over the last several months the switch has continued to ghost on. The original switch that was replaced and is in system as a test has never ghosted on. Today, 2-28-2011, I upgraded to 2.8.16 and removed the vanity switch from the ISY. I then factory reset it and added it back to the ISY. I then put it in all the scenes and programs in the ISY manually, just like it was a new device. I do have programs that watch this switch at all times and I will report back here if it ever ghosts on again. Fingers crossed. If this does not work... I am all out of ideas after this.

very cool. creative. makes me what to come up with an application for this myself.

Bathroom vanity ghosted on again last night in response to motion event. Test switch did not react. When I get some time next month I am going to do the rebuild from scratch. Before I do this, is there any info I can pull from the switch's database that could be helpful in troubleshooting this. The link table looks fine to me but I am not a link table expert.

That sound like conflicting programs to me. In my case, the device does not turn on and off. That function has always been reliable. Only the load active light demand indicator was erroneously flashing on and off. The load was off the whole time. Next time you see it happening, disable all programs, or just unplug the PLM and see if it continues.

(see 3f above)?

“the poltergeist effect†I like it, but not for the event, for the overarching cause, as in: Due to the poltergeist effect, my device again ghosted on. This way we get to use both terms...

Tim, I have not wiped the switch just yet. I do find it interesting that the original problem switch has not "Ghosted On" since the factory reset. I will wait till I am really frustrated before I rebuild the bathroom vanity switch from scratch. But at this point I am not sure what I am waiting for. I have no idea how to proceed from here otherwise. I do not know what additional data I could provide to help find the root cause of something that cannot happen in theory. What do you think of my new term "Ghosted On?" Any other ideas for a cool name for this event?

Yeah, I have a couple of v.2D KPLs. So you have seen a device cause another device to report that it has physically been turned on before? My issue is not a mysterious turning on issue, it is that the problem device is reporting that it has been physically switched on locally.

Added data point: I installed a new switch during this test some time ago. The switch I removed was factory reset and installed in my home with no load. It was then added to only the ISY and programs were built to watch this switch as well. It is called 'Test Switch' Today the problem event occurred again. The bathroom vanity "was turned on". The test switch did not react. Sorry Lee, no event trace. I think my next step is to remove the bathroom vanity switch from the ISY, factory reset it, and then add it back in not restoring it, but building it from scratch. Maybe there is something getting programed in there somehow. The previous problem switch that now sits just for monitoring purposes has never "been turned on" by a ghost.

I just learned about a method that would have change my PLM replacement experience. See: http://forum.universal-devices.com/view ... 2253#42253 This methodology would have made my experience much less time consuming and painful. So much so, that I would recommend that if you own a non-pro ISY unit you should upgrade to the Pro line before changing the PLM. This is assuming you have a lot of battery powered devices that is. If you do not have many devices that require "waking up" I am not sure the upgrade is necessary. But if you have lots of devices that require being put into programming mode I would highly recommend using the method listed in the mentioned post after upgrading to the Pro line of ISY with Batch Mode for writing updates to devices.

Lee, The first instance of this for me that started this post reinforces your summary of the pattern. While not an event trace I am able to tell from the original log that the same sequence of events preceded the original failure. I would like to add that the motion detector that may have tripped the first failure in the switch was not the same as the one for which I sent you an event trace. Based on the 3 lights that turned on outside just before the bathroom vanity turned itself on I can tell that that was a motion detector in my front yard. It was dark out and the ISY triggerd my front flood lighting scene in response to the motion event. The event trace I posted was from a motion detector in my back yard, during the day, where the ISY did not subsequently trigger any scene due to time of day.

Lee. Here is a level 3 event trace from each of my Motion Detectors in succession. PLM is Version v.92 Pulled switch and replacement switch are both v.27 Switchlinc Dimmers All MDs are REV 1.1 I have added the pulled switch back into my system without a load. I Factory Reset it and the only link it should have is to the PLM I had this pulled switch in system for a long time without any issues. While this issue only surfaced after the new PLM was put in the system, I am not understanding how it could possibly be caused by the PLM. To me as a lay person, it seems the first hint of the switch in the event trace is the report from the switch to the PLM saying it has been turned on, and I know for a fact the light in the bathroom is indeed really on as a result of this. Fri 12/17/2010 02:28:55 PM : [iNST-SRX ] 02 50 0A.3C.31 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:28:55 PM : [standard-Group][0A.3C.31-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:28:55 PM : [ A 3C 31 1] DON 1 Fri 12/17/2010 02:28:55 PM : [iNST-SRX ] 02 50 0A.3C.31 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:28:55 PM : [standard-Group][0A.3C.31-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:28:55 PM : Duplicate: ignored Fri 12/17/2010 02:28:55 PM : [iNST-SRX ] 02 50 0A.3C.31 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:28:55 PM : [standard-Group][0A.3C.31-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:28:56 PM : [iNST-SRX ] 02 50 0A.3C.31 13.24.AA 41 11 01 LTONRR (01) Fri 12/17/2010 02:28:56 PM : [standard-Cleanup][0A.3C.31-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Fri 12/17/2010 02:28:59 PM : [iNST-SRX ] 02 50 0A.3F.38 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:28:59 PM : [standard-Group][0A.3F.38-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:28:59 PM : [ A 3F 38 1] DON 1 Fri 12/17/2010 02:28:59 PM : [iNST-SRX ] 02 50 0A.3F.38 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:28:59 PM : [standard-Group][0A.3F.38-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:28:59 PM : Duplicate: ignored Fri 12/17/2010 02:28:59 PM : [iNST-SRX ] 02 50 0A.3F.38 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:28:59 PM : [standard-Group][0A.3F.38-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:00 PM : [iNST-SRX ] 02 50 0A.3F.38 13.24.AA 41 11 01 LTONRR (01) Fri 12/17/2010 02:29:00 PM : [standard-Cleanup][0A.3F.38-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Fri 12/17/2010 02:29:01 PM : [iNST-SRX ] 02 50 0A.3C.FB 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:01 PM : [standard-Group][0A.3C.FB-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:01 PM : [ A 3C FB 1] DON 1 Fri 12/17/2010 02:29:02 PM : [iNST-SRX ] 02 50 0A.3C.FB 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:02 PM : [standard-Group][0A.3C.FB-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:02 PM : Duplicate: ignored Fri 12/17/2010 02:29:02 PM : [iNST-SRX ] 02 50 0A.3C.FB 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:29:02 PM : [standard-Group][0A.3C.FB-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:02 PM : [iNST-SRX ] 02 50 0A.3C.FB 13.24.AA 42 11 01 LTONRR (01) Fri 12/17/2010 02:29:02 PM : [standard-Cleanup][0A.3C.FB-->ISY/PLM Group=1] Max Hops=2, Hops Left=0 Fri 12/17/2010 02:29:18 PM : [iNST-SRX ] 02 50 0A.3E.E6 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:18 PM : [standard-Group][0A.3E.E6-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:18 PM : [ A 3E E6 1] DON 1 Fri 12/17/2010 02:29:19 PM : [iNST-SRX ] 02 50 0A.3E.E6 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:19 PM : [standard-Group][0A.3E.E6-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:19 PM : Duplicate: ignored Fri 12/17/2010 02:29:19 PM : [iNST-SRX ] 02 50 0A.3E.E6 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:29:19 PM : [standard-Group][0A.3E.E6-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:19 PM : [iNST-SRX ] 02 50 0A.3E.E6 13.24.AA 41 11 01 LTONRR (01) Fri 12/17/2010 02:29:19 PM : [standard-Cleanup][0A.3E.E6-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Fri 12/17/2010 02:29:19 PM : [iNST-SRX ] 02 50 0A.3E.E6 13.24.AA 42 11 01 LTONRR (01) Fri 12/17/2010 02:29:19 PM : [standard-Cleanup][0A.3E.E6-->ISY/PLM Group=1] Max Hops=2, Hops Left=0 Fri 12/17/2010 02:29:19 PM : Duplicate: ignored Fri 12/17/2010 02:29:19 PM : [iNST-SRX ] 02 50 0A.3E.E6 13.24.AA 42 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:29:19 PM : [standard-Cleanup][0A.3E.E6-->ISY/PLM Group=1] Max Hops=2, Hops Left=0 Fri 12/17/2010 02:29:31 PM : [iNST-SRX ] 02 50 11.9B.18 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:31 PM : [standard-Group][11.9B.18-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:31 PM : [ 11 9B 18 1] DON 1 Fri 12/17/2010 02:29:31 PM : [iNST-SRX ] 02 50 11.9B.18 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:31 PM : [standard-Group][11.9B.18-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:31 PM : Duplicate: ignored Fri 12/17/2010 02:29:31 PM : [iNST-SRX ] 02 50 11.9B.18 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:29:31 PM : [standard-Group][11.9B.18-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:32 PM : [iNST-SRX ] 02 50 11.9B.18 13.24.AA 41 11 01 LTONRR (01) Fri 12/17/2010 02:29:32 PM : [standard-Cleanup][11.9B.18-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Fri 12/17/2010 02:29:46 PM : [iNST-SRX ] 02 50 11.9E.0B 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:46 PM : [standard-Group][11.9E.0B-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:46 PM : [ 11 9E B 1] DON 1 Fri 12/17/2010 02:29:46 PM : [iNST-SRX ] 02 50 11.9E.0B 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:46 PM : [standard-Group][11.9E.0B-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:46 PM : Duplicate: ignored Fri 12/17/2010 02:29:46 PM : [iNST-SRX ] 02 50 11.9E.0B 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:29:46 PM : [standard-Group][11.9E.0B-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:46 PM : [iNST-SRX ] 02 50 11.9E.0B 13.24.AA 41 11 01 LTONRR (01) Fri 12/17/2010 02:29:46 PM : [standard-Cleanup][11.9E.0B-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Fri 12/17/2010 02:29:46 PM : [iNST-SRX ] 02 50 11.9E.0B 13.24.AA 42 11 01 LTONRR (01) Fri 12/17/2010 02:29:46 PM : [standard-Cleanup][11.9E.0B-->ISY/PLM Group=1] Max Hops=2, Hops Left=0 Fri 12/17/2010 02:29:46 PM : Duplicate: ignored Fri 12/17/2010 02:29:46 PM : [iNST-SRX ] 02 50 11.9E.0B 13.24.AA 42 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:29:46 PM : [standard-Cleanup][11.9E.0B-->ISY/PLM Group=1] Max Hops=2, Hops Left=0 Fri 12/17/2010 02:29:51 PM : [iNST-SRX ] 02 50 11.A1.45 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:51 PM : [standard-Group][11.A1.45-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:51 PM : [ 11 A1 45 1] DON 1 Fri 12/17/2010 02:29:52 PM : [iNST-SRX ] 02 50 11.A1.45 00.00.01 C7 11 01 LTONRR (01) Fri 12/17/2010 02:29:52 PM : [standard-Group][11.A1.45-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:52 PM : Duplicate: ignored Fri 12/17/2010 02:29:52 PM : [iNST-SRX ] 02 50 11.A1.45 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Fri 12/17/2010 02:29:52 PM : [standard-Group][11.A1.45-->Group=1] Max Hops=3, Hops Left=1 Fri 12/17/2010 02:29:52 PM : [iNST-SRX ] 02 50 11.A1.45 13.24.AA 41 11 01 LTONRR (01) Fri 12/17/2010 02:29:52 PM : [standard-Cleanup][11.A1.45-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

Okay! Here she is. The event capture of the switch truning itself on and the ISY reporting that the switch itself has been activated via paddle press. Key: 15.72.63 Light at significant neighbor's house tied to my ISY 0A.3E.E6 Outdoor motion sensor 0C.FB.F5 The problem bathroom vanity Switchlinc. Tue 12/14/2010 02:19:40 PM : [iNST-SRX ] 02 50 15.72.63 00.00.01 C7 13 00 LTOFFRR(00) Tue 12/14/2010 02:19:40 PM : [standard-Group][15.72.63-->Group=1] Max Hops=3, Hops Left=1 Tue 12/14/2010 02:19:40 PM : [ 15 72 63 1] DOF 0 Tue 12/14/2010 02:19:40 PM : [ 15 72 63 1] ST 0 Tue 12/14/2010 02:19:41 PM : [iNST-SRX ] 02 50 15.72.63 13.24.AA 42 13 01 LTOFFRR(01) Tue 12/14/2010 02:19:41 PM : [standard-Cleanup][15.72.63-->ISY/PLM Group=1] Max Hops=2, Hops Left=0 Tue 12/14/2010 02:19:54 PM : [iNST-SRX ] 02 50 0A.3E.E6 00.00.01 C7 11 01 LTONRR (01) Tue 12/14/2010 02:19:54 PM : [standard-Group][0A.3E.E6-->Group=1] Max Hops=3, Hops Left=1 Tue 12/14/2010 02:19:54 PM : [ A 3E E6 1] DON 1 Tue 12/14/2010 02:19:54 PM : [iNST-SRX ] 02 50 0A.3E.E6 00.00.01 C7 11 01 LTONRR (01) Tue 12/14/2010 02:19:54 PM : [standard-Group][0A.3E.E6-->Group=1] Max Hops=3, Hops Left=1 Tue 12/14/2010 02:19:54 PM : Duplicate: ignored Tue 12/14/2010 02:19:54 PM : [iNST-SRX ] 02 50 0A.3E.E6 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Tue 12/14/2010 02:19:54 PM : [standard-Group][0A.3E.E6-->Group=1] Max Hops=3, Hops Left=1 Tue 12/14/2010 02:19:54 PM : [iNST-SRX ] 02 50 0A.3E.E6 13.24.AA 41 11 01 LTONRR (01) Tue 12/14/2010 02:19:54 PM : [standard-Cleanup][0A.3E.E6-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Tue 12/14/2010 02:19:55 PM : [iNST-SRX ] 02 50 0C.FB.F5 13.24.AA 41 11 01 LTONRR (01) Tue 12/14/2010 02:19:55 PM : [standard-Cleanup][0C.FB.F5-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Tue 12/14/2010 02:19:55 PM : [ C FB F5 1] DON 1 Tue 12/14/2010 02:19:55 PM : [ C FB F5 1] ST 255 Tue 12/14/2010 02:19:55 PM : [iNST-SRX ] 02 50 0A.3E.E6 13.24.AA 47 11 01 LTONRR (01) Tue 12/14/2010 02:19:55 PM : [standard-Cleanup][0A.3E.E6-->ISY/PLM Group=1] Max Hops=3, Hops Left=1

The last two nights I have come home and the Load Active LED has been flashing on and off somewhat randomly at about 1.5s intervals. This is with the module switched off and after using Lee's method to 'reset' the load active condition. Just some more data points. No conclusions.

I have borrowed a laptop and it is now running the event viewer 24/7. I will post back data when/if the event happens again.

And the only way to get an event trace is to leave a computer on 24/7 running with Admin Console running and Event Viewer window open, right?

WOW!!! Replaced switch. And it just happened again today with new switch. I am stumped. I do not know what to do from here. Ideas? BTW, I did contact Smarthome about this issue. The reply was that this is not something they have ever heard of either. Clearly something else is going on here.

Lee, Affirmative, both the unit being returned and the replacement was/is v.3A

All, In all my testing and use of both the original unit and the replacement the module always reliably turned the power to the load on and off. The only issues and differences have been in the function and reliability of the load demand circuit. Wow, that is the exact oppisote of the unit I just pulled out and sent back. I had to have the Load Controller supplying main power to the load to get the Load Active LED to function.

Have you been able to get yours to work this way, I would be okay with that. Please tell me how you did it

A swing and a miss as IndyMike would say. Oh well, I tried.

At the very least the LED for 'load active' is coming on outside any specified parameter. If you look at the table of possible LED conditions based on situations you will see that there is no condition for 'load active' while the module is off (not sending power to connected device). Further, the 'load active' is illuminating even if the load is not active. Smarthome agrees in every conversation I have had with them regarding this issue. That is why they sent me a replacement.

And a stringer of LED lights may very well not be considered a load...