Bug - Philips 324131092621 single press action triggers when doing a long press

[queimadus]

Blueprint name

Philips 324131092621

Home Assistant Core Version

2025.10.2

Home Assistant Installation Type

Home Assistant Operating System

Description

When performing a long press on any button, both the single press action and the long press action will trigger. Using zigbee2mqtt.

Automation YAML config

alias: Controller - Philips 324131092621 Hue Dimmer switch - Bathroom
description: ""
use_blueprint:
  path: EPMatt/philips_324131092621.yaml
  input:
    integration: Zigbee2MQTT
    controller_device: 90ffac2a69376c5c6dca5b7a200c66c2
    helper_last_controller_event: input_text.helper_philips_remote
    action_button_up_short:
      - target:
          device_id: 91560209c6b009b829b95c652013b8e3
        data: {}
        action: media_player.volume_up
    action_button_up_long:
      - target:
          device_id: 91560209c6b009b829b95c652013b8e3
        data: {}
        action: media_player.media_next_track

To Reproduce

1. Perform a long press on the up button
2. See that both the single press and long press actions were triggered

Expected behavior

Only the long press action is triggered

Actual Behaviour

Both the single press and long press action are triggered

Additional Details

• I'd like to help developing a fix for this issue.

Screenshots

No response

Additional context

I believe this is because we are listening to up_press events instead of up_press_release. Changing the blueprint to listen to up_press_release instead of up_press (and doing the same for all other actions: down, on, off) in the actions_mapping seems to make it work correctly.

[yarafie]

@queimadus Hi. Very interesting observation.

What I am understanding from your explanation, is that when you hold down any of the buttons (a long press), it is triggering the single button action and the long button action both?

I don't have the device but do you know how to listen to the mqqt events for it? The reason I'm asking is I know the blueprint very well, and the only way it would do that is if when you press/hold down any of the buttons, it sends both the event for the press and hold events one after the other. I would also be interested to see what gets sent when you release the button after a long hold.

I'd just like to confirm my suspicion.

[queimadus]

it is triggering the single button action and the long button action both?

Correct. I used MQTT explorer to check the events being sent. When doing a long press gesture, it sends a on_press event, before sending the on_hold event. If I just do a simple press there's a on_press followed by a on_press_release.

I don't have access to it right now to get some more detailed information, but that's what I observed when I was investigating.

I've been using the device with these changes applied, and it has been working correctly. I can open a PR when I have more time but I just wanted to open a issue and confirm if this made sense, or if any other people experienced the same problem.

It may be worth noting that the zha integration already uses the on_short_release for the button_on_short mapping.

[yarafie]

Totally makes sense. I think others have reported it and there are some pull requests already pending.
However EPMatt has not been active for a while, so it seems, so don't know if you do a PR if it is going to be rolled in.

I had forked EPMatts Repo a while back as I was contributing heavily (Migrated all the blueprints to z2m 2.x, added new controllers)

I wasn't planning to come back to my fork, but I've had some time on my hands.
I've updated my fork, cleaned it up (No Security Vulnerabilities at least according to the github tab on top, which you probably won't see anyways 💯 )

I've rolled in and fixed many issues that were reported on EPMatts Repo and folded in some pull requests that EPMatt didn't get around to, and added additional devices that don't exist in his repo.

I just pushed your fixes for the philips_324131092621 to my Repo, so you can import it from there if you like.

https://yarafie.github.io/awesome-ha-blueprints/docs/blueprints/controllers/philips_324131092621

[queimadus]

Ah, didn't notice this project was "abandoned". I started using the blueprint from your fork and confirm it works correctly 👍

Thank you!