[Dyson Pure Cool Me] Not connected to BroadLink RM
AyberkAltuntop opened this issue · 30 comments
hello, thank you for the plug in. i have a homebridge installed in the container, homebridge rm pro and dyson plug ins are working but i could not manage to run this plug in. in the logs it says [Dyson Pure Cool Me] Not connected to BroadLink RM. i think i should somehow make Broadlink and this plug in talk but how?
Thank you.
Hey, sorry to hear that is happening! Could you possibly send me your config for the plugin? I'll try my best to debug this issue.
Thanks for your quick response. Plug in json config is as follows. Since I am not very expert on this subject, if this is not what you want, I would appreciate it if you could be a little more specific. thank you. :)
{
"name": "Dyson Pure Cool Me",
"serialNumber": "C9E-EU-MFC0097A",
"macAddress": "ec:0b:ae:a0:55:17",
"accessory": "DysonBP01"
}
Thank you. Have you verified that you typed the MAC address correctly? The format is correct, but do double check.
Could you also send a screenshot of what the plugin shows when it starts up? It should print available BroadLink devices once it starts searching.
Mac address is correct. I have attached the plugin log and screenshots to the topic.
What version of the plugin are you using? As well as Homebridge and Node versions.
Also if you know the exact model number of your RM Pro please send that too.
Have you tried running the plugin as a child bridge?
v1.10.9 is your plugin version and node.js is v18.13.0 and Homebridge v1.7.0.
RM 4 PRO
No, i didnt tried child bridge.
I believe the plugin requires node 20. You can update node by going to the homebridge terminal and typing "hb-service update-node" and restart Homebridge when done.
I updated node.js to 20.11.0 and reinstalled the plugin but the problem still persists. Am I missing something? We don't need to add or teach the dyson remote to Broadlink, do we?
No you do not need to teach anything. The plugin is designed to work on it's own with minimal configuration. I will try to look more into this, perhaps a new hardware revision was released that a library the plugin uses doesn't support yet. Seeing that the BroadLink RM plugin works fine with it, I don't have any other troubleshooting ideas to give. I'll get back to you with my findings. Sorry about the inconvenience!
I'm assuming you already disabled the "Lock Device" setting in the BroadLink app? And also tried a child bridge?
Thank you very much for your support and help. child bridge also did not change the result. There is no problem with my other IR devices such as tv at the moment, but as I said, I cannot use this plugin and dyson pure cool me. I would be glad if you keep me informed about updates. Thanks again.
Real quick, could you link the BroadLink RM plugin you're using? And if possible, the serial number of your BroadLink RM (should be printed on the bottom or visible in the BroadLink app)?
Ok so my plugin and that one use the same library for connecting to devices, so I'll have to look into what's going on here. I may need your help since I don't own an RM4 Pro, but I'll let you know when I get there.
Of course, anything I can do. I'll be waiting updates. Thanks.
There's something like that in the logs. I wanted to share it in case it might help you.
Thank you.
That might be an issue to take up here. The fact its even going into that branch of code indicates this BroadLink RM is not officially supported by the library. Also probably a bug with that line in particular. I will do more testing this weekend.
If you could please test the latest version to see if it is still broken, that would be great. I did not do anything related to this issue, so I anticipate that it is still broken. What I said above probably is false considering homebridge-broadlink-rm still works for you.
To make this easier, I purchased an RM4 Pro to test it myself. It should be here in a week.
I hope you didn't buy it just for me :). The problem persists by the way, waiting to hear from you then.
Thank you very much.
I have no clue if anyone else is experiencing this, so it's best I try to solve it anyways. Also, I bought it through Amazon and plan to return it when I'm done. I'd love to use another one of these for my living room, but there is nowhere to put it.
My RM4 Pro came in today. I am able to reproduce the issue and can confirm the RM4 Pro does not work with this plugin at the moment. I will have some time in a couple weeks to work on actually fixing the issue.
Thank you for the information and for confirming the issue. I look forward to hearing back, thank you very much.
I was able to to some limited testing just now. A message showing that RF support was enabled for my RM4 Pro shows up (something that is part of the library), but it can't seem to find it. I also tested with kiwi_cam's plugin, and it does not connect to it for some reason.
I tried testing the library separate from the plugin and ran into the same behavior. I guess the RM4 Pro is not supported, even though the library says it is. I must be missing something, so I am not gonna write this off yet.
I think I discovered the fix for your specific issue, specifically this. Since it is considered a manual device, it wants to print that to the log; however, the log was never defined. I pushed a fix for that, but I plan to include it in my next release, which will probably happen tomorrow.
Woaw thank you for the information. I can't wait to try it :)
Ill be sure to let you know here when I send out the update. It would be version 1.12.0.
Hey Jeremy, we lost the remote on the way back from camp and we need you more than ever now. :) any news? You haven't forgotten me, have you? Thank you.
I have not forgotten! I have just been extremely busy and put most of my projects on hold. I do know I fixed the issue with the missing log, but I do not believe that fixes the issue where the RM4 Pro is not supported. I can't look more deeply into it for another few weeks.