Broadlink RM-PRO and A1 sensor

Feature Requests
4

and what about the A1 multi sensor? is it possible receiving data using the bridge?

and @Danielhiversen, I got the SDK from Broadlink! Is it enough?

5

The bridge only works for RM devices.They have an API(kind of) here
http://rm-bridge.fun2code.de/

6

I also used the bridge on another automation project I have, with a spare phone and it works.

I only recently found about home assistant and I’m trying to wrap my head how to use the bridge with home assistant.

can you elaborate please about how you made it work?

7

You can create an MQTT switch and push a msg to using the tasker plugin or the bridge.

8

Has anyone tried using an MQTT switch? wondering what the delay would be.

Also has anyone had any luck intergrating somfy RTS blinds into the Broadlink RM Pro? I can’t seem to find a straight answer for this anywhere.

9

For what it is worth I have been using the RM pro as well as some broadlink plug switches with this android bridge:

Although the app was written to be a tasker plugin, it also has the bridge capability (and there is some good documentation on how to use it via the http interface)

Have a look at this topic for an example of reading the temperature from the RM pro:

The API in the bridge allows for reading data from the A1 sensor (havent tried it yet) and the dev plans to support the S1 device in an upcoming update (I am looking forward to that one as I already have a bunch of sensors).

I have only been using it for a couple of weeks and haven’t had much issues with it so far (sometimes a little lag sending commands but that is the same lag as the official Broadlink software).

As for the price of the app - it is worth it in my opinion.

10

Hello community.

Here is converted version for python3.5 of broadlink-python api: http://pastebin.com/accU8VX4
Here is sample sensor for temperature on broadlink rm2 pro: http://pastebin.com/A8emAbPv

Sorry but I have no time now to develop switches and etc. If someone have interest to develop, fell free to use this code.

And sorry for my bad English!

1 Like
11

Does this need to Android app or is standalone?

12

No not need, its standalone. Perhaps next month I will have free time and If nobody not start develops components, I will do.

Link to original mdule: https://github.com/mjg59/python-broadlink
It’s use MIT license, but this code is for python2. I change code for Python3 see upper post.

13

Thanks… finally some great news…

Is there some dummies way for using RM2 and A1 on HASS?
How long until we get a full integration on HASS interface such as…

…

Example configuration.yaml entry

broadlink:

  • device: ‘RM2’
    host ip: 999.999.9.999
  • device: ‘A1’
    host ip: 999.999.9.999

Will it be possible???
Thanks

1 Like
14

This example is not possible but I think possible will be:

broadlink:

  • device: ‘RM2’
    host: 999.999.999.999
    mac: xx:xx:xx:xx:xx
    name: ‘TV On’
    ir_packet: ‘packet’

Ok, I’m almost done sensor component. Tomorrow I will upload it.

4 Likes
15

Awesome!!!

16

Here is sensor.

Please, test it.

Support only RM2 Pro (Read data from temperature sensor) and EAIR A1 (Temperature, Noise and etc.)

Next is switch for IR commands but there will be a problem because there is no push button in home assistant… Switch is not good idea for IR or RF remote commands

2 Likes
17

I will buy EAIR (I only hve RM2 pro).
At the moment I use the command below to activate Broadlink RM2 Pro RF command (on hardware electric swtiches) and works perfectly. I have still to test IR

switch:
  platform: command_line
  switches:
    platter11_light:
      command_on: "curl -X GET http://192.168.1.50:7474/?cmd=%7B%2...."
      command_off: "curl -X GET http://192.168.1.50:7474/?cmd=%7B%22...."
18

I don’t understand whats is wrong with code and why not passed tests in GITHUB. Wow.
I apologize but until now I did not use GitHub

19

Thanks very much for that…
Finally awesome!
Could not test yet because I am not home…

About the RF and IR sending capability… I think we could use a assumed_state switch. We could set two different commands for the same switch, such as POWER ON OFF, VOL UP DOWN, CHANNEL UP DOWN.

Besides, we do not need a graphical interface for remote controls, we just need integrate IR and RF commands on automation actions… we already have the e-control interface for that…which is very limited…

There is no need having a switch or a button on the UI, Just the possibility of turning the tv off if left on with nobody home… or turning the AC on a preset cold or hot based on the room temperature…

But need would like to abandon the Android bridge need…

20

but how to get status?

21

but how to get status?

Impossible!
Unfortunately I think use switch is not a good idea. Better would be if there was a button.
All remote controls have buttons not switches :slight_smile:

22

In fact, there is no way to get status back from any IR device, unless you look at it, or check a sensor status changing, such as, turn on AC and check for the temperature variation…

On the other hand, we have RF devices as well, which can inform status or not. Most of them do not inform their status, therefore we need to use different RF signals for turning ON and OFF, what allows sending two or three times the same ON or OFF signal to make sure it had worked.
A RF device with toggle commands is useless for automation rules.

But that is a Whole RF/IR World problem!!!

For RF devices we have better alternatives, such as RFXTRX and RFLINK (which is already being added on HASS).

But for IR devices, Broadlink seems to be the best cost-benefit.

I think the problem about push, switch or assumed_state buttons should be solved later by creating a push button on HASS.

The best step forward will be let us free from android bridge.

The best way to control a IR device is and will allways be using the original remote control.
If we could just send a broadlink IR command throught as an automation action, would already be awesome!!! Even without a push button on the user interface.

23

I have a plenty of Livolo Switches (RF controlled with Toggle Button and OFF button - there is no ON Button), which I have controlled using switches.
I need two virtual switches for each lamp. One is toggle and the other is OFF.
The frontend interface is far from ideal, but it works… when everybody is out of home, I can turn all lights off (for sure) sending a toggle command twice for the OFF switches (I send twice to be sure it will work), and when Kodi pauses, I send a toggle command for the switch I want just once (sometimes it does not work).