Can you try this fix on the dev branch for the dimming issue
Otherwise Can you DM me some traces?
Also DM me traces for your second issue
Yes, I’ve pulled two traces. But can you DM me? I don’t have privileges.
I realised there’s a config option for your second issue… forgot I did that to be honest 
By default it repeats actions/scenes 3 times as a way to deal with complex scenes
Try changing action_repeat_on_press_count ‘(ADVANCED) Repeat actions on multi-presses’ to 0
That should fix that for you, let me know. I’m going to push another change soon so that repeat logic only applies to scenes and not actions.
For your first issue I’ve just pushed a change to the dev branch if you can test that?
I’ve tested this. Still turns off the light after dimming action on long press
Would you mind sharing the blueprint for the sonoff 8 button rf remote?
This is great, @TheHolyRoger !
I am running into some odd issues.
I use the Hue button to trigger scripts. These scripts sometimes include voice announcements and changes to lighting.
With your blueprint, and my options below, I get these symptoms:
When a button is pressed once, the announcement and lights change per the script. No problem.
When a button is pressed twice the announcement is made. No problem.
When a button is pressed three times, the announcement for the 2x press is heard briefly before being cut off by the announcement for the 3x button press. Plus, the 3x button press announcement is heard 3 times. The lights change to the 3x button press script.
When I press a button 4x, I hear the announcement for 2x button press, before being cutoff by the announcement for 3x button press. As I have no announcements for 4x press, 3x announcement continues uninterrupted.
I presume some logic loop issue?
alias: Philips Hue Button
description: ""
use_blueprint:
path: TheHolyRoger/Philips_HUE_SmartButton.yaml
input:
action_button_short_release:
- action: script.chill_mode_2
metadata: {}
data: {}
action_button_double_press:
- action: script.chill_mode_advanced_duplicate
metadata: {}
data: {}
action_button_triple_press:
- action: script.script_living_room_normal_red_button
metadata: {}
data: {}
controller_topic: zigbee2mqtt/Philips Hue Button/action
helper_last_controller_event: input_text.phillips_hue_button_text
button_toggle_dim_entity_first_press: false
button_hold_to_dim: false
hold_to_dim_direction_down: false
button_multi_press_always_fire_first_release: false
delay_between_action_repeats: 600
action_button_quadruple_press:
- action: light.turn_off
metadata: {}
data: {}
target:
area_id: living_room
Hello No matter what I try I can not get the ZHA integration with the button to work. I have log book entries. I have battery and identify under configuration. My device info : RDM003
by Signify Netherlands B.V.
My Zigbee info look like below:
IEEE: 00:17:88:
Nwk: 0x2c65
Device Type: EndDevice
LQI: 108
RSSI: -84
Last seen: 2025-04-11T17:23:15
Power source: Battery or Unknown
Quirk: zhaquirks.philips.rom001.PhilipsROM001
Hello there,
after upgrading my HASS to 2025.5 I have a strange issue: The multi-press actions don’t work anymore. It is strange, because the double press does get caught in the device log "Remote Button Double Press - Turn On event was fired", the action (for me it is toggling a shelly) is not performed. Anyone else with this issue?
1 Like
I’m experiencing the same thing. Wasn’t sure when it started but my long press to toggle a ceiling fan switch no longer works.
Edit: Looking at the helper I created to use this blueprint shows that when I perform a long press it’s recording the event initially as a long press and then when letting go of the button it immediately overwrites it with a short button press event.
Hi there!
I’ve been trying to set up two actions using this automation, one for single button press, the other for double.
Both work with a caveat - double press also initiates the single press. Any way to override this behavior?
Hi, Thanks for the great blueprint. By any chance will you be updating it to include the latest Philips Hue Buttom (RDM005)?
I’ve used this blueprint successfully in the past but now cannot. It relies on a 500 character text helper. When setting up the blueprint, it says:
Input Text used to store the last event fired by the controller. You will need to manually create a text input entity for this, please read the blueprint Additional Notes for more info.
I can’t find the additional notes with guidance anywhere. My understanding is that the original workaround to increase text helper max length beyond 255 was patched last month.
What’s the best way to make the blueprint work in the meantime? As currently defined, I don’t think I can point it at another object (ie. a templated sensor) to store the data, because it insists on a text helper. Back in 2021 there was discussion of using an attribute to do this, but enough has changed in Home Assistant in the last 4 years that none of the guidance remains relevant – and I’m not sure this blueprint would even work with that.
Edit: answering my own question. I’m sure there’s a good reason you shouldn’t do this, but there seem to be a bunch of reasons (1, 2) you need to. I patched .storage/input_text directly on the HA filesystem to increase the max value, then restarted… and all good, it works great now.
1 Like
I noticed there have not been any updates for about a year to this blueprint. Since the issue with the text_helper seems to have become a blocker, I have set out to try and fix this OR re-implement the functionality of this blueprint. When working on this, I will be posting issues in the code that i run into. Please all enjoy my reports and conversely if you are more experienced and see me going off the rails, please do speak up.
First point is the selection of the device to use as a trigger. The current selection specifies a number of possible combinations of integration (Hue or zha) and manufacturer. I think this can be simplified by just filtering on the two integrations and the possible model designations. I will try to see if a regex can be used, so it could be reduced to a mere two options that is automatically also future proof.
Edit: reloading the YAML makes for better testing. The selector filering seems to be pickier than I tought.
Does your version RDM005 is supported en Z2M ? Mine is not… And i think this is blocking the automation to work properly… 
Hello all,
I’m trying to read through all of this and figure out how to get my buttons working with ZHA, but I’m a bit lost with everything. With all of my other products I just paired them and was able to use them, with the button the best I’m able to get into an automation is on/off - but I also need the brightness+ and brightness- functionality. Looking through the recent issues, I’m unclear on how to proceed. Is there a step-by-step somewhere I can follow to do this?
Any luck so far?
I’m not seeing anything named input_text in /config/.storage/ (all I can seem to get to with Studio Code Server), is there a .storage before config that I need to be accessing? If so, can you point me in the right direction on how I would get to that? Studio Code Server seems to be locking to /config/ as the root
Files or folders that start with a . are usually considered hidden, and for good reason: your .storage folder will be full of internal files (auth, core, lovelace, etc.) that are not considered user-editable. I don’t know anything about Studio Code Server but perhaps it is hiding hidden files, in which case, perhaps there is an option to reveal them.
Do you happen to know the location I should be looking in for the .storage folder? I’m not seeing it at the root and can’t find anything with find. Thanks again!
In that screenshot you’re in your homedir (~). I don’t know where the Home Assistant install is relative to that on HAOS.
I can see from your first ls that there’s a config folder there. If that’s it, the command would be ls config/.storage.
I see there’s also a homeassistant folder in your homedir, you could try ls ~/homeassistant/config/.storage.