Hue lights and keypad

[troychasey]

I'm running into a little problem setting a keypad to control my hue scenes.

 

 

Set up:

3 dimmer switches

1 dimming 6 button keypad

 

I have 3 insteon dimmer switches set as follows:

• all wired "always-on"
• "on" state is set at 28% and sets hue lights to 20% and sets the state of all dimmer switches to 28% and keypad to 28%
• "fast-on" sets the hue lights to 100% and sets the state of all dimmer switches to 100% and keypad to 100%
• "off" sets the state of all dimmer switches to off and keypad to off

1 dimming 6 button keypad set as follows:

• wired "always-on"
• Press and hold on "on" or "off" dims hue bulbs via hue's "bri_inc"
• "on" turns hue lights to 100% and sets the state of all dimmer switches to 100%
• "off" turns hue lights to off and sets the state of all dimmer switches to off
• button d (the problem button) turns on and off a hue scene called "pinky" which is a bunch of colors

 

The Problem

 

pressing on or off on any of my switches, successfully overrides my scene "pinky"

But I can not find a way to set the status of button d to off.

 

I know... a lot of setup for a tiny question.

 

Thank you in advance for any help.

[mwester]

Add button d as a responder to a scene.  Then, in your programs that do the hue work, just set that scene to "on" or "off" in order to cause that LED on the keypad to illuminate or not.

[troychasey]

Add button d as a responder to a scene. Then, in your programs that do the hue work, just set that scene to "on" or "off" in order to cause that LED on the keypad to illuminate or not.

So I make a scene that has no purpose other than to turn off the keypad lights!? Brilliant. I'll try that.

[troychasey]

Add button d as a responder to a scene. Then, in your programs that do the hue work, just set that scene to "on" or "off" in order to cause that LED on the keypad to illuminate or not.

And thank you

[mwester]

So I make a scene that has no purpose other than to turn off the keypad lights!? Brilliant. I'll try that.

  Yep, exactly.  Seems really odd, but that's actually pretty common when dealing with z-wave and network resources, or basically with any devices that are not Insteon-based.   With a pure Insteon-based implementation, the scene and the button behavior usually "just work" because of the way one usually constructs scenes; when I added z-wave I ended up creating a bucket-load of scenes that exist for no other purpose than to control the LEDs on my keypads.  Naming conventions are useful to keep those scenes separate from any Insteon scenes that have controllers driving them.