Broadlink RM Pro + Livolo Switches + RF learning woes

Using the IHC app from broadlink I could see a different name on both RMPRO. one is called rmpro/pro+ and have v30 as the latest firmware and other is called just rmpro and have v20028 as the latest firmware. Chinese hardware made by different people maybe!!!
And a last thought: give up Livolo switches. They are not that good for the job.

Yes, I give up livolo. Move to sonoff T1. At least I got the neutral line finally.

Those without neutral line using xiaomi aqara.

what you will recommend instead livolo

Sonoff T1 or any other with a WiFi chip, generally all WiFi switches use the same WiFi chip, but they have different prices and different finish styles.
Sonoff T1 are the cheapest and they are not that ugly, despite the blue waves symboll front printed
You will have feedback when manually switched and could link with Google home or Alexa.

1 Like

Hi all,

Thanks for your great input. I thought I will never manage my two gang Livolo switches because of the problem with the one remote scene support.

But here is my workaround which works so far pretty good. My setup is:

2x 1-Gang 2-Way VL-c701sr
1x 2-Gang 2-Way VL-c702r
2x Remote Controls (4 Buttons a,b,c,d)

Broadlink + Iobroker + alexa

I tried all the setups from all your replies, but nevertheless it never worked as I liked. I wanted to control all switches manually and with Alexa voice commands. My requirements were two control each switch separately and turn all on or off. The only problem was everytime the Toogle All On scene as everybody described here.

My first workaround to avoid the unknown state for the toggle on was to toggle at first all switches off with the one button and after that turn all switches one by one in a Iobroker scene. Sometimes it worked sometimes not and it was really frustrating. After that I tried blocky scripts to set the states on different conditions, but still no luck.

So what I did was:

Step one

  1. Reseted all switches
  2. Switch 1 learned Button Remote1 A
  3. Switch 2 learned Button Remote1 B
  4. Switch 3 learned Button Remote1 C
  5. Button Remote1 D is automatically only toggle only all off

Step two

  1. Learned RF Code Button Remote2 A to broadlink
  2. Switch 1 learned/sensed RF Code Button Remote2 A from Broadlink
  3. Switch 2 learned/sensed RF Code Button Remote2 A from Broadlink
  4. Switch 3 learned/sensed RF Code Button Remote2 A from Broadlink

I managed the new scene in Iobroker but think it can also be done in e-control or ihc…

The Toggle All Off is clear and send only the Remote1 D. For the Toggle All On i send the Remote1 D and After that the RF learned Code Button Remote2 A. This will turn all on lights and nevertheless if the are in different states. Hope you all understand what I try and can maybe help someone with the same issues which I had.

The big problem about sonoff T1 is that they don’t have 2-way. What is the option for these cases? What about the plate 3x3 that livolo has?

In fact you won’t need a 2-way hardware!!!

Once you have feedback even when manually state changed, you can create automation to simulate 2-way. You can simple put another T1 wired just with Line and Neutral and create 3, 4, 5, 6 ways by automating another T1 when you change this T1 state… Got it?

tasmota can even trigger another switch from one switch without mqtt server. Just wifi will work

Hi.

It’s very long time that anyone was here. But I hope that anyone here will help me …
I searched the internet for many hours but didn’t find a solution:

Is ist possible to teach the livolo switch a separate button of the remote for on and off?
Let’s say button A for on and button B for off?

I’m only able to teach the button A for toggle.

Many many thanks in advance for any help :slightly_smiling_face:

Hi all,

I know I’m late to the party, but being lazy by nature instead of having to generate a lot of rf codes for all my switches and write the config, I build a small app to do that for me. The app allows you to add your switches (1/2/3 gangs), name each gang and then create the HA config based on some random remote id. It generates entries for the scripts that send the codes to the broadlink remote, lights and binary switches to keep the last known state of the switch.

App can be found here: https://kind3r.github.io/livolo-rf-codes/ and the code is also available on GitHub.

Feedback is welcome.

EDIT: Added support for dimmers

2 Likes

@kind3r I would like to ask you for an assistance. I try to use your recommended steps of your script tutorial but I found a problem.
When I tried to Copy & Paste code in step 2 to my configuration.yaml there is an error.

duplicated mapping key at line 104, column -2103:
script:
^
How to fix it please?
Thank you.
My Home Assistant version 0.105.3

Hi @tyjtyj, @kind3r, (and all others :D)

I just started playing with HA after struggling for some years with Livolo RF + Broadlink combo, your work here saved me; congrats! the command generator works wonders when it comes to reliability, seems (from initial testing) to be as reliable as Livolo RF remote.

