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
Cloud ping packets not working with RM4 pro with firmware 52079 #641
Comments
No idea, but thanks for reporting this. Could you allow internet access and sniff the new ping packet with your firewall? |
RM4C mini also doesn't work with the current ping packet. The UDP payload is changing :
|
It changes because the message is encrypted. I can't devote myself to this right now, but if anyone is interested, these tools can be used to decrypt the communication. |
Would love to help more on this but I really don't know how to use my .cap binary files with broadlink-hacktools. |
Does anyone happen to have a copy of one of the older firmwares that we could downgrade to? Running into the same issue :( |
You can downgrade Broadlink devices ? I would love to do that too honestely it's so annoying. |
I managed to get a previous version firmware URL from Broadlink support, and tried to downgrade 3 times, and all 3 attempts failed. Feel free to message them on Amazon or via email and see if it works for you. Hope you have better luck :) |
I captured same payloads which start with |
Did you use https://github.com/felipediel/broadlink-hacktools to actually decrypt it ? Otherwise it’s normal it’s always different since it’s encrypted. |
I have tried, and it output:
I presume that the hacktools cannot deal with it. What about your opinion? |
@felipediel Please help us, what whould you need ? 😭 |
Indeed, the hacktools cannot deal with it, the packets have a different structure. The way is to reverse engineer the new firmware and try to understand the structure of the packets and the type of encryption used. This task takes some time and I cannot dedicate myself to it. If anyone can replicate a working watchdog packet, I'll be happy to turn it into production code. |
Same problem for RM4 MINI with V52078 / V52079 Firmware Version =/ |
I bought two rm4c mini both have the firmware 52079 and they periodically ping a http server at http://25913service.ibroadlink.com/devactiva/v2/devactiva After 3 minutes of trying and failing, they reboot. Unfortunately the content is encrypted with what I assume to be also AES-CBC with a constant IV. This is the captured packet: The reason I believe they are AES-CBC with a constant IV and key, is that both the initial request only differ at the end, probably due to a timestamp. Logging the requests I get:
I have tried to replay the answer from the server, but after a few seconds, the broadlink device ignores the answer, probably due to it using the timestamp fields as a nonce. I do not mind trying to reverse engineer the firmware, but before I take apart my units to try and dump the firmware, do you @felipediel, have any way easy way to get the firmware (some download link, or whatever) ? |
Hi @andreluis034. I know a guy who asked their support and they sent him a download link a while ago, but it was the previous version. I think it's worth asking them. Two other approaches that you can try:
|
I removed my RM 4c Mini from Broadlink App, and then reset my RM 4c, and provisioned it from my mac, sending the cloud ping to no avail, it still disconnect after 3 min. |
Thank you for the reply, I will give this one a try. If it does not work, I will try to reverse the android app to see if I can find the functionality to download the update.
Unfortunately it does not... What happens instead, is that the broadlink device starts making even more requests, one after the another. Under normal circumstances it pings the cloud every ~15s.
I never registered my device with the cloud. The only thing I have done, was take it out of the box and use |
Good news ! I've managed to downgrade my RM4C Mini, by combining the URL from this dead link : https://www.reddit.com/r/broadlink/comments/hmqh9c/help_me_update_firmware_rm4_mini_v52075/fy7tb9x/ And using the IP from this thread : https://www.reddit.com/r/homebridge/comments/1181ex4/caution_to_people_using_broadlink_rm_plugin/j9eqq0j/ Which made me able to download the v52075 firmware by combining the new host with the path for 52075 : http://124.71.130.238/RMBL4-52075-8710-BL-FC-2900.upd.bin The firmware is supposedly for RM4 Mini, but I successfully downgraded my RM4c Mini to 52075. However I can confirm the cloud ping method still doesn't work on this firmware. |
Hello my friend, I received your response on e-mail and I'll try to do the downgrade for broadlink RM4MINI and RM4PRO, you can help me on this? Do you use a specific program to do the firmaware downgrade? |
Hi ! You can paste the link directly in the broadlink app. You need to have added it to the broadlink app before. Click on the device, then the 3 dots on the top right, "Property" and firmware update, then an additional button somewhere on the UI where you can input your own custom link. Unfortunately 52075 doesn't resolve anything. I've found the link for 52074 and 52071, but rollback to 52071 failed, and haven't tried 52074 yet. I'm pretty sure all devices shipped with the new way for the cloud ping packet to work, so no firmware will solve the issue. Here's all links : http://124.71.130.238/RMBL4-52071-8710-BL-FC-2626.upd.bin |
Hello, I hope this is the correct repo for this. I use Home Assistant and have 2 different broadlinks:
My issue is with the RM4 pro -- it disconnects and reconnects every 3 minutes to my unifi AP. All outbound access for both broadlinks are blocked at my firewall. This seems directly related to this prior issue which aimed to add support for sending cloud ping packets. After reviewing the logs from pfsense, I can see that both of the cloud ping packets are being sent automatically by home assistant. The RM3 mini stays connected; however, the RM4 pro (with newer firmware) does not.
Has anyone run into this issue? Has the cloud ping packet changed? For reference, I think I setup the RM4 Pro with the app, and the RM3 mini without the app. Any help is greatly appreciated.
PFSense logs for RM4 pro below (10.0.1.50=Home assistant, 10.30.4.9=RM4 Pro):
The text was updated successfully, but these errors were encountered: