Xiaomi wireless wall switch event reporting confusion

Hi kind people of the forums! I have a somewhat weird situation regarding a xiaomi wireless wall switch which is this little thing here.

What applies is:

I have configured my switch, in customization.yaml as such:

binary_sensor.wall_switch_158d0001576456:
    friendly_name: Bedroom slave switch
    device_class: connectivity
    hidden: true

Then I have coded my automation, in my automation.yaml as such (which works OK - I am not here to ask help on the automation code):

- alias: Time-based bedroom light toggle
  trigger:
  - platform: event
    event_type: click
    event_data:
      entity_id: binary_sensor.wall_switch_158d0001576456
      click_type: single
  action:
    service_template: >
      {% if is_state('switch.wall_switch_ln_158d0001c2b51e', 'on') or is_state('light.georges_bedside_lamp', 'on') or is_state('light.vivians_bedside_lamp', 'on') -%}
        homeassistant.turn_off
      {% elif (now().hour | int > 8) and (now().hour | int < 19) %}
        homeassistant.turn_on
      {% elif (now().hour | int > 18) or (now().hour | int < 9) %}
        light.turn_on
      {% endif %}
    data_template: 
      entity_id: >-
        {%- if is_state('switch.wall_switch_ln_158d0001f987c2', 'on') or is_state('light.floor_lamp', 'on') or is_state('light.table_lamp', 'on') -%}
          group.bedroomlights
        {%- elif (now().hour | int > 8) and (now().hour | int < 19) -%}
          group.bedroomambientlights
        {%- elif (now().hour | int > 18) or (now().hour | int < 9) -%}
          light.bed_ambient_light
        {%- endif -%}

And when firing the click event_type through the “Events” menu in Developer tools everything work like a charm.

THE PROBLEM:

When I am trying to actually use the automation in every-day life by hitting the wall switch it doesn’t work. The reason it doesn’t work according to HA’s log is the following:

Unsupported click_type detected: long_click
10:03 AM components/binary_sensor/xiaomi_aqara.py (WARNING)

From what I’ve seen on the documentation this type of aqara binary_sensor only reports ‘click’. So I cannot understand how it manages to report a long_click. Could it be a bug?

Thanks for any help.
Widely appreciated.