At present there are issues with certain devices not being recognized (we know device codes 0x653a and 0x653c are affected) and the integration aborts with a “device not supported” error. I suggest do not buy any RM4 device until this is sorted out as we do not have any advice from @felipediel or @danielhiversen about when this problem might be addressed.
Is there an alternative device that works as good or better than the RM4 with better integration in HA.
Got this error with my new BroadLink RM4S
Logger: homeassistant.components.broadlink.config_flow
Source: components/broadlink/config_flow.py:48
Integration: Broadlink ([documentation](https://www.home-assistant.io/integrations/broadlink), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+broadlink%22))
First occurred: 3:12:50 AM (3 occurrences)
Last logged: 4:26:59 AM
Unsupported device: 0x6364. If it worked before, please open an issue at https://github.com/home-assistant/core/issues
I am not able to integrate broadlink RM4 pro with HA. this is the error i’m getting.
Logger: homeassistant.components.broadlink.config_flow
Source: components/broadlink/config_flow.py:48
Integration: Broadlink
First occurred: 20 November 2020, 10:57:43 (7 occurrences)
Last logged: 0:08:20
Unsupported device: 0x653c. If it worked before, please open an issue at https://github.com/home-assistant/core/issues
Any following on this? Have a new RM4 Pro and get the same error 
I’ve got RM4C Mini brought on Aliexpress na 11.11, doesnt work:
Unsupported device: 0x6539. If it worked before, please open an issue at Issues · home-assistant/core · GitHub
I’ve discovered that my new RM4C mini with typeid 0x6539 works fine in Node-RED [node-red-contrib-broadlink-control] node, when I set my device type to 62be (type for older RM4c mini devices) in rmdevice config node. So it has just new typeid but works same as older RM4C mini devices. But I can’t manually override device type in HA integration
It seems that if you edit broadlink/ init .py you can fix this issue. Problem is I don’t know where to find this file X)
New update, still no fix.
Did you ever find that file? I’ve got the same issue.
No luck at all
I’m also awaiting the pull-request to be added so i can reach my RM4C mini 
Unsupported device: 0x6539. If it worked before, please open an issue at Issues · home-assistant/core · GitHub
16:26:02 – broadlink (ERROR)
1 Like
I managed on HassOs supervised by opening SSH and type:
docker exec -it homeassistant /bin/bash
cd /./usr/local/lib/python3.8/site-packages/broadlink
vi __init__.py
type i to get into editor mode
add this line:
0x6539: (rm4, "RM4C mini", "Broadlink"),
hit esc to leave editor mode
type :w to write changes to file
type :q! to exit vi
You should now be able to add the RM4Mini with id 0x6539 immediately
You only need this file change to add devices.
Note that this file change will not survive a server upgrade (however, any added broadlink device remain available once this line is re-added).
9 Likes
Thanks for your help. But i did the same thing and the error are here yet.
Added the line, but can’t add the integration. I need to run any docker command to enable this?
Seems the updated file can’t be accessed by the host, that says is device not supported.
Thanks in advance
Can you check your log and verify your typeid is 0x6539 ??
(you can see it in your logs…)
And if you re-open init.py with vi after you saved it…does it show the extra line ??
Thanks, my friend.
When you said that the edit will not survive a server reboot, i was fearful to try. Double checked and the file was edited and saved, but don’t work.
Mysteriously, wen i did a reboot, that works!
Thanks one more time for your help!
Weird…after a reboot my file is back in its original state, but the discovered RM4 remains …
Anyway, good that you got it working 
Same error with RM4C mini
Unsupported device: 0x6539
1 Like
Thanks aceindy!
Like k7franklin, I had to reboot before it would work, but my rm4 mini has been added now.
I’m a Hass n00b and “installed” Hass by downloading the VHDX on my Hyper-V server… I suppose this method only works when you’ve installed Hass using the Supervised route?
Thanks in advance!