Thank you for creating the binding!
I was able to install and activate the binding on OH 3.4.2 without problems.
However trying to add Broadlink RM4 Pro results in a dreaded “**COMMUNICATION_ERROR** Couldn’t authenticate” problem.
“Lock device” is Off.
Edit, I’ve confirmed that device is accessible using python-broadlink:
I am having problems compiling the jar for OH 3.4.
I basically managed to compile it succesfully, but it does not activate when installing it in my system. There are a lot of changes that happened between the last time i compiled the binding succesfully (OH 3.2) and now, including increassed checks for null annotations, replacement of org.eclipse.smarthome libraries, junit deprecation, mockito deprecation, et etc etc…
@Lionello_Marrelli ,
The branch broadlink-binding-3.4.x from https://github.com/rlarranaga/openhab-addons compiles and runs in 3.4.3. I still need to clean up some warnings in it, but it would be good if it can be tested. I am testing it in my system right now too.
Unfortunately I am not able to compile from sources. If you give me the link to download the addon jar file to be copied in the add-on directory I can do some test.
I have copied it in my add-ons folder and it recognized my A1 sensor and the RM mini. I still have to check if the broadlink.map file is recognized, but so far it works.
Thank you
Sounds good, it should recognize your broadlink file too. I will make some behavior changing modifications in the future, if i have time (i.e.: changing the config location). But so far, i have only made the minimum amount of changes that will allow the binding to be accepted into OH.
One thing you might want to consider is, unload your previous broadlink binging while testing. I run into situations where they conflict because the underlying libraries are compiled on different versions.
Thank you, indeed old binding was not properly cleaned up.
After uninstalling it in Karafe I was able to install the new one.
RM4 still shows the same error though: COMMUNICATION_ERROR Couldn't authenticate
I recently bought RM4 mini… updated the firmware… then I also accidentally upgraded the firmware of my RM4 PRo… now my RM4 pro showing as offiline… this was in OH2.5
Now I’m also learning/trying openhab 3.4.x… I still could not bring online the RM4 Pro… its getting
[handler.BroadlinkRemoteModel2Handler] - Online → Offline due to: Couldn’t authenticate
But I can add the RM4Mini and my other RM3 mini then it goes online…
I’m using org.openhab.binding.broadlink-3.4.3-SNAPSHOT.jar
Yesterday I updated OpenHAB to 3.4.2. Deleted Broadlink binding 3.2.0 from my addon folder and added instead the latest 3.4.3 jar file.
Everything seems to be working properly with my RM4 Pro.
Hi friends,
I’ve been using the RM4 Pro with OpenHAB for the past two years to send commands to several RF controlled ceiling fans and it’s been running great.
However, due to several reasons I’m thinking of migrating away from OpenHAB to Home Assistant.
Before I go through the migration process that will require recreating the whole system, can anyone tell me if there is a similar way to send RF commands with the RM4 Pro on Home Assistant?
So far, I’ve been using this binding to control them in OpenHAB, and I’m wondering if there’s a similar or better way to achieve the same control on Home Assistant.
Hope someone can help
I have some general questions about Broadlink device integration and the available options to integrate RF capable Broadlink devices.
I’ve started about 3 years ago with OH 2.x and now I’m running on OH 3.4.4. Since then, I’m using a “none-official” OH binding from the millinghousegroup with two Broadlink RM2 (aka RMPro+) devices with both IR and RF (433MHz) codes without any issues.
In the meantime the official OH Broadlink (thermostat?) binding has been published, but it states that only the Floureon Thermostat and RM Mini 3 devices has been tested (others may be working also, but not yet tested). The OH binding documentation pointed out, that it’s based on the broadlink-java-api. This library does mention RM2Devices in the READ.me file. It looks like that themillinghousegroup binding does NOT use this broadlink-java-api but instead using it’s own implementation?!
Does anyone know if these two bindings are related? Is the current official OH Broadlink binding the successor of the (older and non-official) themillinghousegroup binding? If yes, the chance to get the RM2 (RMPro+) supported (also with RF) by the official binding is high.
Does anyone of you use an RM2 (RMPro+) with the official Broadlink binding - maybe also with RF codes?
I’m concerned, that after migrating to OH 4.x (which I plan to do in the next few weeks) the binding of themillinghouse group may no longer work with OH 4.x because the last version (3.2 BETA 1) is 2 years old and no more updates are available.
I am in planning to move from OH3.4.5 to OH4 soon as well, with RM4Mini (+HTS2 sensors) in my collection. A test setup of OH4.0.1 shows that the RM4mini is recognized by broadlinkthermostat binding, allows learning, saving, recalling IR commands. HTS2 sensors are not available (feature request posted).