Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Override app launchers #572

Open
manonstreet opened this issue Dec 1, 2024 · 3 comments
Open

[Feature Request]: Override app launchers #572

manonstreet opened this issue Dec 1, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@manonstreet
Copy link

Is your feature request related to a problem?

No response

Feature Request

The bring your own device feature (entity:none) allows for some really cool possibilities with unsupported device types. I would like to use this capability to launch standard smart apps and leverage Firemote's extensive image library already in place. However this is currently not possible since the App Launcher buttons are tied to the device entity (effectively passing a media player source).

In order to override existing app launchers one of the following would be needed, either:

  1. When creating a custom launcher, extend another key to refer to an existing app image. For example, "app_image: netflix". This would use the embedded netflix image on the custom launcher. The downside of this approach is that overlay and highlighting for when the button is pressed would not work.
  2. Extend button overrides for app_launch_1...app_launch_N. With this approach, app launchers can refer to native smart apps (including the highlighting visual on select), and then a button override can hijack what pressing the button actually does.

While I am not looking to use this capability with AL1/AL2 remote style, I can imagine it would be particularly useful in those case.

Additional Comments (optional)

No response

@manonstreet manonstreet added the enhancement New feature or request label Dec 1, 2024
@manonstreet
Copy link
Author

I found a workaround for this issue, so no longer need on my end if this doesn't make sense to the broader user base.

@PRProd
Copy link
Owner

PRProd commented Dec 5, 2024

Out of curiosity, is your workaround in any way related to the way one user set up their config in issue #547?

In my opinion, your request is still an intriguing one. At the very least, being able to use built-in artwork for custom app launcher buttons is an idea that I'd love to add.

I'll keep this open for now while I think about how best to proceed.

@manonstreet
Copy link
Author

manonstreet commented Dec 5, 2024

My workaround is partly related. My goal was to have firemote support my LG WebOS TV. I already use firemote with my 3 other Roku stick driven TV's and I built a visual switcher leveraging the decluttering card to show the media player entity, plex entity (if the input is on plex), as well as the remote control.

For the LG, I used aspects of this implementation. And I also stumbled upon the same phenomena linked to in issue #547 without finding that page. What I noticed is that I can use this configuration:

type: custom:firemote-card
entity: media_player.lg_webos_smart_tv
device_family: apple-tv
device_type: other
defaultRemoteStyle_override: AFJTV

And as luck would have it, the json values for appName used by Apple TV matches exactly the source name values LG uses, for the apps that I care about (YoutubeTV, Netflix, Plex, and Disney+). Because of this match, I didn't have do anything special at all to make the app buttons work (no overrides or custom launchers necessary).

End result:
Screenshot 2024-12-05 at 4 11 39 PM

And in case you are wondering, those letters are initials for my wife and I that uses a custom launcher to run a script. That script detects the selected source on the media player, and if needed, automatically types in the profile PIN (parental restrictions).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants