Is it possible to set up the Philips Hue Remote v2 so that holding the 'hue' button acts like a modifier key?

So I have the Hue remote v2 (I’m sure most people here are familiar with it). I have it set up in a room to control the ceiling lights, which are 4x Innr zigbee bulbs. These aren’t full RGB bulbs, but are instead just colour temp bulbs (1800k-5000k).

The remote is set up to be on/off for the top button, and brightness up and down on the other two buttons (as is the default). However I would like to be able to control the colour temperature as well.

I had the idea that maybe holding the hue button, while pressing the bright +/- buttons, could be a good way to do this. IF this is even possible?

I have no idea how I would even start going about this, so any help would be appreciated. I am new to home assistant and I actually thought there would be a lot more simplified/helpful documentation about these things, but seems it’s mostly geared towards people who already know what they are doing lol.

You don’t mention whether your remote controls the bulbs via an automation or blueprint, or whether it’s bound directly to the bulbs (that “as is the default” seems to imply the latter).

If you’re using an automation, here’s the way I would do it. Note that I don’t own a hue remote and this is just based on assumption that you’re referring to the Hue dimmer using Z2MQTT.

According to the Z2M page for that device, the Hue button switches between 2 scenes:
“The device keeps track of each press, alternating between two scenes ("sceneid":1 and "sceneid":2 ) in a predetermined group with "groupid":43632 , using the commandRecall command”.
You might have different behaviour if you’re using ZHA.

So:

  • Add a condition to your automation which checks the state of the scene. If it’s "sceneid":1, the brightness keys should send a brightness command, otherwise they should send a colour temperature command.
  • Set up a separate automation that checks for "sceneid":2 command being sent. Add a 30s delay, then send a "sceneid":1 command.

The way it works is this:

  • When you want to control the temperature, press (don’t hold) the hue button - "sceneid":2 command will be sent.
  • Adjust the temperature using the brightness buttons. Given that the first automation is checking which scene is “active”, the buttons should control the temperature because scene 2 is currently active for the next 30s.
  • After 30s have elapsed, the second automation will set scene 1 as the active scene (aka the default). Pressing the brightness buttons will now control the brightness. This way you always know what the default behaviour of the remote will be without having to remember which scene it was on previously.

You might have to mess around with helpers if the state of the scene is not stored, but at least now you have a general idea how this could be tackled.

The Blueprint for that switch should allow many ways to activate Scenes of your own creation (for lighting brightness and colors).