Zemismart ZMR4 on Z2M

[Luks017]

Hi Everyone,

Need to preface this with I am fairly new to HA and Z2M.

I have purchased a couple Zemismart ZMR4 wireless switches and can’t seem to get them to work. Z2M showing these as compatible but under a different model identifier: Zemismart ZMR4 control via MQTT | Zigbee2MQTT

The model of my switches is: _TZ3000_et7afzxz and not ‘_TZ3000_11pg3ima’ as defined in the Herdsman Converters.

Any help would be extremely appreciated.

[smartmatic]

I’ve successfully added the switch via Z2M to HA but the button events doesn’t work at the moment. There is an open issue on Github.
https://github.com/Koenkk/zigbee2mqtt/issues/23187

[Silvermane]

I’ve just received my ZMR4’s and I believe the latest Z2M has fixed the issue. Events are coming through nicely for single, double click and hold features. Would be great if there was a blueprint to manage the device though as opposed to having to do my own automations from scratch

EDIT:
Nevermind, This is probably a better way to go rather than using a blueprint and quite straightforward to accomplish:

Aqara Buttons All-In-One [Zigbee2MQTT]

I would advise everyone to use a more modern and native way to bind actions on buttons without any blueprints: Create new empty automation. In Triggers section add the “Device”. Select device and trigger you need (e.g. “single” action) and set Trigger ID (e.g. “single”) by clicking “Edit ID” in dots menu. Repeat step 2 for each trigger type you need (double, hold, etc…) [image] In Actions section add “Choose” action. In “Option 1” add “Triggered by” condition and select trigger you need (e…

[alsalvad (André Salvador)]

I spent a few hours struggling to get automations to work with a single click using the ZMR4, but by default, this switch only offers triggers based on state changes.

Then I had a moment of enlightenment, and a long-lost neuron in my brain reminded me to check all the events in the Developer Tools.

In Listen to events, I entered * to listen to all events.
When I clicked the button, the following event was registered:

event_type: localtuya_device_dp_triggered
data:
  device_id: abc123456
  dp: "1"
  value: single_click
origin: LOCAL
time_fired: "2025-06-03T02:24:24.967031+00:00"
context:
  id: 01JWSSNBW77608EEV96T23B94S
  parent_id: null
  user_id: null

From that point on, it became very clear what I needed to do: create automations that listen for the localtuya_device_dp_triggered event.

Here’s the YAML for my automation:

alias: Single click living room button
description: Responds to button 1 (living room) via LocalTuya event
triggers:
  - event_type: localtuya_device_dp_triggered
    event_data:
      dp: "1"
      value: single_click
      device_id: abc123456
    trigger: event
conditions: []
actions:
  - target:
      entity_id: light.living_room_1
    action: light.toggle
    data: {}
mode: single

Here, "dp" refers to the button. To create an automation for other buttons, just specify the corresponding number.

Extremely simple and effective.
I hope this helps anyone looking for a solution!