Multiple Broadlink RM mini 3 integration using MQTT

-
Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this. https://lprhodes.github.io/slate/

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone https://github.com/eschava/broadlink-mqtt

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'

4. Start the python script and check that it started and detected all the RM devices.

Check the log file to see what the IP / MAC addresses are.
DEBUG Connected to RM2 Broadlink device at '192.168.1.101' (MAC 34:ea:34:01:01:01)
DEBUG Connected to RM2 Broadlink device at '192.168.1.102' (MAC 34:ea:34:00:00:00)


5. Record the IR command - substitute the 00_00_00 with the last 3 octets of the mac address for the device. (I haven't tried this yet, as I previously added my commands when I only had 1 RM mini)

mosquitto_pub -h 192.168.1.10 -t broadlink/RM2_00_00_00/aircon/off -m auto


6. Configure Domoticz virtual device to replay the IR command

If the MQTT IP address is 192.168.1.10, the following "On Action" can be used to turn on and off the broadlink virtual switch device created in Domoticz

script:///usr/bin/mosquitto_pub -h 192.168.1.10 -t broadlink/RM2_00_00_00/aircon/on -m auto
script:///usr/bin/mosquitto_pub -h 192.168.1.10 -t broadlink/RM2_00_00_00/aircon/off -m auto


Update to avoid python 2.7 errors, use python3.

$ sudo pip3 install paho-mqtt

and start by

$ python3 /home/pi/broadlink-mqtt/mqtt.py




Comments

wurst said…
hey, nice tutorial, but it doesnt work for me. i am getting
python2.7 mqtt.py
Traceback (most recent call last):
File "mqtt.py", line 533, in
devices = get_device(cf)
File "mqtt.py", line 338, in get_device
return configure_device(devices[0], topic_prefix)
File "mqtt.py", line 384, in configure_device
device.auth()
File "/usr/local/lib/python2.7/dist-packages/broadlink/__init__.py", line 203, in auth
response = self.send_packet(0x65, payload)
File "/usr/local/lib/python2.7/dist-packages/broadlink/__init__.py", line 259, in send_packet
payload = self.encrypt(payload)
File "/usr/local/lib/python2.7/dist-packages/broadlink/__init__.py", line 169, in encrypt
encryptor = self.aes.encryptor()
File "/usr/local/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/base.py", line 121, in encryptor
self.algorithm, self.mode
File "/usr/local/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py", line 303, in create_symmetric_encryption_ctx
return _CipherContext(self, cipher, mode, _CipherContext._ENCRYPT)
File "/usr/local/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/ciphers.py", line 62, in __init__
mode.initialization_vector
TypeError: from_buffer() cannot return the address of the raw string within a str or unicode or bytearray object
6:04 am
Melven said…
use python3 instead. I updated the post at the end.
1:09 pm
Post a Comment

Popular posts from this blog

re-installation and disk management

-
Face it, re-installations are a pain. However, its always a chance to put the best of plans into place and then find out how your plans ended up in the mess. Well, all wasn't lost so far. The original plan was to software raid 1 (2x 120GB disks) the installation. Of course, greed took the better of me and i decided, i'd just use one whole disk as a separate data mount and if i need to backup, cron an rsync between disks. at least I'd have a bit more room to play with. But like that is ever going to happen. Data issues, sigh. Unknown to most people, they normally have at least a terabyte of drive space lying around the house. Think about it. How many computers do you have. How many external firewire, usb drives do you have. Have you recently upgraded and have a couple of disks lying somewhere. And we haven't even started looking at optical media yet. Sometimes, I feel like just getting a NAS with at least a terabyte and not having to worry about it for a year, and I sti...
Read more

Apple is Evil

-
The worse of wars come from the best of intentions. As much as I am an Apple fan, I occasionally get the sinking feeling that my passion in the future will be naught. We all have heard that "windows is evil" more often than any other operating systems. Occasionally we feel that way, which our machines crashing, our data corrupted, virus attacks, etc. Giving it some credit, I am impressed with XP and my consistent uptime. In fact it now "has been up for: 14 day(s), 8 hour(s), 11 minute(s), 49 second(s)" We all know mac's are great. Great for uptime, great for idiots, great on a total cost of ownership in any organisation, although not widely accepted. After reading Winn's Mac/Wintel TCO analysis, mac wins on the virus, spyware patching stuff. But why run analyse TCO of just that? How about Fedora vs Wintel? If there is any basis of comparision in an organisation, it would solely be the compatibility factor of groupware applications like outlook and office. Th...
Read more