Shelly BLU Remote Control ZB Long / Double / Triple Press

Configuration
1

Hi,

I want to use the features of the Shelly BLU Remote Control ZB for long or double press.
The feature is here in HA, but HA doesn´t recognize the event when triggered.
Single click works perfect.

Does anybody have an idea?

Bildschirmfoto 2026-04-27 um 20.04.55
Bildschirmfoto 2026-04-27 um 20.04.55948×890 36.7 KB

2

you can use Developer Tools/Events to check what is really received when clicked, double-clicked, etc.

3

I don´t see anything. What am I doing wrong?
Sorry, I´m new to HA.

Bildschirmfoto 2026-04-29 um 08.39.14
Bildschirmfoto 2026-04-29 um 08.39.141440×1742 146 KB

4

If you are using ZHA for Zigbee you should subscribe to zha_event (so one of the items in the list or * for all events):

Screenshot_20260429-084322
Screenshot_20260429-084322840×1820 135 KB

With the information from the captured events you can later create the triggers for your automation (here you should read a little bit about event triggers first).

5

OK got it, thanks! The available event types are listet, but the only event-type that is recognized ist “press”. Double-Pressing and so isn´t shown in the log.

Note: The Remote Control is connected via BTHome to Shelly BLU Gateway.

event_type: state_changed
data:
  entity_id: event.bthome_sensor_cd56_shelly_fernbedienung_button_2
  old_state:
    entity_id: event.bthome_sensor_cd56_shelly_fernbedienung_button_2
    state: "2026-04-29T07:44:12.261+00:00"
    attributes:
      event_types:
        - press
        - double_press
        - triple_press
        - long_press
        - long_double_press
        - long_triple_press
        - hold_press
      event_type: press
      device_class: button
      friendly_name: Button rechts
    last_changed: "2026-04-29T07:44:12.261226+00:00"
    last_reported: "2026-04-29T07:44:12.261226+00:00"
    last_updated: "2026-04-29T07:44:12.261226+00:00"
    context:
      id: 
      parent_id: null
      user_id: null
  new_state:
    entity_id: event.bthome_sensor_cd56_shelly_fernbedienung_button_2
    state: "2026-04-29T07:44:16.844+00:00"
    attributes:
      event_types:
        - press
        - double_press
        - triple_press
        - long_press
        - long_double_press
        - long_triple_press
        - hold_press
      event_type: press
      device_class: button
      friendly_name: Button rechts
    last_changed: "2026-04-29T07:44:16.844112+00:00"
    last_reported: "2026-04-29T07:44:16.844112+00:00"
    last_updated: "2026-04-29T07:44:16.844112+00:00"
    context:
      id: 
      parent_id: null
      user_id: null
origin: LOCAL
time_fired: "2026-04-29T07:44:16.844112+00:00"
context:
  id: 
  parent_id: null
  user_id: null
6

If the integration supports the device you should get correct new_state.attributes.event_type (which is one of event_types). If you always get press no matter what, you can try to file a bug report for the BTHome integration here. BTW, are you sure that the device really supports double_press, etc.?

See

at least they do not mention double_press, maybe long_press works?

7

Oh my gosh, you’re right. I misunderstood… Now I hope for a firmware update, so long I can use the dimmer wheel for my use case…