How do debug shelly.click problem?

Configuration
1

How would I debug this weird shelly.click problem

This automation for a Shelly 2.5 works perfectly:

  trigger:
    - platform: event
      event_type: shelly.click
      event_data:
        device: shellyswitch25-1234567
        channel: 1
        click_type: long
  action:
    - service: alarm_control_panel.alarm_arm_away
      data:
        entity_id: alarm_control_panel.elkm1_house
        code: my_code

This automation for a shellyplus fails in an unusual way: the alarm actually disarms rather than arms.

  trigger:
    - platform: event
      event_type: shelly.click
      event_data:
        device: shellyplus2pm-abcdefg
        channel: 2
        click_type: long_push
  action:
    - service: alarm_control_panel.alarm_arm_away
      data:
        entity_id: alarm_control_panel.elkm1_house
        code: my_code
2

You use the developer tools and go to the events tab.
In the lower part you can enter a listener, so type shelly.click there and then start listening and activate the buttons.

3

Thanks for your reply. The only difference is that while both types of switches report click_type (as shown in my automations) the shellyplus also reports btn_dn and btn_up. Presumably, that shouldn’t matter but I’m wondering. The action is identical in both cases, so I know it works (for the shelly2.5). I also know I’m hitting the alarm service with the shellyplus automation, since the alarm tells me it is disarming. I get the feeling that maybe btn_dn is hitting it (arming) and btn_up is hitting it again (disarming).

4

btn_dn and btn_up should not be acted on, because you have defined long and long_press as the click types.
Only those two should be reacted on.