KeypadLinc 2486S problem

[steelman58]

I have a 6-button KeypadLinc 2486S (v.36) which I am using to control a ceiling fan via FanLinc.

 

When I performed the initial wiring install of the KPL I did a full reset to factory defaults (I normally do this with each device I install when it has been used elsewhere in the house). Using the Admin Console>> Link Management>> NEW Insteon Device I linked the KPL to the ISY. Once linked, when I pressed either the "On" or "Off" KPL buttons, some other lights in the house turned "Off" (it is always the same ones). Pressing the same button again or the opposite button does not turn the affected lights back "On". This all happens before performing any further linking or adding of scenes. None of the affected lights were prevously controlled by this KPL (as far as I recall).

 

Interestingly, the devices under My Lighting in the Admin Console will still show the lights as "On" regardless of them being off. Also, this anomoly only occurs when using the KPL's "Off" and "On" buttons. It does not happen if I use the ISY Admin Console. This makes me think the issue is with the KPL. I've checked to see if there are any links that shouldn't be there but it all looks clean. Possibly I have not done a proper reset to factory defaults, but I've now done it 4 times following the instructions in the KPL manual.

 

I do not have much experience troubleshooting Insteon devices and the ISY-99i and was wondering if anyone has encountered a similar situation? I could not find any posts on the forum which could help with troubleshooting. Any suggestions would be appreciated.

[LeeG]

Assuming this is not the result of an ISY Program being triggered by the KeypadLinc ON/OFF buttons, the problem is the KeypadLinc was linked to the other devices at some point. Resetting the KeypadLinc only clears the link records in the KeypadLinc. The other devices still have link records pointing to the KeypadLinc.

 

Define a Scene, add the KeypadLinc ON button as a Controller and one of the devices that is reacting that should not be as a Responder to the Scene. Then Remove the other device and the KeypadLinc from the Scene. If that stops the other device repeat the steps for each device that is responding that should not be.

[steelman58]

LeeG,

 

I thought the issue was possibly with the KPL and not with the other devices that were responding. I tried what you suggested with making a scene and deleting the device and the KPL from it. Unfortunately, it did not work. So I tried to see if one of the problem devices had any links to the KPL. For the problem device I did a "Show Device Links Table" scan and then did a compare. What you see below is the output.

 

The first line is the ID Address for a ControLinc which controls the Wall Lamp. The second line has an ID Address of 18.5B.84 which belongs to the problematic KPL. What does "Record Mismatch" mean? Further down, "Record Mismatch" shows up again for the link to the PLM (18.CF.42).

 

Should I just delete the device and reinstall, or, should I do something else?

 

[LeeG]

First try a Restore Device for the 2nd Floor device. The mismatch means the device has a link record at a particular link record address that does not match what the ISY thinks should be there. A Restore Device will direct the ISY to rebuild the 2nd Floor device link database.

 

Then do another Show Device Links Table for the 2nd Floor device to see if any link record remains for the problem KeypadLinc. If not then the problem for that device should be resolved and the same approach can be used for the other device(s) as well.

 

If there is still a link record for the problem KeypadLinc then the solution is to Delete the 2nd Floor device and add it back clean.

[steelman58]

LeeG,

 

As it turns out, all three devices which were inadvertently and unintentionally being controlled by the KPL had the same issue and were evident in the Device Links Table comparison. After restoring the devices as you recommended, they are no longer linked to the KPL. This meant I did not have to delete and reinstall the devices which would've required removing them from scenes and then adding them again. This saved a lot of time.

 

Thanks again for your help. This troubleshooting issue has really opened my eyes to some of the ISY tools that are available for correcting problems.