Jump to content

franky

Members
  • Posts

    7
  • Joined

  • Last visited

franky's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. I'm not sure how to tell what the firmware is on the KPL. It says "(2486DWH8) KeypadLinc Dimmer 8 Button v.2D" for all 3 of them, but v.2D doesn't sound like a valid version unless it's in hex and interpreted as 2.13? How can I tell the firmware version? I just bought these from Smarthome a few weeks ago. Thanks for the help.
  2. Yes, that's exactly what I did when I posted the other night. Re-reading my post, I can see the confusion...sorry. I added all 8 lights to the same mutually exclusive group and the first 4 buttons behave correctly by disabling the other 7 when you press any of them; however, the last 4 buttons do not disable any of the other 7 buttons when pressed (but they do turn off when any of the first 4 buttons are pressed).
  3. Actually, you can cross link the 8-key KeypadLinc buttons manually so that all 8 buttons are mutually exclusive from eachother (although it will take you an hour of pushing and holding the buttons for 10 seconds each)...meaning that at any given point, only one button can be lit up. The ISY software has the limitation of only allowing 4 buttons to be mutually exclusive to each other at a time. This is what I was asking. Is there a way to make the ISY setup the KeypadLinc to make all 8 buttons mutually exclusive to each other so that pushing any of the 8 buttons turns off the other 7?
  4. 2.6.6 doesn't seem to allow for more than 4 mutually exclusive buttons on a KeypadLinc 8-button dimmer. The GUI lets me add all 8, but there's strange behavior: * Pressing any of the first 4 turns off all other 7 buttons, so these 4 seem to work correctly * But, pressing any of the last 4 just act as normal toggle buttons and don't turn off any other buttons Looks like it's not sending all of the commands correctly. I've done this over 20 times with the exact same behavior, so it's not a connection issue. I've tried deleteing all programs in the GUI, resetting the keypad to it's factory defaults, forcing a device reset from the GUI, but nothing did the trick. Any ideas? Is this a known bug with this version?
×
×
  • Create New...