Z2M - Various Zigbee Wireless Switch Action

Overview

An easy way for using various zigbee wireless switches

Update 1.0.1;

Compatible with Zigbee2MQTT 2.0.0, while still supporting previous versions.

Prerequisites

  • Ensure all wireless switches are connected to Zigbee2MQTT

Supported Device - (confirmed working)

  • Tuya

  • Sihas

  • Aqara

    • Wireless remote switch T1 (double rocker) - WXKG04LM
      image

    • Wireless mini switch t1 - WXKG13LM
      image

  • Unidentified devices;

    • Even if the device operation cannot be confirmed, it can still be used without modification if triggered by states such as single / x_single / button_x_single in the action sensor.
      (x = 1~4, the numbers of buttons you can tap range from 1 to 4)

User Manual

  1. If you haven’t changed the topic in Zigbee2MQTT, you don’t need to modify the base topic. Leave it as the default(zigbee2mqtt) value.

  2. Type the FRIENDLY NAME of the wireless switch you want to control into the device input.
    2-1. Dropdown selection is not available; manual typing is required.
    2-2. It must be the Friendly Name, not the Entity ID!
    2-3. It’s not certain, but it’s recommended to change the friendly name in Zigbee2MQTT and use that value.

If you’ve arbitrarily changed the friendly name in the Home Assistant UI, it might not work as expected

  1. Create automation actions. Done!

NOTE

  1. The RELEASE action of all buttons DOES NOT WORK
    ( This is because the released event is more suitable to be used as a “wait for trigger” following the hold event, rather than being directly utilized as a trigger.)
  2. The actions of AQARA MINI should only be placed in 1_x_action.
    (x = single, double, hold)
  3. The BOTH CLICK action of Aqara T1 should be placed in 3_x_action.
    (x = single, double, hold)

Blueprint

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

If something seems off, please check my GitHub. Thank you! :blush:

Hi!

This no longer works with v2.0.0 of z2m as sensor action and click have been removed:

Could you please confirm if an update os blueprint fixes?

Kind regards

Had the same issue with another blueprint. I fixed it by enabling home assistant legacy action sensors.

Go to the Z2M add configuration page. Look for the gear wheel (top, toward the right), go to settings then Home Assistant integration and enable Home Assistant legacy action sensors.

I’m wokring on a improved blueprint for 2.0 and gathering different switches to make it usefull for as much people as possible:
take a look: Zigbee2mqtt 2.0 different switches (aqara, opple, ikea)

Hi! I’ve already updated the blueprint, but I forgot to update the “Import” button. :sweat_smile: Please check out my GitHub or Check Button again. Since the behavior has changed, the required fields have been slightly modified. You’ll need to add a Friendly Name now.

Of course, using existing features isn’t a bad thing, but I believe we should avoid relying on legacy functionality! This blueprint does not operate in a legacy or experimental manner. I believe it will continue to work seamlessly even with future updates. :blush:

1 Like