LeeG

Unless SmartLabs has changed the way non-toggle On works, and no other Scene/Program is adjusting On/Off state of button, the KPL is not working as described in manual. All my KPL buttons in non-toggle On mode are bright after 2 blinks. I may not the the latest KPL firmware. What is the KPL firmware?

Until Stu is up on West coast, Unswitched Line and Neutral go to both SwitchLincs. This provides power to both devices. The Load wire to light is connected to Red wire of one SwitchLinc. The Red wire on other SwitchLinc is capped, no connection.

Suggest a Show Device Links Table for new I/O Linc. The Sensor must have a Controller (E2) link pointing back to the PLM. Also an Event Trace at LEVEL 3 showing door open/close of first I/O Linc. The I/O Linc is powerline only. It is possible for one device to work and another on the same circuit not work if powerline comm is poor.

Does the Sensor status LED next to wire connections turn On/Off with door movement? Is the new I/O Linc on the same or opposite 120v leg? Are the 2 120v legs coupled? If yes, how?

Suggest a Factory Reset of KPL and Restore Device. If no other Scenes or Programs are involved and Factory Reset/Restore Device does not resolve, the KPL is failing. Is the ON button bright when pressed compared to A-D?

The LED Brightness applies to all buttons. Not possible to set individual button LED Brightness Don't follow what is happening with A-D buttons. In non-toggle On mode the button will blink twice when pressed and go to LED Brightness for an On button.

The ISY Scene name "Master bedroom motion" and "Master bedroom-Sensor" are different Insteon Controllers. The "Master bedroom motion" ISY Scene uses the PLM as the Controller. Using "Master bedroom motion" as the first (Controller) parameter has no affect on the "Master bedroom-Sensor" Controller result. To affect the "Master bedroom-Sensor" result use this statement In Scene "Master Bedroom / Devices / Master bedroom-Sensor" Set "Master Bedroom / Devices / Master bedroom lamp" 10% (On Level) Also note that by the time the Program is triggered the On command has already been sent to lamp so the first motion On changes the Responder On Level in link record but affect will not be seen until next Motion On.

The maximum values for LED Brightness are Off=7 On=15 Toggle mode is On/Off so as the button is pressed it cycles from On to Off to On to Off Non-toggle mode can be non-toggle On where the the button press always sends an On command and the button LED is bright, or non-toggle Off where the button press always sends an Off command and the button LED is dim. A Program can be triggered with a button press and the button LED turned On (max bright) or turned Off and the button LED is dim.

The last Show ISY Links Table that was posted did not have the required links. That is why I suggested doing a Show ISY Links Table for a simple switch to see if problem was larger than I2CS Keypad. Also if a Delete Modem (PLM) was done. "Sounds like I need to redelete it, re-add it and then add it back to all the scenes?" Yes.

Don't do a Restore Device as the ISY Backup that was restored has the bad information.

Still need to know Firmware and UI Levels. The color of the LampLinc in a Scene is based on whether the LampLinc was added to the Scene as a Controller (will be Red) or added as a Responder (not Red).

LampLincs are Controllers (Red) whether they are actually functioning as a Controller or Responder. Same with other devices such as SwitchLincs which are Controllers (Red) whether they are actually controlling another device.

I have 4 LampLincs on this system from v.28 to v.3B. They are Red as they are Controllers. What Firmware and UI levels are being used (Help | About)?

The Keypad information does not have link records with the new PLM address. Being an I2CS device the link record is required for the device to accept write requests. Perhaps a Delete Modem (PLM) was issued or 0D,52.4F was the old PLM address and this device did not pickup the PLM change. It may require the Keypad be Deleted and readded to pick up the new PLM. EDIT: do a Show ISY Links Table on a SwitchLinc/ToggleLinc/Icon device (whatever you use) and see if there is a link record with the new PLM address 30.DB.C7 E2 01 30.DB.C7 .. .. .. It may be the ISY was not powered down when the PLM was changed.

All the attempts are being NAKed in the Event Trace. That would indicate the I2CS Keypad is not allowing the current PLM to access the Keypad. Suggest doing a Show ISY Links Table for Keypad and post the first few link records along with the current PLM Insteon address.

bipto information is so very good. Need to understand why I/O Linc Relay activated the garage door movement before thinking about a fix. Many of these events have nothing to do with an All On, which you did not have. An Event Trace at LEVEL 3 taken when door moves unexpectedly will offer good info as to why and how to fix/bypass.

The KPL Owners Manual assumptions do not anticipate the ISY. Radio buttons have issues. Better to do things with Scenes. Sceneaaaa KPL1 button A - Controller KPL2 button A - Controller KPL1 button B - Responder - On Level 0% KPL1 button C - Responder - On Level 0% KPL1 button D - Responder - On Level 0% KPL2 button B - Responder - On Level 0% KPL2 button C - Responder - On Level 0% KPL2 button D - Responder - On Level 0% other device(s) controlled by button A Scenebbbb KPL1 button B - Controller KPL2 button B - Controller KPL1 button A - Responder - On Level 0% KPL1 button C - Responder - On Level 0% KPL1 button D - Responder - On Level 0% KPL2 button A - Responder - On Level 0% KPL2 button C - Responder - On Level 0% KPL2 button D - Responder - On Level 0% other device(s) controlled by button B and so on for buttons C and D as Controllers. Be sure to Delete the two KPLs and Factory Reset to eliminate Radio Button information. The above Scenes assume pressing button A on either KPL turns Off buttons B,C,D on both KPLs.

Post #2 has the link to the Migration documentation you requested. It covers Migration from 99i to 994i

Can also check the link records in the FanLinc for the Ramp Rate. The nature of the Fanlinc speed control could make the Off command appear to not work with a slow Ramp Rate. So many unknowns at this point. Without more facts there all guesses.

Without information about 'Master Bedroom Fan Low' nor the furnace load, my guess is the furnace load drops below 500 watts before the 20 minute Wait completes. Of course any change in furnace load above 500 will restart the Wait.

The process of changing PLMs was not successful. The link display for 24.A2.27 is missing the E2 ...... Controller link back to the new PLM. Without the Controller link the device cannot send back to the PLM a state change initiated by the device. Was a Delete Modem (PLM) issued.? Do a Show ISY Links Table for the same device to see if the ISY has also lost the Controller link (E2 .......) information. If the Show ISY Links Table has the E2 link record a File | Restore Devices is needed. If the ISY links is also missing the E2 link an ISY Backup taken before the new PLM was installed followed by File | Restore Devices is needed.

Sounds like the ISY may not have been powered down during PLM switch. Do a Show Device Links Table on one of the switches. Is there a E2 01 xx.yy.zz ....... link where xx.yy.zz is the new PLM Insteon address.

" I have done it in the same place I always" I am noting that the update that is failing is to change the PLM address in the RemoteLinc so the PLM is different from when the RemoteLinc was last successfully updated.

Since the PLM address is being changed things are not exactly the same. Was the old PLM a 2412? Being near another Dual Band device can also be an issue. Add some distance between RemoteLinc and Dual Band device.

Try another set of batteries.