LeeG

Look at the display clip in my previous post. The right side of the display on line 1 says "SwitchLinc Dimmer DB", line 2 has the Insteon address with the device firmware level v.40 at the end of line 2. This is the SwitchLinc with rev 6.5 hardware. Now that the Access Points are coupling, links could be working now that were not working before.

I think the rev 7.5 (which is the device hardware level) that is not recognized has a device firmware level that 3.3.10 does not understand. The device firmware level is displayed at the end of line 2 of the right side display. My rev 6.5 requires about 2 seconds of Set button press to set the mode that controls the On Level when the local paddle is pressed. Why it will not come out of 'resume bright' mode I do not know. Could be defective but I'm doubtful of that. This thumbnail is of the rev 6.5 SwitchLinc which has a device firmware level of v.40

There are two different factors involved. For the SwitchLinc controlling the physical load, around page 10-12 of the SwitchLinc User Guide (depends of the device firmware level) there is a discussion of how the SwitchLinc will react when its paddle is used to turn On the load. There is a 'resume bright' mode where the SwitchLinc remembers its last On Level and 'resumes' that On Level the next time turned On with its paddle. The other mode has the SwitchLinc come On to a fixed On Level. The User Guide covers how to set these modes. The other factor is what happens when the SwitchLinc controlling the load is turned On as a Responder. There should be one ISY Scene with the three SwitchLincs listed in Red as Controllers below the Scene name. Scenexxx SwitchLinc1 SwitchLinc2 SwitchLinc3 Assuming SwitchLinc1 controls the physical load, click the Red SwitchLinc2 node. The SwitchLinc1 Responder On Level is the the level SwitchLinc1 turns On when SwitchLinc2 On paddle is pressed. Click the Red SwitchLinc3 node, set the Responder On Level for SwitchLinc1 to the level it should turn On when SwitchLinc3 On paddle is pressed.

The Program changes the value of variable $Dehumidifier. When the Wait is issued the Program is triggered because the variable has changed value except now the If is False driving the Else clause. The statements after the Wait never execute. If the change to the variable should not trigger the Program the variable should be an Integer rather than a State variable. If the variable is an integer already the change in Humidity as the dehumidifier runs will also trigger the Program again. The value of 1 in the variable will make the if False so the statements after the Wait will not execute. A solution to both situations is have this Program invoke Program 2 which has the existing Then logic. That way when Program 1 is triggered again and runs the Else it will not affect Program 2. EDIT: Wait and Repeat statements allow a Program to be triggered again when the conditions in the If have changed. See this Wiki section which covers Wait and Repeat statements. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order

Unfortunately that cannot be done with a single SwitchLinc. Tapping the Off paddle (simple Off or double tap to generate a Fast Off) will turn the SwitchLinc load Off. Assuming the lamps are already on LampLincs a KeypadLinc or even a battery powered 4 button Mini Remote can be used to control the SwitchLinc with its load and the LampLincs with their load independently.

It sounds like Insteon Direct On/Off commands are being sent to the I/o Linc Relay. Regardless of the momentary mode a Direct On command always turns the Relay On and a Direct Off command turns the Relay Off if currently On. The various command actions described in the I/O Linc User Guide apply to Scene On/Off commands only. Except for applications going through the PLM Insteon devices cannot send Direct commands so the User Guide does not discuss how the I/O Linc reacts to them. Define an ISY Scene with the I/O Linc Relay as Responder. Send Scene On/Off commands to have the I/O Linc Relay respond as described in the I/O Linc User Guide.

Access Points, now called Range Extenders, should blink Red when receiving the test message and on the same 120v leg. If blinking Green the test message is being received with the Range Extender being on the opposite 120v leg. If the second Range Extender is not blinking it is not receiving the bridge test message.

Physically replace the old KPL with the new one. Add the new KPL to the ISY using a dummy name. Right click on the old KPL primary node (ISY will not physically communicate with old KPL). Select Replace 'oldKPLname' with .... which will list the KPLs with the same number of buttons which will include the new KPL under the dummy name. Select the new KPL. The new KPL will be configured as the old KPL, the new KPL dummy name will be changed to the old KPL name so Programs and Scenes will not have to be changed. When the process completes the Admin Console will close so that two KPLs with the same name will not appear.

Run Tools | Diagnostics | Show PLM Links Table. That will display the PLM Link database which may have been lost. I think there is a Count button that will be active when the display is complete; click Count to get number of link records in PLM.. May have lost an Access Point (Range Extender) so the 2 120v legs are no longer coupled. Tap the Set button on the PLM 4 times to start the bridging test. Does a Dual Band device indicate it is on the opposite 120v leg and receiving the bridge test messages.

Stu makes a good point, Integer Variables CANNOT trigger a Program but CAN affect the True/False evaluation of the If clause when the Program is triggered by something else. "device1" being switched On triggers the Program and the value in the Integer variable affects the True/False analysis. Changing the value of $Integer1 NEVER triggers the Program. It must be triggered by "device1" but once triggered the value of Integer1 must be 0 for the If to be True and run the Then clause. If Control 'device1' is switched On And $Integer1 = 0 Then

State variables changing value can trigger programs, Integer variables changing values do not trigger Programs. That is the difference between a State and Integer variable. EDIT: folks have found it a good practice to indicate in the Variable name whether a State or Integer variable. $ixxx or $Ixxx - I use a capital "I" but case makes no difference $sxxx or $Sxxx it serves as a reminder and makes programs self documenting.

I was recommending updating the ISY Firmware from 4.0.5 to 4.2.18. I know of nothing specific in the 15 or so updates that affect this but 4.0.5 is pretty old. Turning a device On/Off directly does not affect other devices. Turn the ISY Scene that has the vanity light and KPL button On/Off to have both devices to react in sync. Something on your system is working with the KPL button and vanity light which produced the Blue messages. Scene:Master Bath - Vanity Off 0 Thu 2014/10/16 11:16:07 PM Program Log (KPL) Master Bath - Vanity Lt Status 100% Thu 2014/10/16 11:16:07 PM System Log Master Bath - Vanity Light Status 100% Thu 2014/10/16 11:16:07 PM System Log

It looks like another Program or group of Programs is running at the same time. Both the KPL button and the Vanity Light are being turned On to 100%. Look at the Program(s) you have created that work with these devices. Scene:Master Bath - Vanity Off 0 Thu 2014/10/16 11:16:07 PM Program Log (KPL) Master Bath - Vanity Lt Status 100% Thu 2014/10/16 11:16:07 PM System Log Master Bath - Vanity Light Status 100% Thu 2014/10/16 11:16:07 PM System Log I would also suggest updating the ISY to 4.2.18. Also since this activity is attempting to compensate for a marginal Insteon network resolving the powerline or coupling problems would eliminate the need for these Programs.

The Event trace should be at LEVEL 3 to have useful data.

Release 4.2.17 is the latest ISY firmware today, by the end of the weekend (if on schedule) 4.2.18 will be available which has some minor functional updates. Either 4.2.17 or 4.2.18 are much better choice than 4.0.5.

Both of those devices are battery powered. Put the Motion Sensor into linking mode using the Motion Sensor Set button. Use New INSTEON Device, enter Insteon address of Motion Sensor, Name of choice, and Auto Discover. Be sure Motion Sensor is near a Dual Band device. Being near Dual Band 2413 PLM is good. When New INSTEON Device is complete be sure to take Motion Sensor out of linking mode before following the same procedure for the Mini Remote.

There are more parts to this puzzle. The "Set Scene 'xxxxx' On" can turn Off a Responder with a 0% On Level but a "Set Scene 'xxxxx' Off" can only turn the Responders Off. Something else besides the posted Program and Scene is turning On "Master Bath - Vanity Light Status 100%" Scene:Master Bath - Vanity Off 0 Thu 2014/10/16 11:16:07 PM Program Log (KPL) Master Bath - Vanity Lt Status 100% Thu 2014/10/16 11:16:07 PM System Log Master Bath - Vanity Light Status 100% Thu 2014/10/16 11:16:07 PM System Log Sorry for delay in getting back, my DSL has been down. Is Master Bath - Vanity Light a Dimmer? I'm wondering if a Program is getting confused if the device is manually set to some level that is not Off and not 100% Also what is the ISY Firmware level?

Scenes themselves do not (cannot) loop. This Log activity is generated by a Program. Please post the Program(s). Scene:Master Bath - Vanity Off 0 Thu 2014/10/16 11:16:07 PM Program Log (KPL) Master Bath - Vanity Lt Status 100% Thu 2014/10/16 11:16:07 PM System Log Master Bath - Vanity Light Status 100% Thu 2014/10/16 11:16:07 PM System Log Scene:Master Bath - Vanity On Thu 2014/10/16 11:16:07 PM Program Log (KPL) Master Bath - Vanity Lt Status 0% Thu 2014/10/16 11:16:08 PM System Log Master Bath - Vanity Light Status 0% Thu 2014/10/16 11:16:08 PM System Log Scene:Master Bath - Vanity Off 0 Thu 2014/10/16 11:16:08 PM Program Log (KPL) Master Bath - Vanity Lt Status 100% Thu 2014/10/16 11:16:08 PM System Log Master Bath - Vanity Light Status 100% Thu 2014/10/16 11:16:08 PM System Log Scene:Master Bath - Vanity On Thu 2014/10/16 11:16:08 PM Program Log (KPL) Master Bath - Vanity Lt Status 0% Thu 2014/10/16 11:16:09 PM System Log Master Bath - Vanity Light Status 0% Thu 2014/10/16 11:16:09 PM System Log Scene:Master Bath - Vanity Off 0 Thu 2014/10/16 11:16:09 PM Program Log (KPL) Master Bath - Vanity Lt Status 100% Thu 2014/10/16 11:16:09 PM System Log Master Bath - Vanity Light Status 100% Thu 2014/10/16 11:16:09 PM System Log Scene:Master Bath - Vanity On Thu 2014/10/16 11:16:09 PM Program Log (KPL) Master Bath - Vanity Lt Status 0% Thu 2014/10/16 11:16:10 PM System Log Master Bath - Vanity Light Status 0% Thu 2014/10/16 11:16:10 PM System Log Scene:Master Bath - Vanity Off 0 Thu 2014/10/16 11:16:10 PM Program Log (KPL) Master Bath - Vanity Lt Status 100% Thu 2014/10/16 11:16:10 PM System Log Master Bath - Vanity Light Status 100% Thu 2014/10/16 11:16:10 PM System Log Scene:Master Bath - Vanity On Thu 2014/10/16 11:16:10 PM Program Log (KPL) Master Bath - Vanity Lt Status 0% Thu 2014/10/16 11:16:11 PM System Log Master Bath - Vanity Light Status 0% Thu 2014/10/16 11:16:11 PM System Log

Node 2 is the Relay node. Node 1 is the Sensor node. Tue 10/28/2014 02:09:03 AM : [ 24 2C B0 2] ST 255 IOLinc status Tue 10/28/2014 02:09:04 AM : [ 24 2C B0 1] DON 0 IOLinc Relay on THIS IS SENSOR, not Relay. Tue 10/28/2014 02:09:04 AM : [ 24 2C B0 1] ST 255 IOLinc Status Trace of Relay being turned Off/On. Note the node is 2. Tue 10/28/2014 10:51:57 PM : [iNST-TX-I1 ] 02 62 15 BB 5A 0F 11 02 Tue 10/28/2014 10:51:57 PM : [iNST-ACK ] 02 62 15.BB.5A 0F 11 02 06 LTONRR (02) Tue 10/28/2014 10:51:57 PM : [iNST-SRX ] 02 50 15.BB.5A 22.80.0B 2B 11 02 LTONRR (02) Tue 10/28/2014 10:51:57 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/28/2014 10:55:03 PM : [iNST-TX-I1 ] 02 62 15 BB 5A 0F 13 02 Tue 10/28/2014 10:55:03 PM : [iNST-ACK ] 02 62 15.BB.5A 0F 13 02 06 LTOFFRR(02) Tue 10/28/2014 10:55:03 PM : [iNST-SRX ] 02 50 15.BB.5A 22.80.0B 2B 13 02 LTOFFRR(02) Tue 10/28/2014 10:55:03 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/28/2014 10:55:03 PM : [D2D EVENT ] Event [15 BB 5A 2] [sT] [0] uom=0 prec=-1 Tue 10/28/2014 10:55:03 PM : [ 15 BB 5A 2] ST 0 Tue 10/28/2014 10:55:18 PM : [iNST-TX-I1 ] 02 62 15 BB 5A 0F 11 02 Tue 10/28/2014 10:55:18 PM : [iNST-ACK ] 02 62 15.BB.5A 0F 11 02 06 LTONRR (02) Tue 10/28/2014 10:55:18 PM : [iNST-SRX ] 02 50 15.BB.5A 22.80.0B 2B 11 02 LTONRR (02) Tue 10/28/2014 10:55:18 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/28/2014 10:55:18 PM : [D2D EVENT ] Event [15 BB 5A 2] [sT] [255] uom=0 prec=-1 Tue 10/28/2014 10:55:18 PM : [ 15 BB 5A 2] ST 255

Can you post the IO Linc nodes ...

I don't think the garage door moved as a result of the I/O Linc Relay. There should have been a Log entry that reflected a Relay command. Scene:SceneIOLincRelay On Tue 2014/10/28 02:39:19 PM Web Log IOLinc I2CS-Relay Status 100% Tue 2014/10/28 02:39:19 PM System Log Scene:SceneIOLincRelay On Tue 2014/10/28 02:43:05 PM Web Log oberkc view that it was triggered by RF unrelated to the I/O Linc is supported by the Log which shows the Sensor changing state when the door moved but no Relay activity.

All battery powered devices have to be put into linking mode manually by pressing and holding Set button. Then use New INSTEON Device, entering Insteon address, Name of choice, and use Auto Discover. Be sure to take device out of linking mode before moving on to next device. What ISY Firmware is being used? Release 4.0.5 does not work as the Hidden Door Sensor is not supported at that level. Install 4.2.17 and refresh Admin Console, being sure to clear Java cache including Applications. Click Help | About to verify both Firmware and UI indicate 4.2.17. If it does not work with 4.2.17 run Tools | Diagnostics | Event Viewer at LEVEL 3 while adding Hidden Door Sensor and post event trace.

Being in a Scene does not cause the Scene to execute when the device is turned On/Off with the Admin Console. Have to turn the Scene on/Off.

In a vertical column..... Breaker 1 - leg 1 Breaker 2 - leg 2 Breaker 3 - leg 1 Breaker 4 - leg 2 Breaker 5 - leg 1 etc They are structured this way so a double breaker in position 3 & 4 provides 240v.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Attempt to add the SwitchLinc to the ISY and post the event trace. There are various reasons why the ISY would not accept the SwitchLinc. The event trace should help identify why. Is this still being done with the 99i at 3.3.10? The reason I ask is later KPLs will not add to 3.3.10 because Smarthome changed the information in the later KPL. Not sure about what has been done with the latest SwitchLinc.