Illusion

I do not think I can help by giving you my programs. As I have over 200 interrelated folder/programs just dealing with the temperature control in my house I think it would confuse things. Even with me having written them it can take me some time to understand their interrelationship to make changes. I have had to make flow charts for portions of it. That said, I would say start simple. Build a set of programs that set temperature based on conditions. Include ability to override these in the conditions and when the override is removed the conditions will have changed and the temps will go back to desired settings. At the core of my system are just a few enabled programs like: Away Temperature: If Program 'Away Flag' is True Then Wait 30 seconds Run Program 'Away Temperature Set Liv Cool' (If) Run Program 'Away Temperature Set Liv Heat ' (If) Wait 6 seconds Run Program 'Away Temperature Set Bedroom Cool' (If) Run Program 'Away Temperature Set Bedroom Heat' (If) Wait 6 seconds Run Program 'Away Temperature Set Office Cool' (If) Run Program 'Away Temperature Set Office Heat' (If) Else - No Actions - (To add one, press 'Action') Daytime Temperature: If From 8:00:00AM To 10:00:00PM (same day) And Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False Then Wait 10 seconds Run Program 'Daytime Temperature Set Liv Cool' (If) Run Program 'Daytime Temperature Set Liv Heat' (If) Wait 6 seconds Run Program 'Daytime Temperature Set Bedroom Cool' (If) Run Program 'Bedroom Mode Check' (If) Else - No Actions - (To add one, press 'Action') Office Occupied: If Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False And ( Status 'Office / Office Fan' is On Or Status 'Office / Office Hutch Lights' is not Off ) Then Run Program 'Occupied Temperature Set Office Cool' (If) Run Program 'Occupied Temperature Set Office Heat' (If) Else - No Actions - (To add one, press 'Action') Office Un-Occupied: If Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False And ( Status 'Office / Office Fan' is Off Or Status 'Office / Office Hutch Lights' is Off ) Then Run Program 'Un-Occupied Temperature Set Office Cool' (If) Run Program 'Un-Occupied Temperature Set Office Heat' (If) Else - No Actions - (To add one, press 'Action') Sleep Temperature: If From 10:01:00PM To 7:59:59AM (next day) And Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False Then Wait 10 seconds Run Program 'Sleep Temperature Set Bedroom Cool' (If) Run Program 'Sleep Temperature Set Bedroom Heat' (If) Wait 6 seconds Run Program 'Sleep Temperature Set Liv Cool' (If) Run Program 'Sleep Temperature Set Liv Heat' (If) Else - No Actions - (To add one, press 'Action') 'Away Flag' is an empty program controlled by my Home/Away KPL button. 'Suspend Temp Programs' is an empty program controlled by a KPL button. You could set a different one for each area. Temperature control is such a personal thing I think it would be tough to have one persons programs work for all. I just list these as ideas to get you started. I do not think my methods of programming are as skillful as more advanced members of this forum. I am reasonably certain that using a different approach like Orest's machine states would greatly simplify things, it is just beyond my capability. So I take a much more blunt force approach. I write some schedule based programs, and then keep adding parameters and other interrelated snippets as situations come up that I wish were accounted for. Years go by and I end up with literately hundreds of programs to adjust my temperature. Messy, but it does work flawlessly and nearly every possible desired operating parameter has been addressed. The one nice thing about this approach is that you can have basic scheduling and/or occupancy with some overrides and away settings operational in 30m of programming or less.

Yes. Admin console self closed as expected as I remember it. Not 100% sure as this was some time ago. I did not know the programs did not get changed till today when I noticed the events caused by conditions that included the switch did not run.

Replaced a switchlinc relay using "replace device with". It does not appear to have saved the programs this device was a participant in. All show as 'not specified'. No time avail for additional testing but wanted to report. Posted with tapatalk

Test complete. The only battery to survive all the test contamination over the years gave up the ghost today. While it was still detecting motion, the liquid electrical tape I put over the light sensor apparently degraded to the point it had been allowing dusk dawn triggers of 10 per day for some time. I brought the unit in to add more liquid tape to the sensor and as a rule I require seeing the MD send an on and off in response to set button presses before I will put the cover back on. She gave me an on, but the battery could not muster up enough energy for the off. I am calling Time of death 7-19-11 for a battery that was put in service 9-27-09. This is in a heavy use area with 15-40 triggers per day. This also had a PLM replace and restore in there which takes extra power. Further, for some time this MD has been sending Dusk/Dawn triggers many times per day. And it was still working when I pulled it down to try to stop the Dusk/Dawn commands. Almost two years. Not bad. Temperature range 8Ëš-109Ëš.

Smooth upgrade. Fixed event viewer level selection for me Fixed Switchlinc Relay LED Backlight issue. BTW. There appears to be two identical "Release 3.1.5 (Beta) Is Now Available" topics with different replies. Forum Bug?

Sorry for the false lead johnnyt, I realized moments after submitting that link and post that it only applies to users of the Pro version. I should have asked before sending you to a topic that does not help.

Please read viewtopic.php?t=536#p3401 in its entirety. This exact issue is addressed in the last few posts.

Thanks for the answer on the errors. Yeah, I can make that switch beep just fine: Wed 07/13/2011 09:39:09 AM : [ Time] 09:39:09 2(0) Wed 07/13/2011 09:39:09 AM : [iNST-ACK ] 02 62 18.32.DE 0F 30 BE 06 BEEP (BE) Wed 07/13/2011 09:39:09 AM : [iNST-ACK ] 02 62 18.32.DE 0F 30 BE 06 BEEP (BE): Process ACK: duplicate ignored Wed 07/13/2011 09:39:09 AM : [ Time] 09:39:10 2(0) Wed 07/13/2011 09:39:09 AM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 30 BE BEEP (BE) Wed 07/13/2011 09:39:09 AM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Wed 07/13/2011 09:39:09 AM : Duplicate: ignored Wed 07/13/2011 09:39:09 AM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 30 BE BEEP (BE): Process Message: failed Wed 07/13/2011 09:39:09 AM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Michel, I can assure you that both the unit I am replacing and the the unit I am replacing it with do indeed have beep. The title I used in my post is from the description the ISY places on these devices. I do not know why it says beep for the dimmer version but not for the relay version. And the errors I see in the event viewer... are those anything to be concerned about?

And while doing all this trouble-shooting I have noticed lots of instances of these errors in my event viewer: Mon 07/11/2011 03:19:18 PM : [FileOpen ] Open failed for [/CONF/ELECMTR.CFG] (r) Mon 07/11/2011 03:19:18 PM : [FileOpen ] Open failed for [/CONF/ELEC.CFG] (r) Mon 07/11/2011 03:17:00 PM : [FileOpen ] Open failed for [/CONF/IR.CFG] (r) Is this anything to be concerned about?

I have a 2476S that I use a program to adjust the back-light of each day. This used to work flawlessly around 2.8.16 but no longer functions in 3.1.3 or 3.1.4. I am replacing the 2476S (Hardware V5.5) due to failure to respond to local control but before this local control issue appeared the back-light had stopped responding to the program. I chalked it up to device failure but that does not appear to be the case. I received my replacement 2476 and added it and did the "replace device with function" under 3.1.3 but was unable to control the back-light from the ISY. Seeing that 3.1.4 specifically addresses the 2476s I re-added it after upgrading to 3.1.4. With just adding the device but before adding it to scenes or programs I attempted to adjust its back-light. No good. Here is the level 3 event trace: (2476S) SwitchLinc Relay - Remote Control On/Off Switch v.3A Hardware v5.8 Mon 07/11/2011 03:31:54 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:31:54 PM : [18 32 DE 1 ] Memory : Write dbAddr=0x0264 [FF] Mon 07/11/2011 03:31:55 PM : [iNST-ACK ] 02 62 18.32.DE 1F 2E 00 00 07 FF 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:31:55 PM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:31:55 PM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 07/11/2011 03:32:05 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:32:05 PM : [18 32 DE 1 ] Memory : Write dbAddr=0x0264 [01] Mon 07/11/2011 03:32:06 PM : [iNST-ACK ] 02 62 18.32.DE 1F 2E 00 00 07 01 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:32:06 PM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:32:06 PM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 It appears to communicate alright, but the back-light does not change intensity. Next I factory reset the old switch (the one I am replacing) and added it back to the ISY. I then tried to change its back-light using the LED brightness button. This very switch used to respond to back-light intensity changes. Level 3 Event Trace: (2476S) SwitchLinc Relay - Remote Control On/Off Switch v.3A Hardware v5.5 Mon 07/11/2011 03:32:55 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:32:55 PM : [14 E5 FF 1 ] Memory : Write dbAddr=0x0264 [FF] Mon 07/11/2011 03:32:55 PM : [iNST-ACK ] 02 62 14.E5.FF 1F 2E 00 00 07 FF 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:32:55 PM : [iNST-SRX ] 02 50 14.E5.FF 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:32:55 PM : [standard-Direct Ack][14.E5.FF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 07/11/2011 03:33:04 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:33:04 PM : [14 E5 FF 1 ] Memory : Write dbAddr=0x0264 [01] Mon 07/11/2011 03:33:04 PM : [iNST-ACK ] 02 62 14.E5.FF 1F 2E 00 00 07 01 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:33:04 PM : [iNST-SRX ] 02 50 14.E5.FF 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:33:04 PM : [standard-Direct Ack][14.E5.FF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 And here is the level 3 Event trace from another switch that still responds to LED commands correctly: (2476D) SwitchLinc Dimmer W/Beeper v.38 Mon 07/11/2011 03:33:45 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:33:45 PM : [16 3A 15 1 ] Memory : Write dbAddr=0x0264 [FF] Mon 07/11/2011 03:33:45 PM : [iNST-ACK ] 02 62 16.3A.15 1F 2E 00 00 03 FF 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:33:45 PM : [iNST-SRX ] 02 50 16.3A.15 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:33:45 PM : [standard-Direct Ack][16.3A.15-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 07/11/2011 03:33:58 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:33:58 PM : [16 3A 15 1 ] Memory : Write dbAddr=0x0264 [01] Mon 07/11/2011 03:33:58 PM : [iNST-ACK ] 02 62 16.3A.15 1F 2E 00 00 03 01 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:33:58 PM : [iNST-SRX ] 02 50 16.3A.15 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:33:58 PM : [standard-Direct Ack][16.3A.15-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

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.