Add RM4 Pro Support #10
Comments
|
Please could you also add support for RM4 mini with code 62bc - I’m getting the following error: [31m[ERROR] [0m Scan RF (RF learning not supported for device (25276) at undefined) |
|
@BarnicleFiend 62bc looks like it’s there already. Are you using the latest version? |
|
I'm using 4.2.6. Its finding my device ok in the log like this: But I'm getting undefined on learn and scan frequency for some reason: |
|
I have two RM4 mini 51da, and I am using homebridge-broadlink-rm-pro v4.2.6. Both RM4 are on the network with static IPs, and both are seen by Broadlink app. RM4-34-a7-be : Discovered Broadlink RM Mini 4 (51da) Pls advise. |
|
I've just published a BETA release to (hopefully) fix this. It should use the new RM4 headers on the devices and enable RF. Could @Fannangir or @johnsclarke try installing homebridge-broadlink-rm-pro@4.2.7-beta.1 and let me know how it goes (I don't have an RM4 Pro to test myself)? Or anyone else with an RM4 Pro for that matter. I'd like to confirm:
|
|
Hi kiwi, |
|
Cameron,
Installed the beta and no longer get the error message but can’t start the device learning. Get the following in the logs when I try to lean a IR code:
15/06/2020, 09:48:01 [Broadlink RM] [35m[INFO][0m Automatic Broadlink RM device discovery has been disabled as the "hosts" option has been set.
15/06/2020, 09:48:01 [Broadlink RM] [35m[INFO][0m Running Homebridge Broadlink RM Plugin version [32m4.2.7-beta.1[0m
15/06/2020, 09:48:01 [Broadlink RM] No accessories have been added to the "Broadlink RM" platform config.
15/06/2020, 09:48:01 [Broadlink RM] Initializing platform accessory "Learn"...
15/06/2020, 09:48:15 [Broadlink RM] Learn getSwitchState: undefined
15/06/2020, 09:48:18 [Broadlink RM] Learn getSwitchState: undefined
15/06/2020, 09:48:18 [Broadlink RM] [31m[ERROR][0m Learn Code (Couldn't learn code, device not found)
I have given the thing a static IP to see if that helps but no better. Config below.
{
"platform": "BroadlinkRM",
"name": "Broadlink RM",
"hideScanFrequencyButton": true,
"hideLearnButton": false,
"hideWelcomeMessage": true,
"hosts": [
{
"address": "192.168.0.206",
"mac": "24:df:a7:e4:7e:84"
}
]
}
From: Cameron <notifications@github.com>
Sent: Sunday, 14 June 2020 6:07 PM
To: kiwi-cam/homebridge-broadlink-rm <homebridge-broadlink-rm@noreply.github.com>
Cc: johnsclarke <john_s_c@hotmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [kiwi-cam/homebridge-broadlink-rm] Add RM4 Pro Support (#10)
I've just published a BETA release to (hopefully) fix this. It should use the new RM4 headers on the devices and enable RF. Could @Fannangir<https://github.com/Fannangir> or @johnsclarke<https://github.com/johnsclarke> try installing homebridge-broadlink-rm-pro@4.2.7-beta.1<mailto:homebridge-broadlink-rm-pro@4.2.7-beta.1> and let me know how it goes (I don't have an RM4 Pro to test myself)?
Or anyone else with an RM4 Pro for that matter.
I'd like to confirm:
1. Commands are sent correctly,
2. You can learn codes correctlty
3. The above two tests work for both IR and RF codes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AP4JLUIRSUN4OLIX2COZSJ3RWSAKHANCNFSM4N5DH5WQ>.
|
|
@johnsclarke - do you see a line like this shortly after starting homebridge: The logs suggest it's not finding your Broadlink device on the network. |
|
Cameron,
The device is there and pingable. How does device discovery work for these things? I’ll do some sniffing and see if anything is getting dropped?
John C.
From: Cameron <notifications@github.com>
Sent: Monday, 15 June 2020 10:53 AM
To: kiwi-cam/homebridge-broadlink-rm <homebridge-broadlink-rm@noreply.github.com>
Cc: johnsclarke <john_s_c@hotmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [kiwi-cam/homebridge-broadlink-rm] Add RM4 Pro Support (#10)
@johnsclarke<https://github.com/johnsclarke> - do you see a line like this shortly after starting homebridge:
Discovered Broadlink RM4 Pro (61a2) at 192.168.0.18 (34:ea:34:xx:xx:xx)
The logs suggest it's not finding your Broadlink device on the network.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AP4JLUPMQVV6FMUXPTEV6XLRWVWG3ANCNFSM4N5DH5WQ>.
|
|
Cameron,
I have attached a capture. It appears to show two way UDP data on port 80. There appears to be connectivity at IP layer. Are any layer 2 protocols involved?
John C.
From: John Clarke
Sent: Monday, 15 June 2020 12:41 PM
To: kiwi-cam/homebridge-broadlink-rm <reply@reply.github.com>; kiwi-cam/homebridge-broadlink-rm <homebridge-broadlink-rm@noreply.github.com>
Cc: Mention <mention@noreply.github.com>
Subject: RE: [kiwi-cam/homebridge-broadlink-rm] Add RM4 Pro Support (#10)
Cameron,
The device is there and pingable. How does device discovery work for these things? I’ll do some sniffing and see if anything is getting dropped?
John C.
From: Cameron <notifications@github.com<mailto:notifications@github.com>>
Sent: Monday, 15 June 2020 10:53 AM
To: kiwi-cam/homebridge-broadlink-rm <homebridge-broadlink-rm@noreply.github.com<mailto:homebridge-broadlink-rm@noreply.github.com>>
Cc: johnsclarke <john_s_c@hotmail.com<mailto:john_s_c@hotmail.com>>; Mention <mention@noreply.github.com<mailto:mention@noreply.github.com>>
Subject: Re: [kiwi-cam/homebridge-broadlink-rm] Add RM4 Pro Support (#10)
@johnsclarke<https://github.com/johnsclarke> - do you see a line like this shortly after starting homebridge:
Discovered Broadlink RM4 Pro (61a2) at 192.168.0.18 (34:ea:34:xx:xx:xx)
The logs suggest it's not finding your Broadlink device on the network.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AP4JLUPMQVV6FMUXPTEV6XLRWVWG3ANCNFSM4N5DH5WQ>.
|
|
your beta works with IR [6/15/2020, 23:11:12] [Broadlink RM] Learn Code (ready) |
|
but it failed with Scan RF. When I press scan button, and press a key in remote, Homebridge seems crashed and restart [6/15/2020, 23:12:56] [Broadlink RM] [INFO] Scan RF (scanning) [6/15/2020, 23:12:57] Got SIGTERM, shutting down Homebridge... [6/15/2020, 23:13:00] RangeError [ERR_INVALID_OPT_VALUE] [ERR_INVALID_OPT_VALUE]: The value "-4" is invalid for option "size" [6/15/2020, 23:13:01] RangeError [ERR_INVALID_OPT_VALUE] [ERR_INVALID_OPT_VALUE]: The value "-4" is invalid for option "size" [6/15/2020, 23:13:02] RangeError [ERR_INVALID_OPT_VALUE] [ERR_INVALID_OPT_VALUE]: The value "-4" is invalid for option "size" [6/15/2020, 23:13:02] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null |
|
@kfung0426 which version of the beta are you using? I did catch that some of the RF functions weren't using the new headers and published homebridge-broadlink-rm-pro@4.2.7-beta.2 yesterday. |
|
@johnsclarke Have you seen this thread: lprhodes#600 (comment) You might need to reset and re-configure the device. |
|
Cameron,
The tread below had the fix. My mistake was thinking getting it to connect to WiFi was enough. It isn’t. The trick is in the Broadlink app get it to connect to WiFi, then to tell the device its name but don’t complete the next step of telling what room it is in. All fine now.
John C.
From: Cameron <notifications@github.com>
Sent: Tuesday, 16 June 2020 7:19 AM
To: kiwi-cam/homebridge-broadlink-rm <homebridge-broadlink-rm@noreply.github.com>
Cc: johnsclarke <john_s_c@hotmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [kiwi-cam/homebridge-broadlink-rm] Add RM4 Pro Support (#10)
@johnsclarke<https://github.com/johnsclarke> Have you seen this thread: lprhodes#600 (comment)<lprhodes#600 (comment)>
You might need to reset and re-configure the device.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AP4JLUP7NZQGXBAPFMI3XFDRW2F3RANCNFSM4N5DH5WQ>.
|
|
@kiwi-cam I'm using beta2 now, error still exist. [6/16/2020, 11:15:23] [Broadlink RM] [INFO] Scan RF (scanning) [6/16/2020, 11:15:24] Got SIGTERM, shutting down Homebridge... [6/16/2020, 11:15:26] RangeError [ERR_INVALID_OPT_VALUE] [ERR_INVALID_OPT_VALUE]: The value "-4" is invalid for option "size" [6/16/2020, 11:15:27] RangeError [ERR_INVALID_OPT_VALUE] [ERR_INVALID_OPT_VALUE]: The value "-4" is invalid for option "size" [6/16/2020, 11:15:28] RangeError [ERR_INVALID_OPT_VALUE] [ERR_INVALID_OPT_VALUE]: The value "-4" is invalid for option "size" [6/16/2020, 11:15:29] RangeError [ERR_INVALID_OPT_VALUE] [ERR_INVALID_OPT_VALUE]: The value "-4" is invalid for option "size" [6/16/2020, 11:15:29] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null |
|
same here with homebridge-broadlink-rm-pro@4.2.7-beta.2 and learning RF codes, payload.length is 0 |
|
@kiwi-cam added that it crashes immediately after started scan, without pressing the rf remote |
|
I added an If-Statement to the code, 6 times a 0 length payload is received and nothing happens when I press a button on the remote. [6/16/2020, 5:34:54 PM] [Broadlink RM] [ACTION] Hold down the button that sends the RF frequency. Maybe it needs more information, the Broadlink App asks for a frequency when learning RF codes... |
|
btw: thanks to @kiwi-cam! I also tried to add RM4 Pro but already failed at the IR level ;-) |
|
From what I can see @kfung0426 the line you've highlight is unnecessary - this module is a translation from the python module and some functionality is removed so it's not a simple line to line translation. I've removed those lines and some some simple testing myself (I don't have RF unfortunately). If someone would like to install the latest beta ( Obviously this isn't ideal. It's very hard to troubleshoot a device when I don't have one. If anyone else wants to have a go at fixing the issue in https://github.com/kiwi-cam/broadlinkjs-rm I'm more than happy to merge a pull request - or take suggestions. |
|
@kiwi-cam Just tested Thanks you for your work! Finally got my fan controllable from HomeKit 🎉 |
|
Let me jump into the discussion. I also got an new device RM4 pro 0x61a2. Any idea how to fix this ? |
|
Update about my test: IR learning works fine but couldn't learn RF codes. Same what @e1l52 just wrote. |
|
I can confirm also : IR learning works for me. |
|
I tested RF learning in Broadlink app and it works. In homebridge (latest beta version of this package: 4.2.7-beta.4) it doesn't give any error, says RF scanning is activated, but the orange light on the RM4 Pro lights up for only 5 seconds, meanwhile homebridge logs say it's still in scanning mode for another 15 seconds (20 seconds total). @kiwi-cam I'm not sure if this information helps, but I can collaborate and test all minor changes on my device. As I know you don't own RM4 Pro version, so I might help that way. |
|
I'm game if you are. I've added some more logging in a new branch of the broadlinkrm-js module. Could you do these steps to replace the index.js file used with this new version:
In summary, you're downloading a new index.js from https://raw.github.com/kiwi-cam/broadlinkjs-rm/kiwi-cam-RF-Debug/index.js and placing it in the dir If you could then run RF learning and post the log output for me. You should see additional lines like this: Hopefully that will give some clues as to where the logic is failing. |
|
Done. No difference if I press buttons on RF remote or not. Here are the results: Expand
[6/29/2020, 3:28:40 AM] [Broadlink RM] [INFO] Scan RF (scanning)
[6/29/2020, 3:28:40 AM] [Broadlink RM] [ACTION] Hold down the button that sends the RF frequency.
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 25
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 30
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 5
[6/29/2020, 3:29:01 AM] [Broadlink RM] [INFO] Scan RF (stopped - 20s timeout)
[DEBUG] packet received with command: 238
[DEBUG] Received packet with param: 30
[6/29/2020, 3:29:02 AM] [Broadlink RM] [INFO] Scan RF (stopped)P.S. now the orange light on the device stays on until stopping the scan. Before it was lit for only 5 seconds. |
|
Can I assume these lines: Are you sending the RF frequency you'd like to learn? 🤞 you say yes and the param 5 is the packet with the code. |
|
@burakcankose you can tinker with the |
|
I also have a 61a2, and i managed to set up my RM4 Pro with working RF devices, thanks for your work @kiwi-cam !
For IR learning, use the button in control centre. For RF learning, follow this comment, where you learn the buttons using @kiwi-cam Since i now got multiple IR and RF devices working on my RM4 Pro, can I help you with debugging somehow? |
Hi this is not working for me :( |
Hi where is the installation guide ? |
|
Hi everyone, The manual download and copy of the index.js was before I setup the beta release. All you'll need to do now is install the beta version. I've added some more debug information in there too to try to help. So new steps are:
Then I'd love to see the logs from an RF learn. Particularly, the packets received from the RM4 when no codes are sent, and when a signal is sent during learning. That'll help identify the packets recieved, then we need to extract the codes from the packets. If anyone is interested, this is all in lines 430:480 of index.js in |
No codes sent during learning:Sent one code multiple times:Hope this is helpful. Both times, the huge amount of logging seemed to stress the bridge, causing the state in the UI on the iPhone to not update properly, i.e. show that learning stopped in the end. |
|
That's not what I was hoping for... but helpful. I'm guessing that param 9 is received on all learn packets and byte 6 is 1 when data is received. Anyone want to install beta.6 and repeat? |
|
Hi @kiwi-cam I installed beta6 and logs here. [7/7/2020, 08:54:13] [Config] Changes to config.json saved. [7/7/2020, 08:55:12] Got SIGTERM, shutting down Homebridge... [7/7/2020, 08:55:14] [Broadlink RM] [DEBUG] packet 5aa5aa555aa5aa550000000000000000000000000000000000000000000000009bce000026606a00050024dfa7d3299001000000cdbe00002228902f06d95d101d2c5e9ca6ff44b8 [7/7/2020, 08:55:15] [Broadlink RM] [INFO] Listening for Broadlink devices on 192.168.2.108:54270 (UDP) [7/7/2020, 08:55:16] [Broadlink RM] [DEBUG] packet 5aa5aa555aa5aa550000000000000000000000000000000000000000000000009dce000026606a00070024dfa7d3299001000000cdbe00002228902f06d95d101d2c5e9ca6ff44b8 [7/7/2020, 08:55:17] [Broadlink RM] [INFO] Listening for Broadlink devices on 192.168.2.108:34031 (UDP) [7/7/2020, 08:55:18] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null [7/7/2020, 08:55:27] Homebridge is running on port 51674. |
|
Thats what I get with beta.6 while pressing buttons on my RF remote. |
|
I'm confirming successful RF scan via python-homebridge cli tool. I was trying code |
How to install ? @Stichoza |
|
@burakcankose |
|
I tried it too. Thats what I get. Any idea what's the problem ? |
|
Try replacing |
|
@Stichoza : Magic !!! this worked for me too |
|
Hi ! I tried this but discovery OK! but learn have error. Traceback (most recent call last): |
|
Thats what helped in my case : |
Yes ! Thank You ! |
|
Looking forward to seeing a solution for RM4 Pro. Im using the official homebridge image and have some trouble getting python cli to work. as of now I'm still stuck with a RM4 Pro with homebridge running and not connected to any of my rf switches :( |
|
hi;, tried the latest beta with rm4 and it"s not working when trying learn button on RF [``` [8/18/2020, 5:10:31 PM] Got SIGTERM, shutting down Homebridge... [8/18/2020, 5:10:45 PM] Homebridge is running on port 51501. |
|
Hi all, { |
|
So is support for the RM4 Pro now part of the official release or its still in beta? |
|
It's mostly there :-) RF Learning is the last hurdle. If you've got existing codes it works 100%. |
|
Hi guys, Commenting this to follow-up, I have the RM4 Pro and unable to scan RF codes as well. Thanks, |
|
This should now be fixed in 4.3.8 |
From: lprhodes#641 (comment)
and
lprhodes#644 (comment)
Need to add support for RF RM4 Devices with codes 0x61a2 and 0x6026
The text was updated successfully, but these errors were encountered: