Incorrect button position mapping in SNZB‑01M (R5) when used in eWeLink Remote mode via MQTT

Ideas & Suggestion Free discussion
1

@Daniel_Zhan Another issue that could just as well be reported to Sonoff as to eWeLink. @MichaelLearnsToCode I trust that the eWeLink Team will guide it further. I would like to report an issue with the Sonoff SNZB‑01M (R5) remote when used in eWeLink Remote mode and integrated with Home Assistant (eWeLink Remote add-on) via MQTT.
The device publishes events with incorrect button position descriptions. These descriptions appear to be inherited from the older R5 firmware, which had a different physical layout.

As a result, the MQTT Discovery entries generated by the device contain wrong button names, which leads to confusion and incorrect automations on the Home Assistant side.

Below is the exact mapping problem.

Incorrect event → position mapping

  1. event.cube_ha_ewelink_remote_addon_bebb61aa_multi_press_1 is reported as: top right.
    Correct: one dot (or simply “top right” if using positional naming)
    Status: Acceptable, though naming could be more consistent.

  2. event.cube_ha_ewelink_remote_addon_bebb61aa_multi_press_2 is reported as: top centre

Problem: The SNZB‑01M has two buttons in the top row, not three. There is no top centre button on this device.
Correct: top left (two dots)

  1. event.cube_ha_ewelink_remote_addon_bebb61aa_multi_press_3 is reported as: top right

Correct: bottom left (three dots)

  1. event.cube_ha_ewelink_remote_addon_bebb61aa_multi_press_4 is reported as: bottom left

Correct: bottom right (four dots)

Summary of the issue
The button descriptions published via MQTT do not match the physical layout of the SNZB‑01M.
This causes:

  • incorrect labels in Home Assistant’s MQTT device card
  • confusion when creating automations
  • inconsistent behavior between eWeLink Cloud mode (correct) and eWeLink Remote mode (incorrect)

Evidence suggesting the mapping was copied from the older R5 remote firmware, which had a different button arrangement.

Expected behavior
The SNZB‑01M should publish correct button position names for all four buttons when operating in eWeLink Remote mode, matching:

Event ID Correct Position Dot Symbol
1 Top Right ●
2 Top Left ●●
3 Bottom Left ●●●
4 Bottom Right ●●●●

Additional notes:
In eWeLink Cloud mode, the button names are correct. The issue appears only in eWeLink Remote → MQTT mode. Fixing the MQTT mapping would greatly improve integration with Home Assistant and prevent user confusion.

2

Sonoff SNZB‑01M (R5)? This is new. Why is there any connection between SNZB‑01M and SONOFF R5? I thought they are two different products. Let me check with SONOFF staff first.

3

yi.liu Staff of eWeLink explained this:

At the moment, the SNZB-01M reuses the same protocol as the R5, so a few known limitations may occur:
1. The 01M has only 4 buttons, while the R5 has 6. As a result, the Remote Gateway may show two extra, non-functional buttons.
2. The 01M supports triple-click, but the R5 does not, so the Remote Gateway won’t be able to recognize triple-click events.
Unfortunately, this can’t be fixed on the gateway side, because we can’t distinguish whether the device is an 01M or an R5.

4

Oh my god :scream:

5

Indeed :slight_smile:
That is why I spent some time working with this and I was able to finally have it useful: Sonoff R5 – eWeLink Remote (MQTT) — Full 6‑Button Blueprint - Ideas & Suggestion - eWeLink Forum. Look for the Here is the dedicated blueprint for SNZB‑01M section.

2 Likes