Sonoff RM433 remote

[iz3man]

I purchased this RM433 Sonoff remote with 8 buttons in the hope that i could match this to any 8 functions in home assistant.
I got also an RF-gateway and the Sonoff bridge flashed with tasmota.
But when i press any button it sends the very same code for all of them.
Any idea how to use it, or make it suitable for my usage?

https://www.itead.cc/sonoff-rm433-remote-controller-base.html

[iz3man]

Ok. Just answered this to myself. I did a mosquitto_sub and this showed some little difference between the codes (and of course that’s enough to distinguish between them):

{"time" : "2019-06-14 15:06:00", "model" : "Smoke detector GS 558", "id" : 29, "unit" : 15, "learn" : 0, "code" : "c003af"}

c003af
2019-06-14 15:06:00
15
0
29
{"time" : "2019-06-14 15:06:02", "model" : "Smoke detector GS 558", "id" : 29, "unit" : 15, "learn" : 0, "code" : "a003af"}

a003af
2019-06-14 15:06:02
15
0
29

[bpmittal]

i am also having a remote from i ifan03 , how can we use for other entities in HA ?

what type of rf receiver can i use to make it work ?

[camnop (DCS)]

@iz3man How did u make this work?

I have a RM broadlink gateway… But I think it just learn the IR from sonoff remote control… it dont look that… some how… it will always know that I press some button on sonoff remote control…

So… when you press some button, who listen? And how it listen in HA? Is it using the gateway or the bridge?

Thanks a lot!

[iz3man]

@camnop I’m sorry. But I couldn’t even remember my posts Ditched that remote loooooong ago. Sorry can’t help.

[Mahko_Mahko]

I’m pretty sure what you are saying is right.

I think the Broadlinks can only learn and send commands. They can’t continuously listen for them. I found my Broadlink RM pro+ could learn and send a large variety of RF codes.

The Sonoff RF bridge can learn, listen and send RF commands. However my experience was it could handle fewer protocols, and depends on what firmware you have flashed. It seems good at learning most cheap RF remote codes.

I have both and use them for different purposes.

[camnop (DCS)]

@Mahko_Mahko

Sonoff RF bridge

That’s what I was saying! You were very clear, thanks!!

Do you know if I can use Sonoff RF bridge with my sonoff door sensor (RF) and my sonoff motion sensor (RF)?

I made a mistake buying these devices… I thought it would be WIFI or Zigbee… but it is RF and I’m not using it since I have bought them.

[francisp (Francis)]

@camnop

Do you know if I can use Sonoff RF bridge with my sonoff door sensor (RF) and my sonoff motion sensor (RF)?

Yes, you can.

[Viking]

Hi All,
I have flashed my Sonoff RF Bridge with Tasmota (latest version) and Portisch, and it works perfect and the bridge correctly picks up the 433MHz data from various devices from different manufactures that I have.
However, it seems totally blind to the Sonoff RM433 remote control. When I click a button on the remote, there’s absolutely no response at all from the Bridge. I know the remote works, cause I’m using it to control a Sonoff D1. But even though the remote has been paired with the D1, shouldn’t its 433MHZ communication still be visible for the Bridge to pick up?

[Mahko_Mahko]

Are there tolerance/idle/filter settings you can tweak?

Like this? Sorry for image, on my mobile.

[Viking]

@Mahko_Mahko - was your latest post intended to be info for me?
If so, I need much more information as what is this, where does it appear, and what should the expected result be?

[Mahko_Mahko]

Yes, for you. I see I missed mentioning the details I provided are ESPHOME examples and config.

With ESPHome, you can tweak some receiver settings which can affect what codes are recieved/logged.

Changing these settings can make previously invisible codes appear in the ESPHome logs.

So I wondered if Tasmota had something similar, and if you’ve tried tweaking them?

The ESPHOME settings are described here:

Remote Receiver

[Viking]

Thanks, I will try this when I get back home next week.
I’ll be in touch.

[Mahko_Mahko]

@iz3man

RM433 Sonoff remote

By the way, I also have a RM433 Sonoff remote. My DIY reciever can hear the signals with those settings I screenshotted a few posts up.

Sonoff RF Bridge with ESPHOME?

I moved off my hardware hacked Sonoff RF Bridge and onto these connected to an ESP32 after I hit up against limits in number of codes I could watch/send. Very happy with it so far. I also hooked up and LED and an RTTL buzzer to it. I have it beep when I hit buttons on my 433mhz remotes so that I know it’s “been sent and heard”… I tried a few ESp32’s I had and it became really solid when I used a Quinled. I left it kind of exposed deliberately - it’s my “RF bug”… [image] substitutions: …

I recall my old hardware hacked Sonoff Bridge running ESPHome could pick up the remote signals too. Can’t recall if the settings were the same or different.

[Viking]

Well, since my RF Bridge does not use ESPHome, but insted Tasmota - I do not see how I can learn from your example unless I reflash the whole thing with ESPHome.
The only Tasmota command I am aware of that directly affects the device’s ability to pick up signals, are the rfraw 166 and the rfraw 177 commands.
I use rfraw 166 mode to communicate with all my other 433MHz devices. But in this mode, the RM433 remote is “invisible”.
However, if I change to rfraw 177 mode, i get the following result when pressing various keys on the RM433 remote:

20:43:13.434 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:13","RfRaw":{"Data":"AA B1 03 02EE 00FA 1DA6 28181819090819090908190908181819081909090908190909 55"}}
20:43:23.041 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:23","RfRaw":{"Data":"AA B1 04 02E4 0104 00BE 1DA6 3818181A090819090908190908181819081909090908190909 55"}}
20:43:23.136 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:23","RfRaw":{"Data":"AA B1 03 030C 00C8 1DB0 28181819090819090908190908181819081909090908190909 55"}}
20:43:32.786 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:32","RfRaw":{"Data":"AA B1 04 02D0 010E 00B4 1D9C 3818181A09081A090908190908181819081909090819090819 55"}}
20:43:32.880 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:32","RfRaw":{"Data":"AA B1 03 0302 00C8 1D9C 28181819090819090908190908181819081909090819090819 55"}}
20:43:43.965 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:43","RfRaw":{"Data":"AA B1 04 02D0 010E 00B4 1D9C 3818181A0A081A090908190908181819081909090819090819 55"}}
20:43:44.058 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:44","RfRaw":{"Data":"AA B1 03 0302 00D2 1DA6 28181819090819090908190908181819081909090819090819 55"}}
20:43:53.397 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:43:53","RfRaw":{"Data":"AA B1 03 02C6 010E 1DB0 28181819090819090908190908181819081909090818190909 55"}}
20:44:01.032 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:44:01","RfRaw":{"Data":"AA B1 03 02DA 010E 1DB0 28181819090819090908190908181819081909090818190909 55"}}
20:44:11.644 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:44:11","RfRaw":{"Data":"AA B1 04 02DA 0104 00BE 1DB0 3818181A09081A0A0A081A0A0818181A081A09090909081819 55"}}
20:44:11.739 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:44:11","RfRaw":{"Data":"AA B1 03 030C 00C8 1DB0 28181819090819090908190908181819081909090909081819 55"}}
20:44:16.124 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-23T20:44:16","RfRaw":{"Data":"AA B1 04 02E4 00FA 00AA 1DA6 3818181909081A0909081A090818181A081909090909081819 55"}}

In rfraw 177 mode, the bridge picks up anything it detects within the 433MHZ band, including noise and random signals. But in this mode, all my other devices stops working. And the data shown above, is most probably coming fro the RM433, but for me it’s impossible to decode and understand them, let alone trying to put them to good use as long as they are undiscoverable in rfraw 166 mode.

[Mahko_Mahko]

@Viking

RM433

In 177 mode, if you push a single button 10 times and adopt the most consistent, does it work as expected?

If you do the same with relearning one of your old devices in 177 mode, does that work?

[Viking]

I’m not sure what you mean by “does it work as expected”?
As I do not know what to expect. If I press 10 times on a button on the RM433 remote, this is the result:

09:18:38.543 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:18:38","RfRaw":{"Data":"AA B1 03 02E4 00FA 1D9C 28181819090819090908190908181819081909090819090909 55"}}
09:18:50.851 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:18:50","RfRaw":{"Data":"AA B1 03 02E4 00FA 1D9C 28181819090819090908190908181819081909090819090909 55"}}
09:18:53.054 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:18:53","RfRaw":{"Data":"AA B1 03 02EE 00FA 1D92 28181819090819090908190908181819081909090819090909 55"}}
09:18:55.393 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:18:55","RfRaw":{"Data":"AA B1 03 02E4 00FA 1D9C 28181819090819090908190908181819081909090819090909 55"}}
09:18:57.746 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:18:57","RfRaw":{"Data":"AA B1 03 02E4 00FA 1D9C 28181819090819090908190908181819081909090819090909 55"}}
09:19:00.138 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:19:00","RfRaw":{"Data":"AA B1 03 02DA 0104 1D9C 28181819090819090908190908181819081909090819090909 55"}}
09:19:05.189 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:19:05","RfRaw":{"Data":"AA B1 03 02DA 00FA 1D9C 28181819090819090908190908181819081909090819090909 55"}}
09:19:10.148 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:19:10","RfRaw":{"Data":"AA B1 03 02EE 00E6 1D92 28181819090819090908190908181819081909090819090909 55"}}
09:19:12.543 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:19:12","RfRaw":{"Data":"AA B1 03 02E4 00F0 1D9C 28181819090819090908190908181819081909090819090909 55"}}
09:19:17.288 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:19:17","RfRaw":{"Data":"AA B1 03 02E4 00F0 1D92 28181819090819090908190908181819081909090819090909 55"}}

If I do the same with one of my other 433MHz devices, still running the bridge in rfraw 177 mode, this is the result:

09:25:56.133 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:25:56","RfRaw":{"Data":"AA B1 05 0140 09F6 00BE 04E2 2BF2 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}
09:25:56.626 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:25:56","RfRaw":{"Data":"AA B1 05 015E 09E2 00AA 04CE 2BCA 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}
09:25:58.083 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:25:58","RfRaw":{"Data":"AA B1 05 0140 09F6 00B4 04E2 2BF2 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283828383828382838283828 55"}}
09:26:00.635 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:26:00","RfRaw":{"Data":"AA B1 05 0168 09E2 0096 04C4 2BB6 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}
09:26:01.127 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:26:01","RfRaw":{"Data":"AA B1 05 0168 09D8 00A0 04C4 2BB6 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}
09:26:04.612 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:26:04","RfRaw":{"Data":"AA B1 05 014A 0A00 00B4 04E2 2BF2 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}
09:26:05.107 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:26:05","RfRaw":{"Data":"AA B1 05 015E 09D8 0096 04C4 2BC0 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}
09:26:06.808 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:26:06","RfRaw":{"Data":"AA B1 05 014A 09F6 00BE 04D8 2BE8 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283828383828382838283828 55"}}
09:26:08.960 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:26:08","RfRaw":{"Data":"AA B1 05 015E 09E2 0096 04C4 2BB6 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}
09:26:09.453 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:26:09","RfRaw":{"Data":"AA B1 05 0168 09D8 00A0 04CE 2BC0 481828383828382838282838283828383828382838283828382838282838283838283828382838283828382838283828382838282838283838283828382838283828 55"}}

Just for comparison, if i switch back to mode rfraw 166, then the same “old” device generates these entries when switched 10 times:

09:38:26.996 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:26","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:27.816 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:27","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:31.101 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:31","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:31.923 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:31","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:35.676 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:35","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:36.496 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:36","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:40.503 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:40","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:41.324 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:41","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:45.386 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:45","RfRaw":{"Data":"AAA6050D8E06006055"}}
09:38:46.209 MQT: tele/sonoff_bridge/RESULT = {"Time":"2023-11-24T09:38:46","RfRaw":{"Data":"AAA6050D8E06006055"}}

The above is what I currently use to make the following HA entity, and it works well:

  - binary_sensor:
      name: 'Main Door'
      state_topic: 'tele/sonoff_bridge/RESULT'
      value_template: >-
        {% if value_json.RfRaw.Data == 'AAA6050D8E06006055' %}
          {{'ON'}}
        {% else %}
          {{states('binary_sensor.main_door') | upper}}
        {% endif %}
      device_class: door

But, as mentioned - the RM433 remote is dead silent when the bridge is set to rfraw 166 mode. According to the docs, the rfraw 177 mode is just for testing purpose as the bridge makes no attempt to qualify, or recognize any known pattern is this mode. It just reports any raw data as it sees them - including noise (which I filtered out in the above first two tables).

[Mahko_Mahko]

Seems to me that your firmware can’t recognise and decode the RM433 protocol.
It can clearly see the raw codes.

Perhaps the Portisch firmware doesn’t support the decoding the specific protocol?
I looked back at my old Sonoff RF Bridge config and my ESPHome firmware was able to decode the remote signals with the rc_switch protocol.

  - platform: remote_receiver
    id: sonoffrmc1r1_lighttoggle
    name: "Sonoff Remote Toggle Light"
    rc_switch_raw:
      code: '001001110111001001101000'
      protocol: 1
    filters:
      - delayed_off: 1s

This page makes some mention of the rc-switch library, but my reading is that it somehow doesn’t apply to your Sonoff RF Bridge (?). But then at the bottom of the page it makes reference to a RM433 Remote. I’m not clear how that all works…

RF Communication - Tasmota

I suspect you may need to change firmware if you want to use your remote.

I don’t really know enough about Tasmota or Porisch firmware to offer any more suggestions. I’ve been very happy with ESPHome firmware, but I’ve also since moved off my Sonoff RF Bridge and on to a DIY device - so don’t know the state of play for Sonoff RF Bridge and ESPHome.

Good luck with solving your issue.

Sonoff RF Bridge with ESPHOME?

I moved off my hardware hacked Sonoff RF Bridge and onto these connected to an ESP32 after I hit up against limits in number of codes I could watch/send. Very happy with it so far. I also hooked up and LED and an RTTL buzzer to it. I have it beep when I hit buttons on my 433mhz remotes so that I know it’s “been sent and heard”… I tried a few ESp32’s I had and it became really solid when I used a Quinled. I left it kind of exposed deliberately - it’s my “RF bug”… [image] substitutions: …

[Viking]

Many thanks for your assistance @Mahko_Mahko Even if I’m still far from any success, I’ve learned a lot from you.