Homebridge Broadlink RM Plugin and Broadlink RM4 - Couldn't learn code, device not found

[jaeger81]

I am running homebridge on docker (Synology NAS). I installed the broadlink-rm plugin and wanted to configure it for RM4C mini. When I try to use learn button I get error in log: "[ERROR] Learn Code (Couldn't learn code, device not found)" Device seems to be discovered since there is a line in log saying: "We've discovered an unknown Broadlink device. This likely won't cause any issues." I also tried using host section in config.json but the result is the same. Any thoughts?

Michael

[Lo0s3R]

Hi! im with same problem, "[Broadlink RM] [Info] We've discovered an unknown Broadlink device. This likely won't cause any issues. Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "610f". The device is connected to your network with the IP address "192....." did you find a solution? Any thoughts?

[dereklucas]

I bought an RM4 assuming it would be a matter of adding the device code (Mine's 51da, by the way) but sadly after poking around I don't think that the RM4 will be able to be supported by this plugin. Unfortunately, I won't be able to dig into this much more because the reset button broke and I'm returning it for an RM3.

I don't think this plugin will ever support the RM4 because I think that the RM4 is only controllable through the Broadlink cloud API. For one thing, the IHC app can't control the RM4, you have to use the new Broadlink app. For a second, I proxied my phone during setup and using the RM4 after it was set up in the Broadlink app, and my phone never connected directly to the RM4. It only contacted https://cf7a67e78338c7401deaeb96488f46fbappservice.ibroadlink.com. Activating the control were POSTs to https://cf7a67e78338c7401deaeb96488f46fbappservice.ibroadlink.com/device/control/v2/sdkcontrol that included the IR data and remote ID.

That makes me think that unless we can put a proxy between the RM4 and the API, we won't know where exactly to send the data. Then, we'll have to interface with the Broadlink API, which adds a lot of complexity to the project.

[jaeger81]

I also gave up. Bought RM3 mini and it works like a charm :)

On 7 Dec 2019, at 21:37, Derek Lucas notifications@github.com wrote:

I bought an RM4 assuming it would be a matter of adding the device code (Mine's 51da, by the way) but sadly after poking around I don't think that the RM4 will be able to be supported by this plugin. Unfortunately, I won't be able to dig into this much more because the reset button broke and I'm returning it for an RM3.

I don't think this plugin will ever support the RM4 because I think that the RM4 is only controllable through the Broadlink cloud API. For one thing, the IHC app can't control the RM4, you have to use the new Broadlink app. For a second, I proxied my phone during setup and using the RM4 after it was set up in the Broadlink app, and my phone never connected directly to the RM4. It only contacted https://cf7a67e78338c7401deaeb96488f46fbappservice.ibroadlink.com. Activating the control were POSTs to https://cf7a67e78338c7401deaeb96488f46fbappservice.ibroadlink.com/device/control/v2/sdkcontrol that included the IR data and remote ID.

That makes me think that unless we can put a proxy between the RM4 and the API, we won't know where exactly to send the data. Then, we'll have to interface with the Broadlink API, which adds a lot of complexity to the project.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lprhodes/homebridge-broadlink-rm/issues/513?email_source=notifications&email_token=AN4J5QAVW2S7XXCXQJBW62TQXQCRHA5CNFSM4JR643Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGGO42Y#issuecomment-562884203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4J5QGWOSKC3BZJWWZNZ2LQXQCRHANCNFSM4JR643QQ.

[lprhodes]

Hey, I'll buy an RM4 and an RM4C Mini and see what I can do.

[dereklucas]

I replaced the broken RM4 with an RM3 and set it up through the BroadLink app. After that I had the same issue. I found a comment on python-broadlink that fixed my problem. If I recall, you can use IHC with an RM4 only after it has been set up with the BroadLink app. It, and the older app, cannot set up the RM4. That’s enough to confirm for me that the RM4 is cloud control only.

Good luck! The web API wasn’t terribly complicated, but that’s not really what I wanted.

[lprhodes]

Interesting, thanks!

[Cocco17]

Any news on the RM4 Mini with the ID "610f"? :)

[kiwi-cam]

Hi @Cocco17. Unfortunately this project seems to have been abandoned again. The good news is there there are forks adding RM4 support. I personally have done work on the broadlink-rm-pro fork which doesn't yet support that device code - but I should be able to get that added today.

[Cocco17]

@kiwi-cam That would be awesome! Think I already saw another request for this device code already somewhere, so I guess more people would profit from your work :) Thanks in advance

[kiwi-cam]

Done 👍

4.2.9 or 4.2.10-beta will support your device.

[Cocco17]

@kiwi-cam great! Looking forward testing the functionality :)

[aldryk77]

@kiwi-cam I have an RM4, and installed your fork but i do not see my RM4 identified by homebridge - how can i get support to my RM4?

[kiwi-cam]

@kiwi-cam I have an RM4, and installed your fork but i do not see my RM4 identified by homebridge - how can i get support to my RM4?

If your device isn't supported you'll typically see a message saying:

"[Info] We've discovered an unknown Broadlink device. This likely won't cause any issues.

Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "????". The device is connected to your network with the IP address "x.x.x.x".

If you let me know what type of device you're using and the type code given I'll add it to the list.

[aldryk77]

@kiwi-cam Thanks for helping me 👍 I do not see this message in the log.. I only see now that it is automatically discovering the RM devices... but how do i know if it indeed captured the RM4 Pro?

[aldryk77]

@kiwi-cam

When i try to use the Learning RF button - i get this:

[BroadlinkRM] [INFO] Learn Code (Couldn't learn code, device not found)

And i have set it (the button) to the IP address of the RM4 Pro...

[aldryk77]

@kiwi-cam Any idea?

[kiwi-cam]

When you start homebridge does it find a device? You should see something like: [Broadlink RM] [INFO] Discovered Broadlink RM 4 Pro (6026) at 192.168.x.x (24:df:a7:xx:xx:xx)

[aldryk77]

When you start homebridge does it find a device? You should see something like: [Broadlink RM] [INFO] Discovered Broadlink RM 4 Pro (6026) at 192.168.x.x (24:df:a7:xx:xx:xx)

Nope. It only finds the RM Mini i have. not the RM 4 Pro.

[kiwi-cam]

Do you have the RM4 Pro setup in the Broadlink app? If so (by default) local network access is blocked: https://github.com/kiwi-cam/homebridge-broadlink-rm/tree/kiwi-cam-beta-1#documentation

[aldryk77]

THANKS!! That did the trick!

[BroadlinkRM] [INFO] Discovered Manual RM4 Pro Device (2227)

[aldryk77]

@kiwi-cam Last question - is the RF learning supported? I am able to control IR from the PRO. but not RF...

[kiwi-cam]

Take a look at #45.

Currently testing it in BETA. It'd be great if you could try it out and let me know of any issues.

[aldryk77]

I'll be happy to beta test it. downloading the beta now.