Harmony Hub Activity Selector & Button Mapper (Sanytron Astrion & HA)

1

CLICK THE LINK BELOW FOR EXAMPLE FLOW FOR YOU TO RE-CONFIGURE TO YOUR OWN USAGE

Requirements

node-red-contrib-harmony-extra

node-red-contrib-home-assistant-websocket

Functions

Harmony Button Mapper

The Button Press Nodes are exposed to Home Assistant as button entities.

The Flow detects what Harmony Activity is Active and then will Re-Map the button Press to the right device.

image
image952Ă—729 190 KB

Wrap the buttons exposed to Home Assistant in scripts repeat for each button entity

image
image1804Ă—439 26.4 KB
image
image268Ă—741 23.4 KB

Map each script to the ROS TV Card

image
image1155Ă—790 33.3 KB

Harmony Activity Mapper

Provides switch entites that can be used with the ROS Switch Control card

Automatically manages the state of the switches and keeps sync with the Harmony Hub if operating from the Harmony remote, not just the Astrion Remote.

image
image717Ă—763 80.8 KB

Map each switch to the ROS Switch Control Card

These will be available on the remote to switch between activities including off.

image
image1162Ă—872 45.4 KB

NOTE: ROS TV Toggle is mapped to the power button in the ROS TV Card, it switches remote.harmony_hub on (last activity) and powers off using the power_off activity.

image
image418Ă—251 14.8 KB

Keep Harmony Alive

Sometimes NodeRED drops connection with the Harmony Hub, resulting in a non-responsive remote. This flow ensures the connection stays alive

image
image1783Ă—408 78.8 KB
image
image1773Ă—493 34.2 KB

Nvidia Shield + Plex, very poor experience
2

One thing you can try if you are game, to clean up all the individually configured button entities if you dont need them elsewhere you can use a single events node in NodeRed listening for “remote_command” or similar. of course if you also need those buttons in a lovelace dashboard you might as well have them all defined, though you can make button in HA that sends event data too.

And the script I use for each button is just a copy/paste of this:

remote_command_left:
  alias: "Remote Command: Left"
  sequence:
    - event: remote_command
      event_data:
        command: "left"

That gives you one node that outputs “left” when called that you can route as needed.

1 Like
3

I use those buttons in my Firemote Card, the Astrion remote uses the same buttons. Easier to have them available individually.

Once Sanytron allows button.* entities to be mapped directly to the TV ROS Card, I can skip the wrapping my buttons in scripts.