Device identifying itself as ‘24614’ is not currently supported. Please report this to the developer!
RM pro… ideas? Version: org.openhab.binding.broadlink-2.5.1-SNAPSHOT
Thank you for the link, but the app doesn’t work with newer RM devices.
The app was last updated in 2018.
Is there any way or any binding that works with a RM 4 Pro?
I’ve been trying to find a way to learn RF codes with the RM4 Pro, but, so far, with no success.
1 Like
Hello all,
I’m trying to use a Broadlink RM4 mini; I can ping it but it is not recognized by openHAB. The log reports:
2020-09-16 22:40:44.942 [ERROR] [nding.broadlink.internal.ModelMapper] - Device identifying itself as ‘24846’ is not currently supported. Please report this to the developer!
Is it possible to add this code somewhere or must the add-on by updated?
Thanks,
Anders
Hi Anders,
Sorry for the delay, but BETA 12 now contains support for your RM4 device:
Cheers,
John
1 Like
Thanx a lot John!
I have tested home assistant because there the binding works great but home assistant is not realy my thing, I am an openhab user for a while now and like it more then HA.
I get no errors! Great, but it does not work…
openHAB 2.5.9 Release Build on a rasp 3B+
Your latest BETA 12
Item:
String Broadlink {channel="broadlink:rm4:xx-xx-xx-xx-xx-xx:command")
broadlink.map
TV_on=0000006d00220002015700ac0015001600150016001500410015001600150016001500160015001600150016001500410015004100150016001500410015004100150041001500410015004100150041001500160015004100150016001500160015001600150041001500410015001600150041001500160015004100150041001500410015001600150016001506890157005600150e94
I actualy converted it to hex (I got the code via HA) it was
JgBYAAABJpURFBEUEjgRFBEUERUQFREUETkROREUETkRORE5ETkROBEVEBURFBE5ERQRFBEUERUQORE5ETkRFBE5EjgRORE5EQAFHwABJksRAAxZAAEnSxEADQUAAAAAAAAAAAAAAAAAAA==
As a test a simple rule:
rule “tv on”
when
Item TT_sw_Test changed
then
Broadlink.sendCommand(“TV_on”)
end
I have no errors but IR code is not send or is wrong? TV does not turn off…
Does anybody know a simple way to learn the IR hex codes with a RM4C mini?
I am not a programmer, I have got the codes for HA but I am not sure if I convert them right. I have done String to hex via an online tool.
thx
Authentication failed:
java.net.ProtocolException: Response from device is not valid. (0x22=0xFF,0x23=0xFF,0x24=0xFF)
Solution: In android Broadlink app, turn off the Lock device switch shown in the image and Openhab will see the device again.
Firmware: v44057
1 Like
hello, thanks and welcome!
Is your RM4mini connected to the cloud too?
When Openhab automatically identified rm4, not work.
When Openhab add manually rm3, work online, but not send ir data.
I disconnected from the cloud.
Connecting Broadlink.WinApp, but app message is Writing compatible device not detected.
Device is 0x5f36.
EUREKA!!! It works!!!
I’m using beta12 with RM4pro (6026) and I can send IR signals to my air conditioner…but winter is coming 
I’ve tried to learn RF code but “No data received…” …is there an other “learning mode” for RM signals?
thanks!!!
themillhousegroup any help?
here we are:
./broadlink_cli --device "0x6026 192.168.82.160 936de4a7df24" --rfscanlearn Learning RF Frequency, press and hold the button to learn... Found RF Frequency - 1 of 2! You can now let go of the button Press enter to continue... To complete learning, single press the button you want to learn Found RF Frequency - 2 of 2!
If I add like RM3 it is online but can’t send signal.
If I add as RM4 then “Response from device is not valid. (0x22 = 0xFB, 0x23 = 0xFF, 0x24 = 0x00)”
There may be a problem in B12 because 0x5f36 RM3 should send the signal with the parameters of RM4.
Openhab automatically recognizes the device as RM4.
broadlink_discovery:
###########################################
RM4
broadlink_cli --type 0x5f36 --host 192.168.1.238 --mac 24dfa77ac05b
Device file data (to be used with --device @filename in broadlink_cli) :
0x5f36 192.168.1.238 24dfa77ac05b
The problem is “BroadlinkProtocol.class”:
final boolean error = packet[34] != 0 || packet[35] != 0;
if (error) {
throw new ProtocolException(String.format(“Response from device is not valid. (0x22=0x%02X,0x23=0x%02X,0x24=0x%02X)”, packet[34], packet[35], packet[36]));
}
I’m running a RM4 but the temperature/humidity channels seem to be wrong. Actually humidity delivers the temperature and temperature is 0… Instead the broadlink_cli output seems to be right:
./broadlink_cli --type 0x62bc --host 192.168.103.9 --mac 24dfa74***** --sensors
temperature 24.27
humidity 60.57
Running on BETA 12
Thanks for the bug report @Flip, you were exactly right. The RM4 devices have 2 more bytes in their protocol responses. This is now fixed in Beta 13:
Cheers,
John
1 Like
Hello, any news for openhab3 binding?
Thank you.
1 Like
Hi Viktor, I’m experiencing the same issue with the same device (type 5f36). Conversely, the device works as expected with the Python Control for Broadlink library.
I also found it easier to switch Python Control for Broadlink.