Universal Remote Card

⚠️ BREAKING CHANGES ⚠️

• Auto-filling of custom actions is now handled by the configuration UI.
• Styles are now set using CSS Styles fields which accepts pure CSS with templates.
• Global button styles have been deprecated since they can be included in the global CSS styles.
• Some special shortcut alternate names have been deprecated in favor of one name per special shortcut.
• Template custom actions (not templating) are obsoleted, as there wasn't a good way to handle them in the configuration UI that would be better handled by copying other custom actions.

To update your old configuration, open the remote configuration UI editor, scroll to the bottom of the general tab, click the update old config button, and save. You may have to make some adjustments to your remote configuration if they do not update correctly. Sorry for the inconvenience.

Setup (Almost) Entirely Through the UI

Version 4 of this project introduces a fully functional configuration user interface! No more poring over the README and digging through the out of date Home Assistant community thread to figure out how to use this card! Well, sort of. You'll still have to use YAML to do some templating in fields that don't normally accept text like range and step, and to learn about CSS style options. Still you should now be able to do the vast majority of custom actions setup just through the user interface. You can also hover your mouse over the remote preview, and it will outline the element and display a tooltip with it's element name or CSS selector.

True Universal Support

This card now supports many more platforms out of the box! Previously the default keys and source lists were just for Android TV. Now this card supports these platforms with no additional custom action configuration:

• Android TV
• Fire TV
• Roku
• Kodi
• Apple TV
• Samsung TV
• LG webOS

Note that only Android TV, Fire TV, Roku, and Kodi support the keyboard functions. Adding support for additional platforms can be made via feature or pull requests if there is a way to integrate them with Home Assistant. I personally use Android TV, so I'm very open to further improving the default key and source lists for the other platforms. Keyboard support is also dependent on there being a way to send keyboard commands via Home Assistant.

Multiple Touchpads and Sliders

You can now create touchpad and slider custom actions! Creating a slider or touchpad with the same names as the default elements will overwrite the default ones. Creating slider or touchpads with different names will create distinct ones that you can use to include multiple sliders and touchpads in your remote. Touchpads also now support up to five icons and labels, one for the center and each direction. Use these to clarify what the touchpad does if not just navigation.

You can now also add labels to custom actions. Like other fields these can be templated to include dynamic information.

Rebranding to Reflect Expanded Functionality

When this project first started, it was just to provide Android TV support to an existing project. Since then it has greatly expanded to support buttons, touchpad, sliders, and keyboards on many platforms with several different action methods and many different action types. Because of the greatly expanded scope of this project since release, it is being rebranded as Universal Remote Card.

What's Changed

• Fully functional Configuration UI.
• Rebranded to Universal Remote Card.
• [BREAKING] All deprecated field updates are now done by the configuration UI and saved to the YAML configuration.
• Out of the box support for default keys and sources for more platforms.

TODO

• Rewrite README.
• Refactor repetitive configuration UI code.
• Touchpad hold action menu for all platforms

Full Changelog: 3.9.3...4.0.0-beta.001