Broadlink RM4C Mini device not supported 0x520d

[hauser123]

The problem

Device not supported error message when adding a new device. Device is: Bestcon RM4C Mini Universal WiFi Infrared Remote Control.

What version of Home Assistant Core has the issue?

2022.5.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Broadlink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/broadlink/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.broadlink.config_flow
Source: components/broadlink/config_flow.py:38 
Integration: Broadlink (documentation, issues) 
First occurred: May 24, 2022, 11:06:25 PM (4 occurrences) 
Last logged: 3:56:07 PM

Unsupported device: 0x520d. If it worked before, please open an issue at https://github.com/home-assistant/core/issues

Additional information

Similar issue: #72538 (just the device number is different).

[probot-home-assistant]

broadlink documentation
broadlink source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @Danielhiversen, @felipediel, @L-I-Am, mind taking a look at this issue as it has been labeled with an integration (broadlink) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[a000a498]

same as me
Logger: homeassistant.components.broadlink.config_flow
Source: components/broadlink/config_flow.py:38
Integration: Broadlink (documentation, issues)
First occurred: 14:06:36 (2 occurrences)
Last logged: 14:06:46

Unsupported device: 0x520c. If it worked before, please open an issue at https://github.com/home-assistant/core/issues

[hauser123]

Please note the different device id 0x520c vs 0x520d. Or does it matter?

[a000a498]

Please note the different device id 0x520c vs 0x520d. Or does it matter?

I know ,uust want let them know ,have another device id cannot support😅

[a000a498]

You can use this to solve your issue

I just tested and it works

[kpblca]

Hi,
i found the same issue when purchased new RM4C mini device.

But just adding of new device ID in init.py was solved the issue. Here the device's box & software version.

[felipediel]

Thanks guys, it will come in the next version of python-broadlink. If you want to have it before the release...

1. Open Home Assistant and install "SSH & Web Terminal" add-on
2. Disable Protection mode
3. Click "Terminal" on the sidebar and install the patch:

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

4. Restart the server.

You need to reinstall the patch if you update Home Assistant. It's not permanent.

[jerrychong25]

Thanks guys, it will come in the next version of python-broadlink. If you want to have it before the release...

1. Open Home Assistant and install "SSH & Web Terminal" add-on

2. Disable Protection mode

3. Click "Terminal" on the sidebar and install the patch:

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

4. Restart the server.

You need to reinstall the patch if you update Home Assistant. It's not permanent.

@felipediel Thanks for this solution, it's working fine! =)

[adocampo]

Hi, i found the same issue when purchased new RM4C mini device.

But just adding of new device ID in init.py was solved the issue. Here the device's box & software version.

Thank you dude! I have the very exact model and firmware and adding that worked here as well!

[gianlucaf81]

But just adding of new device ID in init.py was solved the issue. Here the device's box & software version.
Where is located init.py file? thx

[simonbrunton]

I wondered the same thing ☝️ Is it created when the Broadlink integration is installed?

[kevinkey619]

You can use this to solve your issue

I just tested and it works

Doesn't work for me.

[adocampo]

Doesn't work for me.

Which code did you tried? My RM4C mini worked with the code 0x520D
For those wondering where __init__.py is located, if you're using the docker version, you should follow the instructions on the screenshot, in my screnario, the code 0x6539 was already set, but I added a new line with the code 0x520D, and then it start working.

[zambod24]

Thanks guys, it will come in the next version of python-broadlink. If you want to have it before the release...

1. Open Home Assistant and install "SSH & Web Terminal" add-on
2. Disable Protection mode
3. Click "Terminal" on the sidebar and install the patch:

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

4. Restart the server.

You need to reinstall the patch if you update Home Assistant. It's not permanent.

Can someone explain how exactly to enter this code into the terminal. I have Terminal and SSH set up in HA but when I copy and paste the patch and hit enter it returns “command not found”. A photo or video of it in the terminal would be greatly appreciated!

[felipediel]

It must be "SSH & Web Terminal", there are two similar addons, the one you are using cannot access the container.

[gianlucaf81]

pip3 install git+https://github.com/mjg59/python-broadlink.git@new_product_ids --force-reinstall --no-deps

with a new version of HA (the latest) it works. Thank you.

[Boussen]

pip3 install git+https://github.com/mjg59/python-broadlink.git@new_product_ids --force-reinstall --no-deps

with a new version of HA (the latest) it works. Thank you.

still does not work

[unrat]

pip3 install git+https://github.com/mjg59/python-broadlink.git@new_product_ids --force-reinstall --no-deps

with a new version of HA (the latest) it works. Thank you.

still does not work

The latest release is still missing the ID for RM4C mini (0x520D) therefore it cannot work for now out of the box. Still, manual adding this ID is required.

But there is an open Pull Request which will add support for RM4C mini

[iamhuman2414]

I added (0x520D) in init.py and still not working for me after a server restart, any idea why?? Do I still need to add it in configuration.yaml? It's manually added there. I also tried the Broadlink integration, entered the RM4C IP address but still showing not supported.

[calcioscacchi]

Hi there. Any news about this issue? I'm using version 2022.8 and it still not working.

[SEVENID]

mjg59/python-broadlink#689 closed, but device still doesn't work. Version 2022.8.7 (docker stable)

[nachomanzano]

Hi i have the same problem:
[homeassistant.components.broadlink.config_flow] Unsupported device: 0x520d

Home Assistant 2022.9.5
Supervisor 2022.09.1
Operating System 9.0
Frontend 20220907.2 - latest

[ComputerWarlock]

Sam problem here as well New out of box RM4C Mini
Home Assistant 2022.9.5
Supervisor 2022.09.1
Operating System 9.0
Frontend 20220907.2 - latest

[unrat]

Yes, thats because the pull request was closed without merging it. But there is now another open pull request where the ID will be included.
Don't know why he didn't merged the other one, the effort would have been minimal.

As i see it, HA is using the latest release and as long as there is no new one with the ID in it, it can not work out of the box. Please check the Releases page of the other project if the device was added. Only then it will be working without manually adding the device ID.

[purplephoenix76]

It quite a chore to jump through this with every pushed HA upgrade. How can we expedite this to be incorporated into the new release? I just updated to 2022.9.6… probably another 2022.9.7 in a few days time. The agony.

[unrat]

How can we expedite this to be incorporated into the new release?

Wish i could tell you. But to be honnest, i think we have to wait for Felipe to merge it and make a new release. Till then the only choice we have is manually add it after every update or make no updates till it is merged.

Maybe there is a way to make a script in HA itself which is triggered after each update adding the ID automatically to the file. But no idea if or how this is possible, never tried such a thing

[purplephoenix76]

Bumper. my old RM4CMini just got toasted and i’ve bought a replacement. I followed the above to pull the changes using pip3 and it shows successfully install. However, even after restarting, it still show unsupported for 0x520d. Did i miss out anything?

[unrat]

Did i miss out anything?

What does the log say?

[purplephoenix76]

That's all I get from the logs 2022-09-22 19:25:42.011 ERROR (MainThread) [homeassistant.components.broadlink.config_flow] Unsupported device: 0x520d. If it worked before, please open an issue at https://github.com/home-assistant/core/issues

…

On Thu, 22 Sept 2022, 7:31 pm unrat, ***@***.***> wrote: Did i miss out anything? What does the log say? — Reply to this email directly, view it on GitHub <#72762 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASTW3C33D4P4LKNIUCIAURLV7Q7QHANCNFSM5XNQS47A> . You are receiving this because you commented.Message ID: ***@***.***>

[unrat]

I always add it manually into the file, never tried pulling and updating the file from the repo.

Can you have a look if the ID is actually in the file? explanation how to do so see above in the pictures with the chinese language

[Bat-Maniac]

When is this damn thing going to be updated?

I only bought the RM4C Mini because in the Home Assistant Documentation for Broadlink intergration it is listed as supported.

I've been waiting for almost half a year now, but with every Core update I have to add it manually again.

It's not as if new versions of the RM4C mini are released every week. That's why it could finally be updated.
Other integrations are also updated with almost every new version of Hass. Why this seems to be as hard?

[purplephoenix76]

@felipediel - Can you help us to pull this into the next build? Appreciate it!

[kpblca]

The pull request with new RM4c mini code 0x520d is exist here: mjg59/python-broadlink#715

It just need to merge it!

[Bat-Maniac]

I'm sorry for my last comment.
I know that development isn't easy all the time, and sometimes it just takes longer.
But it's a little frustrating when you buy a device that is listed to be supported, but it's not.
I didn't want to be rude and certainly I didn't want to cause trouble for anyone.

[ComputerWarlock]

I just got an RM4 Mini and it works fine. Few dollars more, didn’t want to wait for this one to be setup. I can confirm it works without issue as of right now. The RM4C Mini still does not

[simonbrunton]

RM4C mini is still not supported in 2022.10.5

[MrTheFirst]

Oh noooo😩😩 Please add 0x520D🙏

[cfromm1911]

Could someone please merge this change? I have 0x520D, but using HASSIO. I cannot figure out how to access the site-packages, "SSH & Web Terminal" no longer has a "Protection Mode" option, and docker command is not found.

[Bat-Maniac]

I‘ve switched from Home Assistant to Homebridge now, because all I really need is the HomeKit integration.
With Homebridge everything is working fine. I installed the Broadlink plugin and all my remotes are working, even the 0x520D.
Hass was a good experience for years, but with the time it‘s getting too much time-consuming and buggy.
Too much updates in a month, and with every update and with every update you hope that everything is working. But something you are waiting for to be updated won‘t be updated for over a year.
If you can't take care of the development, then maybe you should remove the integration. At least then there are no misunderstandings when users buy hardware that is compatible according to the description, but it isn‘t.

[ilvi80]

please add RM4C mini 0x520d support