-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Red RM Mini 3 does not work #30215
Comments
Hey there @Danielhiversen, @felipediel, mind taking a look at this issue as its been labeled with a integration ( |
i have the devices, I can cooperate as much as needed to help integrate this aparentelly new device. I can get online to help figure out what's going on. |
Have a similar issue, I have more than one of the RM Mini 3's, the one running firmware v55 works fine with HA but the others running 44057 aren't responding to HA but work with the Broadlink app. HA doesn't error out with send commands but the 44057 units don't seem to be receiving them or responding to them. |
This issue should be addressed to https://github.com/mjg59/python-broadlink, since all the communication with the device is being handled there. |
Dennis, my red rm mini runs this exact same firmware, so I'm guessing it has nothing to do with the model, but the firmware. Felipe, how do we proceed in moving the issue? |
Felipe, I would be happy to lend my time and try to get this older firmware responding to ha broadlink component |
I don't have this device, so it is difficult for me to contribute to this topic, but I encountered some open issues involving the Broadlink RM 3 Mini and the Broadlink API. Perhaps you can help them find a solution, which will be reflected here. mjg59/python-broadlink#274 |
Hey @ariel-madril as @felipediel mentioned earlier, this is not an issue for home assistant to fix. Home assistant uses the python-broadlink module to interact with the devices. I'm watching the three issue threads mentioned above hoping for someone to solve this. From what I understand, there are a number of variations of RM Mini 3's, the international versions run the v55 firmware and work with python-broadlink out of the box. The Chinese variants can still be discovered but they come up with different types (0x5f36) and run the 44057 firmware however, they cannot send or receive codes successfully, even after adding the 0x5f36 type to the module. Below is an extract of the two discovered types, top one being the working international version that I have.
|
Here are some steps that may be helpful for someone who has this device and is willing to solve the problem:
|
Here you can find some clues to identify where the problem is: #23566. |
Seems Broadlink and ihc apps config devices differently. Couldn't get HA / Broadlink Manager work with my RM3 mini set up using BL but ihc is ok. Hope it helps. |
Hi, same problem, but found solution, RM3 Mini 44xxx FW, reset device by long press until led rapidly flash, use BroadLink app to connect to WiFi (keep phone close to RM). AND STOP!! Do nothing more, dont't add anything more, quit app and now everything in HA works! ha... funny right? |
Hey @QuadrifoglioVerde and @wai00cheung, I've tried the long reset and configured wifi using the Broadlink e-control app, the new Broadlink app as well as the IHC app. I've also tried re-configuring the wifi using python-broadlink and in all cases, I can't send or receive from the python-broadlink CLI or from HA. |
@dennisadvani I use ?newer? Broadlink app (not e-control) for configure WiFi , HA and Broadlink manager works, when i configure some device in Broadlink app then nothing works (HA can't connect, Broadlink Manager not responding to learn). |
Thanks for confirming @QuadrifoglioVerde are you able to share your firmware number and Device type? I'll try a few more times with the Broadlink app. |
@QuadrifoglioVerde did you mean the Broadlink app (blue icon and white dots) or Ihc for EU? I tried a couple of times, also creating a new broadlink account, but still not working for me. |
@dennisadvani and @goose2600 I used this app:
|
-mine fw 44059 |
@QuadrifoglioVerde @wai00cheung Mine (copied from "device info" menu in the android app): Python-broadlink discovery cli cannot find any device. My exact steps are:
I added a switch like @QuadrifoglioVerde but learnig is not working from HA (led is not blinking) and I guess also sending commands is not working. |
I got as far as capturing some traffic in Wireshark, dumps available to download here if anyone wants to take a look. |
@Siytek I have a couple of questions: I am still looking for a way to find the device type for my Mini! |
@goose2600 I managed to get broadlink manager to pick up my device, but it just shows errors when it does...usually it picks up the other ones I have that works properly. I wanted to post a pic of the error, but I'm trying to get it to connect to the red one, and it doesnt... I hate how it doesnt let me pick up from a known device list instead of having to rely on the "scan" button... I would turn the others off, but they are mounted on the ceilling and opening the sockets would mean breaking some of the holder and redoing it latter... |
@goose2600 do not add device to room, stop at this step, when led stops blinking then quit. btw i choose Czech Republic if that helps. |
@goose2600 yes I can set up my device in Broadlink Manager using my Windows laptop. Once it is on the network I am able to discover it with Python-broadlink cli via my Ubuntu server...
I have added device ID 0x5f36 to _ init _.py prior to running Broadlink_discovery, not sure if it makes a difference here as I did not try it without the edit. However I am unable to learn commands from any platform other than the Broadlink app. |
Thanks to everybody. @QuadrifoglioVerde Broadlink manager for Windows keeps discovering an unknown device. |
Did you try adding 5f36 to Also when you reset it to discovery mode, is the LED flashing intermittently or quickly/consistently? |
@goose2600 my device (?PID?) is 3727, and works in all apps, include python-broadlink. |
Before to test I modified the init.py and while in discovery mode the led is blinking quickly/consistently (I am not in AP mode). |
@chemelli74 Do you remember what caused the storage error? And how did you solve it? There is another user reporting this error, but I don't have the device to reproduce it. |
I have only a wild guess about it: I learned a lot of codes to understand the on/off thing when I saw it, so I bet it's related to the time last code stays in device cache. Simone |
I think there are some things we still don't know about those special headers. Perhaps they contain flags like "store this code" or "clear the cache". I will investigate further when I have the device. |
Same issue here, RM4 Pro, i am also get the error "Failed to enter learning mode: The device storage is full". |
I found a few different headers in my files and created a possible solution. Can anyone help me test it? |
Library updated. What should I test ? Simone |
@chemelli74 Try to reproduce the error with this new version. |
ahahahah, first code learned and:
Simone |
Let's try with another header that I found here, just a sec. |
I just updated the file. You need to get rid of the error before trying again (don't ask me how). |
If you open a terminal and try device.check_data(), does the problem persist? |
Simone |
You need to authenticate first: |
Sorry, a bit tired ;-)
Simone |
The error persists. The truth is that we always had this error, but it was going unnoticed. If we can’t solve it, I think it’s okay to ignore it. |
If you mean that it was always logged, I'm sure it was not the case. But maybe it was the time that my device was not authenticated. Simone |
I recently changed the library to raise firmware errors. This error can only be identified after the update. I will keep trying to handle it correctly, I would not like to ignore this exception. But if we do not succeed, I do not discard this option. |
I made a script to learn 10,000 codes combining my remotes (one receives and the other sends) and I still didn't get any storage error. So I think this problem is only related to RM4 series. |
I just realized that the problem has nothing to do with those special headers because 0x2737 has the same problem and does not use them. |
@chemelli74 I solved the problem. Here is the solution, in case you need it before the release. |
@felipediel, finally tested:
Issue is related to /etc/host missing entry:
if I add "127.0.0.1 <container name>" then it start working again. But now I get this issue:
|
@chemelli74 Sorry, the instructions are out of date. The solution is already part of the Home Assistant (0.110.2). I just changed the instructions in case you need to revert. |
Tested with fresh 0.110.3 docker container and get the same error message:
Simone |
This is the |
Hi guys. Please do not update before this PR is merged. 0x5f36 is unstable at 0.115. |
Hi Felipe, |
INTEGRACION RM MINI 3 FIRMWARE: 44057 EN HOME ASSSITANT
El codigo aprendido se introduce en el archivo: Copiamos el codigo en un switch: |
Works with : ihc ver. 1.9.50 |
All issues reported here have been resolved. If anyone has an issue, please open a new case. |
The different (I don't know if it's new or not) RM Mini colored red does not work with broadlink component.
I used broadlink_cli to try to get it into learning mode and got the following:
AttributeError: device instance has no attribute 'enter_learning'
In home assistant, the commands just don't execute in the device, altho the buttons goes from on to off normally.
The firmware on this is 44057
Model: RM mini 3
FCC ID: 2ACDZ-RMMINI3-RM
On intelligent home center app from broadlink, the devices work as intended.
It has no firmware upgrades available for it.
On e-control app, it shows as unrecognized device, but shows.
Using broadlink manager gives the following:
![image](https://user-images.githubusercontent.com/6908310/71450066-d5f8fe80-2730-11ea-9874-4ecfd404fcf0.png)
It seems that even tho it's looks like exactly the same model, it operates differently and has a different model number and api to authenticate and recieve learn and send signals.
The text was updated successfully, but these errors were encountered: