I use the Broadlink integration remote.learn_command service call, this places them in a file where you can either use them directly, or grab them for SmartIR or for scripts. See the linked text below.
Use the configuration editor to look at the files after capture.
Did you ever figure this one out? Iâm using a RM4 mini, and I seem to be encountering the same issue you did.
Iâve setup the RM4 mini to AP mode, connected to it successfully via WiFi, installed the Python-Broadlink script, and run broadlink.setup, but nothing seems to happen.
There is no output or any apparent process that ran in Python, and the RM4 mini light is still flashing slowly as it was before.
Iâve tried this on 2 brand new RM4 minis (never added to the app), and the result is the same.
Running the debug.py script that @zoogara shared shows that no devices have been detected too.
Setup RM mini 4 into AP Mode to connect with Broadlink app:
1- Long press the reset button until the blue LED is blinking quickly (like 7 seconds).
2- Long press again until blue LED is blinking slowly (like 14 seconds).
Configure RM mini 4 with Broadlink mobile application
1- Install broadlink app in your cellphone: https://play.google.com/store/apps/details?id=cn.com.broadlink.econtrol.international
2- First Open Press plus sign (+) to open menu then press Add device
3- Press Add a new device then press Universal Remote
4- Select your RM Version then press Next (My case RM4 mini - 2019 version)
5- Press button to confirm you are already connected
Add Air conditioner to RM Mini 4
1- Press RM mini already configured then press plus sign (+) to open menu
2- Select AC Remote Full Display
3- Press Add appliance button
Unlock RM Mini and Get IP address for Home Assistant
1- Press RM mini already configured
2- Press elipsis sign (âŚ) to open menu
3- Press property
4- Disable toggle with label Unlock device
5- Press Device information then get IP Address displayed into their corresponding section
Docker configuration
1- Install docker in Raspberry with get.docker.sh script with curl
1- Navigate to http://localhost:8123/ in the raspberry or http://<raspberry.pi.ip.address>:8123/
2- Let Home Assistant to autodetect your location
3- Add Broadlink integration and set RM miniâs ip address given by broadlink mobile application
4- Click the device labeled with Chinese characters then click the gear icon and finally set a better readable name (My case RM Mini 4)
5- Stop Home Assistant Container from domotic-server directory with command: docker compose down
6- Clone repo GitHub - smartHomeHub/SmartIR: Integration for Home Assistant to control climate, TV and fan devices via IR/RF controllers (Broadlink, Xiaomi, MQTT, LOOKin, ESPHome)
7- Copy custom_components into container/config directory generated by docker
8- Open container/configuration.yml then paste example configuration, defined in smartir/configuration.yml, below existing configuration
9- Set name and unique_id with values set on Broadlink mobile app for the Air Conditioner device
My device is joined to my network and I can ping it, but impossible to use the cli tool, please let me know if you have any idea
Traceback (most recent call last):
File "rm_config.py", line 74, in <module>
main()
File "rm_config.py", line 64, in main
devices = broadlink.discover(timeout=5)
File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/broadlink-0.14.1-py3.8.egg/broadlink/__init__.py", line 115, in discover
s.connect(('8.8.8.8', 53)) # connecting to a UDP address doesn't send packets
Broadlink integration just fails for me with Device not supported on RM4 mini. HA version is 0.115.2
2020-10-09 10:32:48 ERROR (MainThread) [homeassistant.components.broadlink] Unsupported device: 0x653a. If it worked before, please open an issue at https://github.com/home-assistant/core/issues
Just updated to HA version 0.116.4 still exactly the same problem. Perhaps change the integration documentation to not show these devices as supported when they are not. Is there any way to find out when the support will be added so I donât upgrade HA for no benefit.
I just bought and installed an RM4 mini on October 14th and was able to install it the same day. There was a bit of a learning curve with getting the stupid thing to give up itâs âlockâ, but around 10 factory restarts later and me about to throw it against the wall, it worked. Obviously it looks like others are working as well, so removing a known working model from the support documentation seems like it may be a bit counter-intuitive.
Since you havenât really posted any steps that you went through to troubleshoot, Iâll go over generally what I did. First I would factory reset it by sticking a small pin into the reset hole for around 30 seconds. After 10 or so seconds it should blink slowly with something like 4 blinks and the a pause, then after another few, it will blink faster, about 4 times per second. Eventually it will blink super fast and reboot. At that point you can take the pin out and wait for it to start up. I personally didnât have any luck with doing the âsmartâ install, though that could be my UTM blocking some kind of communication, so I had to go straight to the AP install. If the led is blinking rapidly, push the reset button for 10 or so seconds until it blinks slowly (4 then pause). Install the app on your phone and add the RM4 mini, that part should be painless. As soon as itâs joined, check your router or whatever is handing out DHCP leases to see what the IP address is. Throw it in there and try it out.
I will say that at first it wasnât working, but that was likely because I was skipping a step earlier, so I eventually got fed up and finished adding the RM4 mini all the way through the cloud bit. When I tried adding then, I got some kind of error (likely what you have) and noticed in the configuration for the RM4 mini in the app that it said it was locked. Once I factory reset and did everything again, it seemed to work fine.
EDIT - Oh! Also, if you get to the cloud bit, try updating the firmware. I did that too and might be part of why it started working. You can check your firmware version off of what HA was reporting in my screenshot above since I believe that app shows it as well (donât know for sure since I uninstalled it)
Thanks very much for your kind assistance, @jarvistek. I think there may be different models of RM4 Mini and mine, which I purchased from a dealer here in Australia, may be somehow different in some way and just will not install in HA. I bought two of these, both paired up with the broadlink app (using the AP install method) with no problem and I have the broadlink app linked with Alexa and both RM4 minis work fine in the Broadlink app and with Alexa. The firmware version of both units is the same as yours. As soon as I try to add the broadlink integration in HA for either of my units it comes back with âdevice not supportedâ. I can see the lock switch in the broadlink app and I have tried adding to HA with it locked and unlocked but every time I just get âDevice not supportedâ. Here is a screenshot of one device details from the broadlink app.
Also, could you let me know your version of HA. It seems that perhaps this integration may have worked in older versions of HA (like 0.109) but was perhaps broken in more recent versions (I started with 0.115}
Thanks again for your assistance, I really appreciate it.
Edit: Also there is a lot of confusing (to me) advice on other forums which says to stop the broadlink app installation at the point where the RM4 attaches to the router and then do the HA integration setup.
I didnât do this because I need the broadlink app integration with Alexa but Iâd love to know if you did it this way or went right through with the broadlink app installation before doing the HA integration. I actually have an RM4c Mini on order with Aliexpress but it will probably take 3 months to get here with the Covid delays. I was waiting for that to arrive to see if my problems are just a version issue.