Broadlink RM Pro Remote

[thekevinkalis]

Hi all,

Apologies if this has come across before, but there’s so much information and I’m such a noob with Home Assistant, I get a bit lost.

I’ve got a Home Assistant installation and I’d like to add a seperate section for my remotes from my Broadlink RM Pro.

Now I’ve gotten as far as learning the codes and actually adding the commands to my configuration.yaml file, but it’s very basic. As an example, I’ve got my volume buttons mapped, but they show up as ‘switches’ within my Home Assistant, so pressing the ‘On’ button in HA turns the volume up and the ‘Off’ turns the volume down.

I would like somethings similar to this:

Custom UI: Tiles

Tiles custom state card for Home Assistant [preview] Download and more info at GitHub: https://github.com/c727/home-assistant-tiles Known issues: -remove/disable more-info-dialog in state and header card -if the original entity is it the same view the browser scrolls to it after clicking a button

Let’s just assume I’m incredibly dense. Where would I start? I’d even settle for something simpler, just a list of buttons, somewhat organised, that represent each function.

Also, it seems the mapping for the Broadlink seems to be either On/Off. I can’t seem to get the directional buttons (up, down, left, right) configured properly. Is there a workaround for this?

Here’s the excerpt from my config file for the broadlink

  - platform: broadlink
    host: 192.168.2.000
    mac: '--:--:--:--:--:--'
    timeout: 15
    switches:
      tv_sony_volume:
        friendly_name: "Sony TV Volume"
        command_on: '******************************'
        command_off: '******************************'
      tv_sony_power:
        friendly_name: "Sony TV Power"
        command_on: '******************************'
        command_off: '******************************'

Any and all help would be appreciated.

[letherwin (Marco Crocellà)]

Instead of switches I created a bunch of scripts, all with the specific channel code:

lg_down:
alias: LG Channel Down
sequence:

• service: switch.broadlink_send_packet_192_168_1_132
  data:
  packet: JgBgAAABK5MTEhMSEzcTEhMSExITEhMSEzcTNhQSEzYUNhQ2FDYUNhQ2ExITEhMSExITEhMSExITEhM3EzcTNhQ2FDYUNhQ2FAAFKwABK0kTAAxjAAErSRMADGIAAStJEwANBQAAAAAAAAAA
  lg_channel_1:
  alias: LG 1
  sequence:
• service: switch.broadlink_send_packet_192_168_1_132
  data:
  packet: JgBIAAABKZUSExEUETgSExEVEBUQFRAVEDkRORITEjgRORI4ETkROBM3EhMSExITETkRFBEVEBUQFBE5ETkRORITETkRORE5EQANBQ==
  lg_channel_2:
  alias: LG 2
  sequence:
• service: switch.broadlink_send_packet_192_168_1_132
  data:
  packet: JgBgAAABKZURExITEjgSExEUEhMRFBEUEjgROREUEjgTNxI4EjgROBITEjgSExEUETkSExEUERQROREUETkROREUETgSOBI4EgAFLQABKEsSAAxjAAEoSxEADGMAASlLEgANBQAAAAAAAAAA

This way you can use them everywhere you like, in a switch, in a custom card or, for me, in appdemon to have a remote control that I can use directly from my smartphone:

Main arguments, all optional

title: LG Remote
widget_dimensions: [80, 100]
widget_margins: [1, 1]
columns: 8

label:
widget_type: label
text: Power On

layout:
- power, tvpc
- channel1, channel2, channel3, volup
- channel4, channel5, channel6, voldown
- channel7, channel8, channel9, channelup
- blank1, channel0, blank2, channeldown

power:
widget_type: script
title: Power
icon_on: mdi-power
icon_off: mdi-power
entity: script.lg_on

tvpc:
widget_type: script
icon_on: mdi-television-box
icon_off: mdi-television-box
entity: script.lg_tvpc

channelup:
widget_type: script
icon_on: mdi-chevron-up-box
icon_off: mdi-chevron-up-box
entity: script.lg_up

[thekevinkalis]

Hi, thanks for the info, that certainly seems like the best solution.

I love the style you used for the remote and buttons. How did you go about setting up the buttons. I’ve seen somewhere that people use picture entities.

[letherwin (Marco Crocellà)]

that’s appdaemon standard, it isn’t lovelace.
In my hass.io interface I have a normal media-control card:

I use the appdaemon interface for my smartphone, with a quick link: