core: Broadlink RM4C Mini device not supported 0x520d

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: https://github.com/home-assistant/core/issues/72538 (just the device number is different).

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 41 (2 by maintainers)

Most upvoted comments

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

ComputerWarlock on Sep 30, 2022

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

Open Home Assistant and install “SSH & Web Terminal” add-on
Disable Protection mode
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

Restart the server.

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

felipediel on Jun 7, 2022

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?

Bat-Maniac on Sep 24, 2022

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.

2022-06-03_13-17-10 photo_2022-06-03_13-25-13 photo_2022-06-03_13-25-23

kpblca on Jun 3, 2022

Oh noooo😩😩 Please add 0x520D🙏

MrTheFirst on Oct 23, 2022

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!

adocampo on Jul 6, 2022

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! =)

jerrychong25 on Jul 4, 2022

please add RM4C mini 0x520d support

ilvi80 on Nov 18, 2022

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 https://github.com/home-assistant/core/issues/72762#issuecomment-1254895316, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASTW3C33D4P4LKNIUCIAURLV7Q7QHANCNFSM5XNQS47A . You are receiving this because you commented.Message ID: @.***>

purplephoenix76 on Sep 22, 2022

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.

unrat on Sep 22, 2022

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

nachomanzano on Sep 21, 2022