I successfully control devices with Broadlinmk RM3PRO by sending commands from metadata, but how to control my devices by voice with google I don’t know. Also interesting!!!
It works similar to adding lights to Google Assistant (i.e. create a supported GA item like a switch).
In my case I use a dummy switch and a rule:
1 Like
Thx, I think I understand how to control devices like lamps or switches(on/off). But I also have a device-like multimedia player with many commands (not only on/off), like “increase/decrease volume, next video, stop/pause”, how to control this type of device, or for example I have blinds http://prntscr.com/12u9u2g it has 3 commands.
PS doesn’t know if I correct, but it looks like you use a socket with a power meter to check that your TV spends energy (to check it enables or disables)? Do you use SP3S? because I don’t know how to get the power information, always null
Yes, you are correct. My Samsung TV, as well as my Mibox, also got multiple other commands controllable by IR. The problem though with IR is that even for those, you will need some kind of control like a switch as each i.e. volume increase is a single IR signal sent. Further you will not get the actual current state of, say, volume or even if the TV is on/off.
I did some testing with volume IRs as well as left/right/up/down IRs for my Mibox and basically also had to use a switch item for it. If there are other solutions, happy to learn about them though as it is not the easiest (i.e. you cannot tell Hey Google, set volume to 50).
Hence I am using this in combination with a Xiaomi Smart Socket that my TV is plugged into which then sets the Samsung TV either to on or off (did not write that rule yet to update a separate status item).
Your Broadlink binding 3.1.0.b5 runs well on my OH3.1.0M4. Now, with M5 being available and for future 3.1, I ask if you could help with a recompile due to changes in UoM dependencies (Upgrade Units of Measurement dependencies by wborn · Pull Request #2319 · openhab/openhab-core · GitHub)?
Looks like this is needed to be fixed… I was runnning OH3.0.2 without problems…
but by testing some features of M5 concerning openhab gooogle integration is was sturggeling with broadlink binding… At least broadlinks were not anymore recognized.
@moment returning to OH3.0.2 by etching the backup
Thank you, @proyleg. This works flawless with my RM4 Mini incl. cable sensors for temp/hum on OH3.1.M5.
Thank you very much!
It is also working very well with my RM4Mini and OH3.1.M5 after upgrading from M3 (it was not working with OH3.1.M3). I recorded the codes with the python-broadlink module (GitHub - mjg59/python-broadlink: Python module for controlling Broadlink RM2/3 (Pro) remote controls, A1 sensor platforms and SP2/3 smartplugs).
After struggling a bit with the broadlink-mqtt solution I was very happy to find this binding.
However, it was quite difficult to find this binding, as this thread is huge and also the topic is not suggesting a working binding.
Are there any plans to add it to the official openhab-addons repository?
Hi Guys
Im using 2.5.10 BETA and see this for my BEOK thermostat, is the a better version that supports this device?
17:39:56.252 [WARN ] [l.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Beginning Broadlink device scan...
17:39:56.254 [WARN ] [.internal.discovery.DiscoveryProtocol] - Beginning async Broadlink device scan; will wait 10000 ms for responses
17:39:56.258 [WARN ] [.internal.discovery.DiscoveryProtocol] - Broadlink device scan waiting for 10000 ms to complete ...
17:39:56.285 [INFO ] [l.discovery.BroadlinkDiscoveryService] - Data received during Broadlink device discovery: from 192.168.0.110:80 [78:0f:77:18:43:03]
17:39:56.293 [ERROR] [inding.broadlink.internal.ModelMapper] - Device identifying itself as '20141' (0x4ead) is not currently supported. Please report this to the developer!
See the second post here OH3 · Issue #13 · themillhousegroup/openhab2-addons (github.com)
A precompiled jar seems to have been posted around 5 posts above this one. Note that the build system changed at OH 3.1.M5 so you will need to use a JAR that was built for versions before or after this point in time.
Source code is found here
openhab2-addons/bundles/org.openhab.binding.broadlink at master · themillhousegroup/openhab2-addons (github.com)
It is waiting to be reviewed and merged, see
Hi,
You might want to try the broadlinkthermostat binding - it’s specifically designed for these OEMed thermostats (assuming it’s a Broadlink device underneath, which it looks like it is)
Thanks Matt,
I’ve rebuilt the binding with all the latest PR-recommended improvements for OH 3.1.M5 and later here.
Worth mentioning that due to renaming of some config parameter and channel names, you’ll probably want to delete any Broadlink Thing s in your system created by previous versions of this binding, and then re-add them once you’ve installed this one.
Cheers,
John
I am on the stable version of openhab:
openhab/stable,now 3.0.2-1 all [installed]
How do I install the binding for that version?
Is there a binding for that version?
Thanks
It should not be hard to get it working, however I really really encourage you to move to the milestone builds until 3.1 stable is released. Since the stable is the first one ever in the V3 lineup, it is missing a lot of stuff that has come out. The UI has a lot of new stuff.
Ok thanks. I will upgrade and see what breaks 
After changing parameter name
mac
to
macAddress
my textual thing configuration worked without issues with RM4 mini incl. cable sensors.
I am also using textual configuration. If I use macAddress, I get a blank MAC in the Thing in the UI and I get an “awaiting configuration” error. With mac the MAC address appears correctly in the UI.
Even with the correct config, I am still getting “cannot authenticate” on my BG1 socket. Do I need to supply any more config details?
(Openhab 3.1.0.M5 with latest version of the binding from the link above)
@barneyd I suggest to temporarily find your device by autodetect, to confirm it working properly with the binding, and move to textual config only after that:
- Comment your thing in .things file (or rename .things to e.g. .thing);
- check it is removed from things list; if not stop openhab, do
openhab-cli clean-cacheand restart - go to Main UI / Things, add new thing by “+” and proper binding; detect your device
- Give it a temporary name
- Find it in things list, open it
- in “Thing” tab configure to your needs (IP, mac, etc) and then change to “Code” tab. This should present the defined parameters with required parameter names.
- modify your textural .thing(s) file with different thing name, change back to .things file name; thing should appear in parallel to autodetected thing
- Remove the autodetected thing
To check binding version, open openhab’s console in shell, list bindings by bundle:list | grep "Broadlink" and see timestamp at version info. I have 3.1.0.202106150948.