This is awesome, could you please put a few words around it as I’m unsure of the image order under “Example - Power Switch” say I don’t have any of the Example - Power Switch config setup, where do I start?
Like I cant figure out how you got the item "Living Room - Samsung TV - IR - Power as a Link beside the command, I cant seem to do that?
Had a call with Richard and we walked through setting up the on/off as string, which works.
The switch should also work as long as ON/OFF is in the map file as well (I think that might have been the initial miss).
Edit:
Porlbem solved, I’ve created the Broadlink.map file at /etc/openhab/transform
by ‘sudo nano Broadlink.map’
Then I’ve added the Variable name - TV_POWER={IR-CODE}
And it’s worked.
with sudo nano broadlink.map… you open an editor, and with saving you created the file “broadlink.map”… thats the reason… before you got an error message that there was not the recmonended file “broadlink.map”…
I am still new to openHAB, but I am starting to find my way around. I’m running OH 3.3 on Win 10; an easy install. I have configured a few simple TP-Link switches (HS-103) and their bindings without issue.
Encouraged, I moved on to the Broadlink RN4 mini. I’ve configured it with the Broadlink app to connect to the local network, confirmed it’s IP and MAC addresses from the router and installed the unofficial binding (Broadlink 3.2 beta1). Using the console, I confirmed the binding is installed and it is active.
When I add the thing, I get “communications_error. Couldn’t Authenticate”. The openhab.log Broadlink discovery error identifies it as an unknown device.
Device identifying itself as ‘21014’ (0x5216) is not currently supported. Please report this to the developer!
The device is a RM4 mini with temperature and humility sensors. I have this suspicion I am overlooking something.
I have tested the new broadlink binding in OH3.4 and reported my results on my RM mini in this thread. At present I am not able to use my broadlink.map file with previously captured IR codes.
Support for other devices is not available at present but the docs say that support should be possible.
Just want to let you know, that the version 3.2 BETA 1 (version from Jul 7, 2021) from the themillhousegroup/openhab2-addons is still working without issues after migrating from OH 3.3.0 to OH 3.4.0 (via docker image update). I’m using two RM2 devices and the map files with IR and RF codes are still working.
I remember that a couple of years ago I had a similar problem with the Broadlink RM3. For me it worked that I ping the RM3 every 60 seconds to keep the network connection alive.
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.