Illusion

Andy, I see what you are talking about. I can confirm this is also the case in the version I am running before upgrade 2.8.16 I will check after upgrading as well

Andy, I am upgrading later today and will be adding an IRLinc TX (converts Insteon to IR) later today. I will also be working extensively with my IRLinc RX as well (converts IR to Insteon). What is it I should be looking for. I am not sure I understand your concern but would like to help if I can by confirming your issue.

Is this a permanent part of our upgrade life? As all releases from now on are above 2.8.5, is there some point in the release chain where we are safe and no longer need to perform this step any longer to upgrade? I am on 2.8.16. Is this step required to be performed for me to install the 3.1.3 beta?

Another option is to consider the Venstar Commercial line of the thermostats. 2700, 2800, 2900. These are designed to be security devices with cool set point limitation, heat set point limits, and keypad lock options. As this is done at the t-stat no programs or querys would be necessary and it should be 100% reliable with no education or interaction with renters. They also can be security locked into program auto mode while still allowing limits on manual overrides.

Lee, Still no more ghosting on instances since I made problem switch a controller for an arbitrary scene. Maybe this would work as a solution for the few others that have experienced this phenomenon. Since this issue presented itself, this is the longest period, by far, that I have not had a ghost on incident.

Interesting data point: Since making the problem switch a controller of a scene I have not had it ghost on. I wonder in the other cases where this has been reported (other forums) if the switch in question was not a controller of any scenes.

Too late for me to evaluate now as those conditions have changed, but I thought it was interesting that the last run and last finish times were blank. As that program ran last night it is odd to not have a value in that field. My ISY is on back-up power and does not cycle off even for a split second as it is actually running off the battery at all times. (online back-up power source). May not have anything to do with DST change, but thought I would report it here in case others have similar issues.

Thank you Chris and Michel. This explains the behavior I have been experiencing. And on another note. Daylight Saving Time. Spring forward today. This program failed to run: Switch Backlights Day: If From Sunrise - 29 minutes To Sunset + 29 minutes (same day) And Program 'Away Flag' is False And Program 'Keypads are Dim' is True Then Run Program 'Backlight level Bright' (Then Path) Else - No Actions - (To add one, press 'Action') Backlight level Bright: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Bedroom / Wake / Wake 3AM' On 15 / Off 7 (Backlight Level) Set 'Bathroom / Bathroom Shower Fan' 0% (Backlight Level) Set 'Front Yard / Front Porch KPL' On 15 / Off 7 (Backlight Level) Set 'Livingroom / HVAC KPL' On 15 / Off 7 (Backlight Level) Set 'Livingroom / Livingroom KPL - On' On 15 / Off 7 (Backlight Level) Set 'Livingroom / Livingroom Mantle' 0% (Backlight Level) Set 'Livingroom / Livingroom Overheads' 0% (Backlight Level) Set 'Back Yard / Back Porch Middle Low' On 15 / Off 7 (Backlight Level) Run Program 'Keypads are Dim' (Else Path) Else - No Actions - (To add one, press 'Action') Program Summary shows Last Run and Last Finish for Switch Backlights Day as Sun 2011/03/13 7:11:33 AM Program Summary for Backlight level Bright shows Last Run and Last Finish as blank. I manually ran the then portion of Switch Backlights Day to get the backlights bright today. As this is the first time the program has failed in this manner I assume it is related to DST.

Test Notify Program: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send Notification to 'Gmail' content 'Test' Else - No Actions - (To add one, press 'Action') Successful email content: Name: test Subject: test Body:test Deleted word "test" in body and replaced with "${alert.node.addr}" and saved. Failed email content: Name: test Subject: test Body:${alert.node.addr} Deleted "${alert.node.addr}" and put the word "test" in its place and saved. Successful email content: Name: test Subject: test Body:test Deleted the word "test" and put "${alert.control} in its place and saved. Failed email content: Name: test Subject: test Body:${alert.control} Deleted "${alert.control}" and put the word "test" in its place and saved. Successful email content: Name: test Subject: test Body:test Deleted the word "test" in subject and put "${alert.group.name} in its place and saved. Successful email content: Name: test Subject:${alert.group.name} Body:test

Vanity is responder to nine scenes. Controller to none. That in and of itself is interesting. I think I will make this device a controller of some scene and see if it turns the scene on when it ghosts on. I assume it will as it is sending the command out as though it had been switched on. Scene:Number of devices in scene 1:7 2:47 3:8 4:7 5:3 6:5 7:32 8:35 9:5

Played around with custom notifications just a bit for the first time the other day. It appears that if there is no value for a variable in a custom notification the notification is not sent at all. IE. I put a control variable in the body of the notification, I build a program without any if values. The then is to send the custom notification. I manually run the then portion of the program. No notification is sent. Is this normal? Have I understood the failure to send reason correctly?

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