Broadlink/Bestcon RM4C Mini via MQTT

I have the RM4 Pro user guide. It actually doesn’t mention the LED color options. Just the different blinking variations and what they mean.

Thanks, I’ll read the thread and write about my issue. Hopefully someone will be able to help :slight_smile:

the RM4C will be disconnected from internet forever or only when I configure it?

To be able to locally control your device, you must not let it connect to the Broadlink servers. If it connects, local control will no longer work.

If it’s setup for local control, then there is no reason for it to connect to the internet!

thank you for the answer

my router can’t block a single ip to the internet…sob…:frowning:

But that’s OK, I think. If you get the device connected too your local WiFi as described in either method (app or python-broadlink), it won’t try to phone home afterwards.

The message is really a warning for those using the app to connect the device to the local WiFi - if you go to far with the app (further than instructed), the device will contact the Broadlink servers!

I cant get my rmpro to connect via the python-broadlink (not using the app).
How can this be done?
I put the rmpro in AP mode (4 blinks, pause). so it does not register an IP on my wifi network yet. How can the broadlink discovery find it?

  1. The RM4C Mini is now a wifi access point. Connect your computer to the access point (it will probably have Broadlink in the name). It may take a little bit of time for the access point to appear in your wifi list.

the access point that says “broadlinkprov”? I see it, can connect to it, but what next?

Then continue with the next step:

  1. Once connected, in a terminal on your computer, start the python console by typing python3 and hitting enter.

I am connecting my laptop to the broadlink RMPRO. where do I type python3? do I ssh into my openhab ubuntu ?My OH resides in a ubuntu VM in my esxi server

I see.

You’re currently following steps to connect your Broadlink device to your wifi. This has nothing to do with openHAB (yet!). You must follow the instructions using the device which you’ve connected to the Broadlink AP (so your laptop - hopefully you installed python-broadlink onto your laptop?).

Once the Broadlink device has connected to your wifi network you can SSH into your device which runs openHAB, and continue from there. This should become clear when you get to the Install broadlink-mqtt step.

However, you’ve now mentioned an RMPro - @mjeshurun was not successful in using this tutorial with his RM4 Pro - you can see the results just a few posts above when you first joined!

Thank you . It looks like I have to put a wifi adapter and pass it through to my OH vm. And even so, it may not work for the RMPro.

Really? Why? Surely your OH VM is connected to your home network?

Quite. Have you tried using the broadlink binding?

yes, the OH VM is connected to my home network. But I only connect to it via putty, whilst I connect the the RMPRO with either my laptop or my phone to the “Broadlinkprov” wifi - but I have so far failed to connect this way.

I have not tried the broadlink binding as I was attracked to this method which does not call or connect to the Broadlink servers

The broadlink binding does not connect to the broadlink servers either.

I will try the Broadlink binding

I dunno why but even with the newest Broadlink app, I could not connect the RMPro to my wifi network -which I managed to a year ago before i removed it and put it in cold storage.

Hi @hafniumzinc ,
I may have found the reason why I couldn’t learn the RF codes, and I hope you might be able to assist me in solving it.

At one of the posts relating to “device storage is full” @eschava asked me this question:
“What is the value of the device_type parameter in the mqtt.conf or custom.conf files?”

His question made me realize I might have missed a step while trying to use the python-broadlink and broadlink-mqtt solutions you described in your guide.

In both solutions described in your guide, I did not fill my device_type parameters in any file.

For example, this is my device type output I got by using the python-broadlink method, but I didn’t notice I needed to save the device_type data into a special file located in the broadlink_cli folder.

pi@raspberrypi:~/python-broadlink/cli $ ./broadlink_discovery --timeout 10 --dst-ip 192.168.1.6
Discovering...
###########################################
RM4
# broadlink_cli --type 0x61a2 --host 192.168.1.6 --mac 24dfa7b9c689
Device file data (to be used with --device @filename in broadlink_cli) : 
0x61a2 192.168.1.6 24dfa7b9c689
temperature = 0.0

I did the same mistake with the broadlink-mqtt solution. which means I didn’t fill my device type info into the custom.conf file.

It looks like the python-broadlink solution might be easier for noobs like me.
Could I trouble you, @hafniumzinc , to please explain how I should save the device_type info into the python-broadlink broadlink_cli folder, or to add the info into the custom.conf file under broadlink-mqtt?

Sorry in advance for such a noob request :pray::pray:

The device_type parameter in mqtt.conf (or custom.conf) is by default set to lookup, which presumably means that broadlink-mqtt uses whatever python-broadlink discovers automatically as your device type. The extract you give:

pi@raspberrypi:~/python-broadlink/cli $ ./broadlink_discovery --timeout 10 --dst-ip 192.168.1.6
Discovering...
###########################################
RM4

means python-broadlink seems to correctly discover your device type (RM4), and presumably broadlink-mqtt uses that.

I have not changed the device_type parameter in my own broadlink-mqtt configuration files - it’s been left at the default.

1 Like

Thank you for taking the time to check.
Then I really don’t know causes the “device storage is full”. :dizzy_face:

Hi @hafniumzinc

Just wanted to let you know, that with the help of kind people on this thread I now know how to learn commands from RF remotes :))

To make a long story short, I was instructed to use this terminal command in order to start RF learning:
python3 broadlink_cli --device "0x61a2 192.168.1.6 24dfa7b9c689" --rfscanlearn

Could it be the learn command you mentioned in your guide for the python-broadlink method was for IR learning only? devices[0].enter_learning()

1 Like