New release with support for RM4C mini (product ID 0x520D)?

[mt0321]

Hello,

Could we get a new release supporting the Broadlink Bestcon RM4C mini with product ID 0x520D?

Support was merged in to the new_product_ids branch in June thanks to titusthefox04, but it's not in the main branch and also not available via Home Assistant, presumably because the last release was 0.18.2 in May.

Let me know if I can help. Thank you!

[seb5594]

Would be very nice if this device could get be added into the main branch :)

[guieiras-dev]

Can't wait for this release to. I bought 3 RM4C mini with product ID 0x520D and would love to have native support.

---

Tip: If someone wants to support new Product IDs right now, patching manually the Home Assistant instance can be a solution.

1. Open Home Assistant and install "SSH & Web Terminal" add-on
2. Disable Protection mode
3. Connect to the Home Assistant instance using SSH:

ssh USER@IPADDRESS
docker exec -it homeassistant /bin/bash
cd /./usr/local/lib/python3.10/site-packages/broadlink
wget -O __init__.py https://raw.githubusercontent.com/mjg59/python-broadlink/new_product_ids/broadlink/__init__.py

4. Restart the server.

[OGB1952]

I'm another one that has just bought a few of these newer RM4C Minis and have run into the same issue, so if there is an easy way to patch HA to recognise these product ID 0x520D RM4C Minis I would be grateful for any tips (I am definitely a novice!).

[guieiras-dev]

@OGB1952 You can try the steps on my comment above. After step 4 (restart the server), your HA should be able to recognize the RM4C using the native Broadlink integration.

[OGB1952]

Many thanks, but try as I might I cannot find the location of the broadlink directory, or even the location of the Python directory. I'm running HA on a Raspberry Pi using the standard HAOS installation, so not using Docker. I've hunted high and low through the file system to try and locate where the file containing the definitions may be lurking to no avail. This is all that is in the /usr/local/lib directory:

[core-ssh /]$ cd /./usr/local/lib
[core-ssh lib]$ ls
libjemalloc.a      libjemalloc.so     libjemalloc.so.2   libjemalloc_pic.a  pkgconfig

It's a bit frustrating, as if I've understood things correctly it looks like all that needs to be done is to add a line in a file to define the 0x520D product ID.

[iron-2]

Just got mine RM4C mini and have the same issue. Hopefully this is fixed soon.

[seb5594]

Can't wait for this release to. I bought 3 RM4C mini with product ID 0x520D and would love to have native support.

---

Tip: If someone wants to support new Product IDs right now, patching manually the Home Assistant instance can be a solution.

1. Open Home Assistant and install "SSH & Web Terminal" add-on
2. Disable Protection mode
3. Connect to the Home Assistant instance using SSH:

ssh USER@IPADDRESS
docker exec -it homeassistant /bin/bash
cd /./usr/local/lib/python3.10/site-packages/broadlink
wget -O __init__.py https://raw.githubusercontent.com/mjg59/python-broadlink/new_product_ids/broadlink/__init__.py

4. Restart the server.

This does not work anymore since latest HassOS update. The python packages seems to have a new location. Do you know the new location?

[OGB1952]

I've spent a fair bit of time trying to find where the packages have moved to with no luck, I'm afraid. It's irritating knowing that a simple file edit will probably fix this, but not being able to find where that file now is.

[iron-2]

Where can I leave a post so that the devs get a message on this issue??

[guieiras-dev]

I feel sorry that you couldn't find the files with the guide on my comments above, but I’ll try to be more specific and I hope you should be able to manually patch your instance.

1. Use the Add-on from Home Assistant Community Add-ons, not from Official Add-ons. Remember to follow the installation guide correctly.
   

2. It’s very important that you disable Protection Mode before starting add-on.

3. Connect to your instance using SSH or using Web Interface on add-on. When the instance is connected, you should see lines like these.
   

4. Enter the lines below. These “docker” command should work no matter what is your installation (even HASS OS).

docker exec -it homeassistant /bin/bash

cd /./usr/local/lib/python3.10/site-packages/broadlink
wget -O __init__.py https://raw.githubusercontent.com/mjg59/python-broadlink/new_product_ids/broadlink/__init__.py

[KennyHec]

For those having problems with python dir not being found, use this instead in the terminal. This has always worked for me.

docker exec -it homeassistant /bin/bash
pip3 install git+https://github.com/mjg59/python-broadlink.git@new_product_ids --force-reinstall --no-deps

[FlameSoulis]

I'm reporting that the above instructions are incorrect. I have a core installation on a virtual machine, and I'm noticing that python is entirely missing. Perhaps this is the cause of all the problems?

In addition, the docker command doesn't work either because the command doesn't exist.

EDIT: Okay, thanks to this post, the issue is the terminal type. Switching this resolved the issue and made the above work.

[domoaligato]

the workaround works for me on unraid in docker.

[simonbrunton]

RM4C mini is still not supported in 2022.10.5