Illusion

I got the replacement unit today. I did a "replace with" but am unable to make the ISY control this new 2476S back-light. Do I need to delete it, upgrade to the latest beta and add it back to the ISY to be able to control the back-light?

Michel, Thanks for the quick reply. We are all at the mercy of the single supplier.

Hi Lee, Thanks for the suggestion. I did a device link compare for 8 devices. 3 were KPLs. Man that took a long time. In all cases the link records were identical or identical/ignore or just ignore. No extra records or mismatches in the random sample. Very strange. While trying to troubleshoot the KPL back-light issue I referenced earlier in this thread I noticed that the back-light on this problem SWR was not going dim even though there was no comm errors. I just figured it took a surge. I did a reset/restore on it but that did not fix the back-light issue. I tried to adjust the back-light locally. That worked. But any attempts to adjust it from the ISY either programatically or manually through the device options fails to change the intensity. So I just changed out the bottom light pipe to a frosted and called that dark enough. I removed this switch from the programs that change the back-lights and let it alone. The next morning I noticed that the ISY did not turn this switch off after 10m like it is supposed to. (shower exhaust fan). I discover that device status is not updating in the ISY. Do a couple more factory resets/restores before I discover the link table issue. Somewhere in this process the switch stops responding to local on requests. I decide there is too much wrong with this switch now and I call for an exchange. But I still find the messed up link table fascinating. Especially as I cannot find another link table with errors. Another Insteon mystery. I have to let so much of my inquisitive side go with this stuff because there is just so much we cannot see. The mysterious v.35 issue which no one can explain what the failure is or how a switch can effect so much that it is not a party to, my bathroom vanity switch that ghosts on if it is not a controller of a scene even with exchanged units, my IRLinc RX that sends 5 repeated commands if my TV is not on a filter (where is that in the Insteon protocol?) and currently for me these two KPLs that all of a sudden occasionally will not change their back-light brightness because of a comm error so severe that they do not respond to three direct attempts. But just sometimes! So try to troubleshoot that!!! If I do something that fixes it, I will not know what it is and I will stop trying to understand. Cause I Can't. Just having it work will have to be enough for me. Sorry, rambling. Frustrated with Insteon for the past couple of weeks. Can't seem to get ahead of it. Sometimes it controls me instead of me controlling it...

"- Support for 2476S" I am lost. I thought this module was long supported. Smarthome list this as: SwitchLinc Relay - INSTEON Remote Control On/Off Switch (Non-Dimming), White As I am having unusual difficulties with this exact module is there an issue with me adding it using 3.1.3? It did add correctly, but I had some odd link table issues.

I had a switchlincrelay (SWR) go wonky on me. I did a factory reset and restore from the ISY. The switch seemed bad. It would not respond to any of the scenes it was a member of. I did a link table comparison and the ISY showed it should have a single link, to the PLM. But the ISY knows that this device is a member of a whole bunch of scenes. I had to remove/re add the device and re-assign it to its scenes. Why would the ISY not know about needed links for scenes the ISY knows the switch is part of? I restored a KPL recently and sure enough it does not appear to have all its scene info either. Link table comparison shows correct, but that does not mean anything if the ISY link table is incorrect. Thoughts?

Sorry this may be a bit late, but I am having difficulty with the event viewer. It will be sometime before I can download and test on the latest firmware so I will report here. If I select level 3 (whatever that is called now) and then try to drop back to level 1 it still shows level 3 info. If I select none, then select level 1 or 3 the event viewer will still not propagate information. I have to reopen the event viewer from the tools menu to get it to work. I have also found I have to select my desired info level before opening the new window because it will open to the last selection and then I cannot change it, except to level 0 (none) successfully.

It has been 3 months since I made the problem switch a controller of a test scene with a spare switch in it as the responder. The switch has not ghosted on since then. I have removed the spare switch from the system and the scene. I am interested if just making this switch a controller of a scene with no responders other than the PLM will also prevent the ghosting on phenomenon. I am assuming it will be the same as having another switch in there. As I understand it, the scenes we see in the ISY has the ISY as a responder to the scene, just like all the devices in said scene, right? So creating a scene with just this problem switch in it should be the same as having a responder switch in the scene as well?

Something else is going on here. I am not sure what. I pressed the buttons on the 3AM KPl approx 50 times. All showed up in the event viewer with 2 hops left, no button presses missed.

Thanks Lee. I will see what I can do. Querys on the devices only are loosing 1 hop most times. Having trouble getting consistent results though.

Since upgrading to 3.1.3 I have had a problem changing the back-lights in two of my KPLs. I have this done programmaticly. I am trying to determine if I have a new comm issue or if it could have something to do with the beta. I never had an issue with this before, but I did add 5 additional devices after upgrading to 3.1.3 Here is a log of the level three event viewer.: Mon 06/13/2011 04:42:44 PM : [All ] Writing 2 bytes to devices Mon 06/13/2011 04:42:44 PM : [12 3A 85 1 ] Memory : Write dbAddr=0x0264 [00] Mon 06/13/2011 04:42:44 PM : [12 3A 85 1 ] Using engine version i1 for 'Wake 3AM' Mon 06/13/2011 04:42:44 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:42:53 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:02 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:03 PM : [iNST-SRX ] 02 50 12.3A.85 13.24.AA 23 28 02 SET-MSB(02) Mon 06/13/2011 04:43:03 PM : [standard-Direct Ack][12.3A.85-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 06/13/2011 04:43:03 PM : [iNST-ACK ] 02 62 12.3A.85 0F 2B 64 06 PEEK (64) Mon 06/13/2011 04:43:07 PM : [12 3A 85 1 ] Memory : Write dbAddr=0x0264 [00] - Failed Mon 06/13/2011 04:43:07 PM : [All ] Writing 2 bytes to devices Mon 06/13/2011 04:43:07 PM : [F C1 DE 1 ] Memory : Write dbAddr=0x0264 [00] Mon 06/13/2011 04:43:07 PM : [F C1 DE 1 ] Using engine version i1 for 'Front Porch KPL' Mon 06/13/2011 04:43:07 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:09 PM : [iNST-SRX ] 02 50 0F.C1.DE 13.24.AA 26 28 02 SET-MSB(02) Mon 06/13/2011 04:43:09 PM : [standard-Direct Ack][0F.C1.DE-->ISY/PLM Group=0] Max Hops=2, Hops Left=1 Mon 06/13/2011 04:43:09 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 2B 64 06 PEEK (64) Mon 06/13/2011 04:43:18 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:27 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:31 PM : [F C1 DE 1 ] Memory : Write dbAddr=0x0264 [00] - Failed Both devices are v.2d I made a test program that just tries to change the back-lights in these two problem devices for testing purposes. Each device is on a different circuit. I do not appear to be having any other comm issues, even with other devices on those same circuits. These are the only two I am having trouble with. The regular program changes lots of switch's back-lights, but it appears to only use i2 on these two, the two I am having trouble with. Thoughts? An issue with the beta or because I changed something else in the system?

When I select a device from the new web interface I do not see a title for which device I am looking at...

Yes, the nodes for the IR TX are there in the list for me as well.

I confirm the nodes of the IRLinc RX do not show up in the list of nodes window in 3.1.3

In Variables when I try to change the name of the variable the bottom 20% of the text I am typing is cut off. Once I exit the editing of the line I am able to see all the text.

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?