Sonoff SNZB‑01M Remote (ZHA) blueprint for HA

Ideas & Suggestion
, ,
1

This blueprint provides full support for the Sonoff SNZB‑01M remote in ZHA, using zha_event for fast and reliable event‑based control. Each of the four physical buttons exposes four different actions:

  • Single press
  • Double press
  • Triple press
  • Long press

This gives you 16 fully customizable actions that can be mapped to anything in Home Assistant.

:inbox_tray: Import Blueprint

Requirements

To use this blueprint, your SNZB‑01M must be supported by the correct ZHA quirk.

Devices based on the FC12 cluster (including the SNZB‑01M) require a custom quirk/script for proper event mapping. Installation instructions are available here:

:backhand_index_pointing_right: Orb 4-In-1-SONOFF Help Center (The document refers to the Orb 4‑in‑1, but the quirk installation process is identical for the SNZB‑01M.)

This blueprint listens for the actual ZHA commands emitted by the device:

  • remote_button_short_press
  • remote_button_double_press
  • remote_button_triple_press
  • remote_button_long_press

If the correct quirk is not applied, these events may not appear or may be mapped incorrectly.

Physical Button Markings

The SNZB‑01M has embossed symbols on each button:

  • Top Left → one dot
  • Top Right → two dots
  • Bottom Left → three dots
  • Bottom Right → four dots

These correspond to endpoints 1–4 in ZHA.

Automation Mode

The blueprint allows selecting the automation mode:

  • queued (default)
  • single
  • restart
  • parallel

To avoid log spam during rapid button presses, the automation uses:

Code

max_exceeded: silent

Compatibility

  • Home Assistant 2024.12+
  • Home Assistant 2025.x
  • Integration: ZHA
  • Device: Sonoff SNZB‑01M (FC12)
  • Requires quirk or native FC12 support

FAQ

Does this blueprint work without installing a quirk?

No. The SNZB‑01M requires a quirk for proper FC12 event mapping. Installation guide: Orb 4-In-1-SONOFF Help Center

How do I check if my device is using the correct quirk?

Go to: Settings → Devices & Services → ZHA → Your SNZB‑01M → Zigbee Information

You should see a quirk name containing FC12 or SNZB‑01M. If it shows ZHAStandardDevice, the quirk is not applied.

Why does the blueprint use zha_event instead of device triggers?

Because the SNZB‑01M does not expose device triggers in ZHA. All actions are emitted as FC12 events.

Can I assign different actions to each button?

Yes — each of the four buttons supports: single, double, triple, and long press → 16 actions total.

Why do I see a simple dropdown instead of a fancy UI selector?

Blueprints based on events (zha_event) do not use the extended UI widgets. This is a frontend limitation, not a YAML issue.

Does the device support long‑press‑hold or repeated events?

No. The SNZB‑01M sends only a single remote_button_long_press event. It does not emit repeated “hold” events.

Is this blueprint compatible with HA 2024.12 / 2025.x?

Yes — fully compatible.

Why do I see logs like “派发 zha_event 成功” when I press a button?

Because your custom ZHA quirk is working correctly. That message literally means “zha_event dispatched successfully”. It is printed by the quirk at the moment it converts a raw Zigbee FC12 report into a Home Assistant zha_event. This is a success message, not an error.

Why is the message in Chinese?

Because the log string comes directly from the quirk source code:

_LOGGER.warning("派发zha_event成功: …")

It’s purely a developer log message, not something generated by ZHA or Home Assistant itself. You can safely translate it as “Successfully dispatched zha_event”.

1 Like
Sonoff R5 – eWeLink Remote (MQTT) — Full 6‑Button Blueprint