Same device type and also not able to get it working now. It looks like there changed something if you read the topics you also shared, but no idea how to adapt to get it working
Great! I would be able to test it this weekend, but is it required to have OH 2.5.3? Normally I only switch to a new version when it is a stable release.
please don’t use that jar as it will break all broadlink things
as for versioning: there probably won’t be a 2.5.3 stable if there are no bugs in openhab core - this version, especially the snapshot, is for the ability to update the addons: Development of openHAB 3.0.0 and 2.5.x
So is there a consensus on what version of the binding currently works? I’,m on OH 2.5.2 and have installed the 2.5.1 version of the binding which is stuck on initializing on the RM thing. Is there an older version that will work? The 2.1 version was working with my 2.3 install.
Thomas, I tried to use BETA_03 release and received the following error with my RM2:
2020-03-22 09:56:30.756 [ERROR] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-f4-49-34[v]: java.net.ProtocolException: Response from device is not valid. (0x22=0xF9,0x23=0xFF,0x24=0xFF)
2020-03-22 09:56:30.758 [ERROR] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-f4-49-34[v]: Attempting to authenticate prior to getting device status FAILED. Will mark as offline
2020-03-22 09:56:30.760 [ERROR] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-f4-49-34[v]: updateItemStatus: Online -> Offline
Hi,
I need to be able to control two IR devices in my living room: my subwoofer and my projector.
I am considering getting this device:
Two questions:
There seem to be multiple versions of this. Do you know, which is the newest and if it will work with this work with this binding?
(How) Can I train this with arbitrary IR remote? Especially the subwoofer remote is probably not in any database. An I also failed setting up my LG PF-1500 projector with LIRC.
python3 broadlink_cli --type <output from discovery> --host <output from discovery> --mac <output from discovery> --learn
which outputs the codes to the shell which you can enter into the broadlink.map
if it doesn’t work anyways then with an error of wrong length start adding two zeros (00) to the end of the code until it works.
PS: yes i am referencing my repo here which is a fork of a fork of the original work because it was the only way to get it to work for me using a current ubuntu, python3 and my 0x5f36 device. and all other tools also weren’t talking to my 0x5f36; the python lib was the only one with the fix (at the time of forking it was still a pull request which has been merged in the meanwhile)
maybe the original repo https://github.com/mjg59/python-broadlink works now but from what i can tell not with python3 and i was unable to get it working with another python in my ubuntu - but i am not really a python person (neither am i a java person for that matter!)
@ip-ua: that happened to me as well (same error codes!) until i un-did a bugfix John Marshall committed on 7 Jan, then it suddenly started working. but: it occasionally happens again; then i take the thing offline and online again and it works for some time
i am neither a pro in openhab, nor java, nor python and very much not with that weird broadlink protocol, just trying to hack the stuff so it works for my needs and sharing my findings
@KidSquid: why did you change your device type, was the field empty upon discovery? it should be automatically discovered and the type should be the same as if you did python3 broadlink_discovery (described above with python-broadlink), just in int not hex - not manually entered because of some list (usually)
plus which app did you use for setting up the wifi? these don’t work:
cn.com.broadlink.econtrol.international
com.broadlink.rmt
cn.com.broadlink.econtrol.plus
this does work:
at least for android, don’t know & don’t care about that californian fruits
not working means: it sets up fine and is controllable via that app, but neither the binding nor the python scripts can communicate with it…
I changed it after 30 minutes of no connection in the hope that needed to be changed to connect. So I have thrown away the thing…and it was immediately rediscovered and I have left the device type as it…still says it can not find a device at the designated IP. I can ping the device from the OH server.