Broadlink integration - what does it do?

Configuration
1

I have a Broadlink RM Pro and RM Mini 3. I’ve added the Broadlink integration to my HA 0.118.3 setup, and both devices are listed in my setup, but as far as I can see the only way to set up devices (e.g. IR/RF appliances) which are controlled by the Broadlinks is to create switch items in configuration.yaml, which was possible in much older HA releases without the need to explicitly add a Broadlink integration component.
What’s the point of adding Broadlink integration from the Lovelace UI? Does it make it any easier to add Broadlink appliance controls?

2

I have the same. I assume it’s the beginning of being able to configure through the integration rather than having to use yaml.

3

It’s just a way forward with GUI setup. To make the best use of your Broadlink devices I suggest using this. I’ve been using it flawlessly for years now (including it’s predecessor).

4

So am I right to assume that HA Broadlink integration offers no benefits at the moment to anyone who uses a Broadlink Remote to control other appliances via IR or RF? (i.e. configuring switches etc in configuration.yaml is still required)

5

What do mean here? Once the Broadlink device is completely configured in HA there is a lot you can do with it. For example I have one to control my non-smart amplifier by turning it on/off and to the correct input based on my TV or Chromecast Audio being in use. Without integrating the Broadlink with HA that would not be possible.

Yes, you do still need some YAML to get things completely setup. My guess is that the move from YAML to GUI for the Broadlink Integration is still in progress, with only the base setup currently being done via the GUI and the rest YAML.

1 Like
6

To put it another way: I already had my Broadlink-controlled devices defined in the switch: section of my configuration.yaml, and they all worked fine before I installed the new Broadlink integration from Lovelace. I don’t see what benefit I have obtained from installing the integration.
What am I missing?

7

It is simply that the inclusion of Broadlink devices into HA is now done via the GUI rather than YAML. No new features or functionality. Adding Broadlink devices (ie: RM3 mini etc.) can ONLY be done via the GUI now, but the actual switch entities to get control still requires YAML. Like I said above, I think it is simply a work in progress.

8

Presumably if I don’t add the Broadlink integration I don’t lose any functionality?

9

You need the Broadlink Integration to have the actual device included in HA

10

I was previously using my Broadlink devices fine (with HA 0.65.0) without having installed the Broadlink integration - just entries in the switch: section of my configuration.yaml. That’s what I don’t understand - I’ve installed the integration but I don’t see any more usable functionality than I had before I installed it.

11

As a said before there is no new functionality, only a change in how part of the config is done since HA 0.115. Now a (small) part of the config is via GUI, the rest via YAML.

Breaking change in version 0.115

If you read it you will see that all config entries except switch: have been removed. You will notice in the example given in the blog post that the IP address (host) config has been moved from YAML to GUI. That is the key change that is required ever since that version of HA.

Here is my pre-HA 0.115 code for inclusion of a Broadlink device. This config entry was removed and now sits via the Integrations GUI.
#switch:

switch:
  - platform: broadlink     ### REMOVED FOR HA 0.115.0
    host: 192.168.0.71       # 'lounge IR'
    mac: '34:xx:xx:xx:xx:xx'
    type: rm_mini
    friendly_name: 'Lounge IR'

I guess the difference is that I don’t have my remote codes as switch: entities since I’m using the far superior SmartIR custom_component. Since you are still coding your remote codes, you can still use / need to use, the switch: config entry.