-
Notifications
You must be signed in to change notification settings - Fork 11
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
Unable to discover BroadLink RMmini3 #71
Comments
Having the same problem, the plugin dont autodetect the RM mini 3 and if i add the learn button manualy with the hosy key i get error: device not found. |
I'm running into the same issue. Someone on Reddit Homebridge suggested I try this fork as I was getting a similar error with a learnSwitchState: undefined message using the main broadlink rm plugin. The OP said it has to do with using the Broadlink app to configure the device originally and not e-Control. Haven't tested that myself to check as I need the Broadlink app to be able to connect my device to Google Assistant as I use that primarily in my house, even more than Apple Home. Hoping this can be patched possibly to be able to use the plugin even if you used Broadlink app to originally configure the device. |
I doubt that this can easily be patched. I assume when setting up the device with the new Broadlink app Broadlink disables the "standard" communication on the device that is why this plugin (and all open source plugins) doesn't work. The only way would be for Broadlink to reenable this communication or provide an API for their new service. Why don't you use Homebridge to Google Smart Home for Google Assistant? This way you wouldn't be limited to the new Broadlink app. |
Any news guys? |
Upstream recently added support for a few more models in broadlinkjs. I made a PR to update the version - #79 Give that a go and see if it fixes anything
(I thought I have a RMmini3 but the plugin identified it as Changelog here |
Hi, |
Yeah! Or just fork yourself and update the js version 🙂 If you have permission problems, install as |
Just gave it a run but stuck here Does this solve as well for the issue with the 5f36? |
Ah yeah if you don't have git with ssh setup. Try https:
|
:( nope still npm ERR! A complete log of this run can be found in: |
Would have loved to test it, but I am not able to install via the process you have mentioned. Have done some research and not able to resolve. If here is any other proceedure I could use to try please let me know |
Just for information the fix of @dvcrn does not solve for the 5f36 devices. There is a thread now open on the broadlink-rm plugin to fix this. the devices require a specific header which is not yet part of the broadlinkjs script. |
take a look lprhodes#600 |
Hello,
I just wanted everyone know what I have been struggling for a day. I simply couldn't make my new RMmini3 to be discovered. Device discovery wouldn't find the device and even with the "hosts" config set up correctly the device hasn't been discovered.
As it turns out the problem is with the new BroadLink app. If you pair your RM3 with the new BroadLink app homebridge-broadlink-rm, python-broadlink won't discover it.
You have to reset the device and set it up with the old e-Control app. After that everything will work as normal. : )
Hope this will help someone...
The text was updated successfully, but these errors were encountered: