dizzyjay Posted December 2, 2012 Posted December 2, 2012 I have a ISY program set to turn on all my (insteon) lights including the ones assigned to the main dimmer on each of my two 8 button keypads. I have assigned the "All On" scene to the "B-scene" slot on each of the keypads. When i turn on the scene using the html interface, all of lights function as programmed; when I turn them on using the keypad, all the lights except for the ones assigned to the same keypad i'm using turn on. This happens on both keypads. If I manually turn on the individual light using the keypad while the B-scene is on and then turn it off using the B-scene button, all lights turn off including the ones assigned on the keypad i'm using. Any ideas what I'm doing wrong? thanks in advance- dj
LeeG Posted December 2, 2012 Posted December 2, 2012 What is the KeypadLinc firmware level and what is the ISY firmware level? Edit: what is the Main A or ON button responder On Level when button B node below the Scene name is selected.
dizzyjay Posted December 2, 2012 Author Posted December 2, 2012 levels for A-nodes on both keypadLincs set to 100% for the scene assigned to B-node; the A-node in off position when I click the B-node. Firmware for ISY: v3.2.6; not sure on the firmware for keypadLinc but happy to check if you can point me towards a "how to".
LeeG Posted December 2, 2012 Posted December 2, 2012 Click the KeypadLinc Primary node in My Lighting tree. Second line in right pane has KPL firmware - v.xx.
LeeG Posted December 2, 2012 Posted December 2, 2012 The latest I have is v.40 which does support button B turning On/Off Main A. I'm running 3.3.4. Try a right click on the KPL Primary node, select Diagnostics | Query Insteon Engine. Then set Main A Responder On Level when Button B as Controller is selected to something different to force an update to the KPL. See if Button B will now turn On Main A. The Main A Responder On Level can be set back to 100% On Level. Changing the Responder On Level for Main A is to force a KPL update after running Query Insteon Engine. If that does not work it may be necessary to upgrade to 3.3.4. I don't think v.41 firmware dropped the capability of Button B controlling Main A.
dizzyjay Posted December 2, 2012 Author Posted December 2, 2012 I ran thru the tests and it did not fix; I also upgraded the ISY to 3.3.4 and it did not resolve either. Is there a way to factory reset the KPL?
LeeG Posted December 2, 2012 Posted December 2, 2012 Yes, the KPL User Guide describes the process of factory reset. Pull the air gap for 30 seconds. Push it all the way in past the level of the frame for 10 seconds. A Restore Device has to be done after that to restore the device link database.
LeeG Posted December 2, 2012 Posted December 2, 2012 Run Help | About, verify Firmware and UI both show 3.3.4. If UI (Admin Console) is not 3.3.4 the URL invoking the Admin Console needs to be updated to get the Admin Console to 3.3.4.
dizzyjay Posted December 2, 2012 Author Posted December 2, 2012 thanks for hanging in there with me LeeG; both interfaces are 3.3.4; a factory reset & restore on one of the KLP did not fix. to confirm how i set everything up i made another scene with just the light on the KLP (node A) and assigned it to another button (node C) on the same KLP (as a responder); it did not work either. If i run it from anywhere other than the KLP, it works fine.
LeeG Posted December 2, 2012 Posted December 2, 2012 Is this a Relay or Dimmer KPL? I ran my test on an 8 button KPL Dimmer with v.40 firmware. The only thing I can think of now is to Delete the KPL from the ISY. Do a factory reset of the KPL and add it back to the ISY from scratch under 3.3.4.
dizzyjay Posted December 2, 2012 Author Posted December 2, 2012 I believe it's a dimmer: KPL (#2486DWH8); I just tried the suggestion of deleting/factory reset of one of the 2 KPL and it did not resolve the issue appreciate the attempts.
Recommended Posts