But I quickly ran into an issue :(, while the codes work on an older RMPro device, they do not work with a RM4Pro device; The codes are ignored by RM4Pro (no LED); if I try to learn a livolo code, it looks very different (a lot longer) - but using those learned codes is not reliable at all.

Do you guys know how to adapt the codes to work on a RM4Pro device?

Thanks a ton!

The codes produced by the script are exactly what the livolo remotes produce with no RF interference. As such it’s not an issue of the codes, but what RMPro4 expects as an input format.

So it’s either a case of the broadlink HA plugin needing an update to work with the new RMPro, or reverse engineering the code format of the RMPro and write a conversion script.

Can you post some of the codes that were produced by the new RMPro when you tried to copy the livolo remote codes to see what they look like? Maybe it turns out to be a simple encoding issue.

This is a very very VERY late reply, but yes you can do what you want by assigning scene buttons to light switches instread of the plain toggle ones. Generate them using the script above as you get (if I recall correctly) only 4 scenes per remote, which means you can control only two switches for every remote (2 scenes for on, and 2 for off)

Thanks a lot for the reply!

My best guess is that the “header” portion is different on RM4 Pro devices. HA works with RM4 though, as the examples provided in the HA documentation are accepted.

Commands accepted by RMPro (from the HA integration docs):

* 26001c001d1d1c1e381e1c1e1b1e1c1d1d3a1c1d1c1e1c1d1c1f1b1e1c000d05000000000000000000000000
* 26001a001c1e391e1b1e1c1d1c1e1d1d1c3a1e1b1d1d1d1d393a1c000d050000000000000000000000000000

Vs generated commands for livolo:
* b2802600130606060606060c0c0c060606060c0c0c06060c0606060606060c0c060606060606060606060000
* b2802600130606060606060c0c0c060606060c0c0c06060c0606060606060c0c0c0c06060606060600000000

Vs learned commands:
* b1c0b004ce9e06000b040605060506040605060506090c04060a0b0a060506050604060506040605060505051305050b0b0505060505050605050506050b0a06050a0b0b050506050506050505060505060505061205050b0b0505060505050605050506050b0a06050b0a0b050506050505060506050505060505061205050b0b0505060505050605060505050b0a06050a0b0b050506050506050506050505060505061205050b0b0505060505050605050605050b0a06050b0a0b050506050506050506050505060505061205050b0a0605060505050605060505050b0a06050b0a0b050506050506050506050505060505061205050b0b0505060505050605060505050b0a06050b0a0b050506050506050506050505060505061205050b0b0505060505050605050605050b0a06050a0b0b050506050505060505060505060505061205050b0b0505060505050605050605050b0a06050a0b0b050506050505060506050505060505061205050b0b0505060505050605050605050b0a06050a0b0b050506050506050506050505060505061205050b0b0505060505050605050605050b0a06050b0a0b050506050505060506050505060505061205050b0a0605060505050605050605050b0a06050b0a0b050506050505060506050505060505051305050b0b0505060505050605050605050b0a06050b0a0b050506050505060506050505060505061205050b0b0505060505050605050506050b0a06050b0a0b050506050505060506050505060505051305050b0a0605060505050605050506050b0a06050a0b0b050506050506050506050505060505061205050b0b0505060505050605050506050b0a06050a0b0b050506050505060505060505060505061205050b0b0505060505050605050605050a0b06050a0b0b050506050505060505060505060505061205050b0b0505050605050605050506050a0b06050a0b0a060506050505060505060505060505061205050b0a0605050605050605050506050a0b06050a0b0a060506050505060505060505060505051305050b0a0605050605050605050506050a0b06050a0b0a060506050505060505060505060505051305050b0a0605050605050506050506050a0b06050a0b0a060506040605060505050605060505051305050b0a0605050506050506050506050a0b06050a0b0a060505050605060505050605060505051305050b0a0605050506050506050506050a0b05060a0b0a060506050505060505050605060505051305050a0b0605050506050506050506050a0b05060a0b0a060505060505060505050605060505051206050a0b0605050506050506050506050a0b05060a0b0a060505050605060505050605050605051305050b0a0605050506050505060505060a0b05060a0b0a060505050605060505050605050605051206050a0b0605050506050505060505060a0b05050b0b0a060505050605050605050605050506051206050a0b0605050506050505060505060a0b05050b0b0a060505050605050506050605050506051206050a0b0506050506050505060505050b0b05050b0b0a050605050605050605050605050505061206050a0b0506050506050505060505050b0b05050b0a0b06050505060505060505050605050506
* b1c0b004ec9e06000d0505050605050506050605050a0b05060a0b0a060506050505060506040605060505051305060a0b0505060505050605060406050b0a06050a0b0b050506050506050506050506050505061206040b0b0505060505050605060406050b0a06050b0a0b050506050506050505060505060505061206040b0b0505060506040605060505050b0b05050b0a0b050605050605050506050506050505061206050a0b0505060506040605060505050b0b05050b0a0b050605050605050605050605050506051206050a0b0505060506050505060505050b0b05050b0a0b050605050605050506050605050506051206050a0b0506050506050505060505060a0b05050b0a0b060505050605050605050605050506051206050a0b0605050506050505060505060a0b05060a0b0a060505050605060505050605050506051206050a0b0605050506050505060505060a0b05050b0b0a060505050605050605050605050605051206050a0b0506050506050505060506040b0b05050b0b0a060505050605050605050605050605051206050b0a0506050506050505060505060a0b05050b0b0a060505050605050605050605050506051206050a0b0506050506050505060506050a0b05050b0a0b060505050605050605050605050506051206050a0b0506050506050505060505060a0b05050b0b0a060505050605050506050605050506051206050a0b0506050506050505060505060a0b05050b0b0a060505050605060406050605050506051206050a0b0506050506050505060505060a0b05050b0b0a060505050605060406050605050505061206050a0b0605050506050505060505060a0b05050b0a0b060505050605050506050605050506051206050a0b0604060506050505060505050b0b05050b0b0a050605050605050605050605050506051206050a0b0506050506050505060505060a0b05050b0a0b060505050605050605050605050506051206050a0b0506050506050505060505060a0b05050b0a0b050605050605050506050506050506051205060a0b0506050506050505060505050b0b05050b0a0b050605050605050506050506050505061205060a0b0506050505060505060505050b0b05050b0a0b050605050506050506050506050505061205060a0b0505060505060505060505050b0a06050b0a0b050506050506050506050506050505061205050b0b0505060505060505060505050b0a06050b0a0b050506050506050506050505060505061205050b0b0505060505050605050605050b0a06050b0a0b050506050506050505060505060505061205050b0b0505060505050605050605050b0a06050a0b0b050506050505060506050505060505061205050b0a0605050605050605050605050b0a06050a0b0b050506050505060506050505060505051305050b0a0605060505050605050605050b0a06050a0b0b050506050505060505060505060505051305050b0a0605060505050605050506050b0a06050a0b0a060506050505060505060505060505051305050b0a0605060406050605050506050b0a06050a0b0a060506050505060505050605060505051305050b0a0605050605050605050506050a0b06050a0b0b05050605050506050505060506050505

PS: Wow, community support seems excellent here! :slight_smile:

PPS: @kind3r it seems that the generated config is no longer fully compatible with HA (version Home Assistant 2021.4.5) I get “extra keys not allowed @ data[‘packet’]” error when trying to use ON/OFF commands.

Weird, I thought I updated the config generation when they made the change … seems not. Can you try now (reload the page etc.) ?

Also, about the RM4pro, maybe someone can lookup some specs about the packet format, if it indeed changed and it wasn’t just the config issue. At a first glance looks about the same, just repeating the sequece.

Thank you @kind3r, I’ve reloaded the page and it seems to have a configuration similar to toggle commands, I did not try it but I don’t see why it wouldn’t work.

All I could find about RM4 are these things:

But I am very unfamiliar with these libs so I did not manage to extract anything very useful.

A bit offtopic here: I’ve seen than Broadlink added “official” support for livolo in their (newer) “Broadlink” app - the codes seem a lot more reliable; however I could not find a way (yet) to get them out of the app (iOS version); I tried capturing the traffic with Charles but did not see anything interesting. I wonder if we could find a way to access their “database” and maybe import the config directly in HA.

I’ve seen some posts about eControl/IHC on the web, but nothing related to “Broadlink” app.

Hmm, I think I found something useful about RM4 family support: Add support for 0x5f36 devices and RM4 series (#317) · mjg59/python-broadlink@1a1169f · GitHub

Particularly this line: Add support for 0x5f36 devices and RM4 series (#317) · mjg59/python-broadlink@1a1169f · GitHub

Just for posterity…

Which country do you live in? Where did you buy your livolos from and where did you buy your rm4pro from?

Chinese versions operate on different RF MHz than european/us ones. If you bought the RM4 from ali express it supports both frequences, but if you got it off amazon then it supports only the eu/us ones. Similarly, I suspect that the livolo switches operate on different frequencies depending on the country they are targeted for.

Might be the issue, but it’s a shot in the dark

I’m in Romania; regarding the switches/RM remote - don’t really remember; I bought some of them from Ali, some from local distributors - hard to say. I can probably check the product codes, maybe I can find out more about them.