Hue Dimmer - Cannot send button held command without button pressed sent first

I just got a Hue Remote Dimmer to try out and have added it first to the Hue app and then ran discovery in the Hue Bridge integration to add the device to Hubitat.

In the Hue app I opted to configure the buttons elsewhere. I was hoping to be able to use Button Controller app to control two different lights. I wanted:

Button 1 Pushed - Toggle Ceiling Lights
Button 1 Held - Toggle Table Lamp

However when I hold button 1 it first sends an event for button 1 pushed before button 1 held, resulting in both lights toggling. I've not used buttons in my system before, is that the correct behaviour? Thanks.

(Assuming you are talking about events, not commands...)

From what I remember, yes. The driver just passes along everything the device sends, and I don't think there's anything for a plain release (after a short press). So, it passes along what it does get: a short push ("pushed"), continued holding ("held"), and a release after a long hold ("released"). Then you can do whatever you want with the events you actually care about, but unfortunately there isn't a good way to separate a push from a hold -- at least not without implementing some sort of timer that waits and then does a "pushed" if it doesn't get a "held," an idea I don't love for a device that is ultimately Zigbee even if it's over the reliable Hue API. Something like this is would ceratinly possible, however... (although still not sure how reliable it would be).

1 Like

Thanks Robert I thought that could be the case and did wonder if it could somehow differentiate - never mind.

FYI unimportant but I noticed a tiny flaw in your docs. You describe a setup for a 5 button pico but it looks like in your example button rule that you'd copied the raise level commands to the lower level button so the screenshot doesn't quite reflect the description - button 4 should be 'start lowering' (very minor):

Thanks for catching that! Updated the screenshot.

If you do have a use case for this, I could experiment with a driver change in 2.4.1 (option or entirely different driver, I'm not sure yet...). But given the above, I'm still hesitant for pretty much any reason except the reliable Hue API. Picos are the only built-in drivers I can think of that do something similar, so it's not unheard of, but ClearConnect probably has something over Zigbee. :smiley:

I have one Hue Dimmer Switch paired directly to Hubitat, and have different actions for "push" and "hold" configured in Button Controller.

I use a custom driver, but there is an built-in one as well.

1 Like

Yes I've certainly a use for it. Having the additional commands available would allow me control of additional devices from the same position without additional remotes. That's more for aesthetics/WAF. One remote could be used to toggle and dim the main ceiling lights, toggle the table lamp, fully open/close the blinds/curtains in that room. I'm sure I can't be alone in trying to get more out of those 4 buttons.

Yes Pico's would be the way forward. In the "matter bulbs suck, I'm going back to Hue" thread I've been looking at and discussing that possibility. It would mean a not inconsiderable outlay for the Lutron Hub and it could only be used for Pico's as in the UK we can't use Caseta (which is a crying shame as potentially I would gone full Lutron at the outset for sheer reliability/usability). I'd need to import the 5 button Pico's (relatively straight forward via amazon global shipping)

Thanks. That doesn't work via the Hue Bridge integration. I've loaded the driver and reset the remote to give it a try. The instructions for adding the device differ between that driver page and the Hubitat add device page but as it happens neither work for me and it won't pair. This was just an experiment to see if it could work as I wanted but I'd rather not pair direct anyway so will relink it to the Hue hub for now.

Edit: It did eventually pair and appear in the device page and Zigbee details page but other than initial error messages it wouldn't log an event for any button press. I've reset it and re added it to the Hue.

FANTASTIC! I just did a factory reset on my Hue dimmer switch V2, added it as a Zigbee device, and applied your custom driver. It works perfectly and allows me to trigger a button "HELD" command without the button "PUSHED" command beforehand. Thanks!

My use of the dimmer switch is a bit unorthodox but something that maintains my sanity. I CANNOT STAND COMMERCIALS when watching TV. I use an Amazon Fire TV stick for most of my TV's. I had set up a custom voice routine for Alexa where I would say "Alexa, commercial skip one" and then Alexa says "One minute commercial break," followed by a command to mute my fire tv stick for one minute and then unmute. (I actually have my Alexa devices set up to respond to "Computer" instead of "Alexa" as I will forever be a TNG nerd.) I had set up identical routines for "Computer, commercial skip two," where Alexa says "Two minute commercial break" along with muting the TV sound for 2 minutes and then unmuting. I had commercial skip three and four set up as well.

It got a little annoying having to actually say "Computer, commercial skip two" or whatever, especially if I had company over. So I set up the Hue Dimmer switch as an alternative to trigger these routines. When I press the #1 button, it triggers the one minute commercial skip routine, muting the TV for one minute. The #2 button triggers a 90 second commercial skip, the #3 a two minute skip, and the #4 button a three minute commercial skip.

I wanted to activate other routines using the HELD function on the remote and your driver made this possible. Holding the #1 button triggers a routine to fast-forward the video I'm watching by one minute. #2 HELD triggers a 90 second fast forward. #3 HELD triggers a 90 second rewind and #4 HELD triggers a one minute rewind.

Thanks again for the custom driver to make all of this work seamlessly!

1 Like