PRProd / HA-Firemote

Apple TV, Amazon Fire TV, Fire streaming stick, Chromecast, NVIDIA Shield, onn., Roku, Xiaomi Mi, and Android TV remote control card for Home Assistant
GNU General Public License v3.0
454 stars 68 forks source link

App launcher 2 for Roku #459

Closed siesta5787 closed 2 months ago

siesta5787 commented 3 months ago

Describe the bug

I am using app launcher 2 for my roku and love it. Only thing that doesn't work is the hamburger button doesn't work. I think because that is specific to firetv? I was hoping that it might be an easy fix to have a roju specific version that replaces that button with the * button on the roku remote. Its the only thing missing and this layout is way better than standard roku remote since that doesn't have volume buttons and its tougher to use. Also it would be cool if you could see the current playing channel / media control built in one which adds some duplication and isn't layer out as nice. Thanks for your work on this. Super helpful!!

To Reproduce

Click the hamburger button when using app launcher 2 on roku.

Expected Behavior

Error message.

Which Type of Device Do You Own?

TCL and ONN with built in roku.

Troubleshooting Steps Completed

No response

Additional context

No response

PRProd commented 3 months ago

Greetings @siesta5787!

You are correct. The hamburger button is not a button that the Roku family has on its remote controls. If you get a chance to read through closed issue #435, you will see that this was also discussed and then patched about a month ago in the Firemote version v3.4.7 released on June 6, 2024.

If you are seeing an error message that looks like this when you press the hamburger button, then you should update to the latest Firemote version.

Service androidtv.adb_command not found

If instead (and/or after you update), this informational dialog message was displayed:

image

Following the link shown in this box https://github.com/PRProd/HA-Firemote#button-overrides provides instructions about how to make that button (or any other button) do something else.

For example, adding something like this to your Firemote card's YAML should override the Hamburger Buttons non-functionality in AL2 with the Roku device family's options/info/* function:

button_overrides:
  hamburger-button:
    service: remote.send_command
    target:
      entity_id: {{ REPLACE THIS LINE WITH THE ID OF YOUR ROKU REMOTE ENTITY }}
    data:
      command: info

Obviously, you'll want to edit this to properly fit your situation. A full list of valid Roku commands (like the Roku "info" command) can be found here.

Another example similar to this was provided and accepted here in #435 as well.

In regards to this:

Its the only thing missing and this layout is way better than standard roku remote since that doesn't have volume buttons and its tougher to use

If you change your mind someday about your "tougher to use" experience, you actually CAN have volume control with the native looking Roku Firemote:

image

At the bottom of the App Launch Button dropdown menus, you will see a selection of device specific Functions. In that list, I've included volume controls, as well as some other features that might interest you: image

In regards to this:

Also it would be cool if you could see the current playing channel / media control built in one which adds some duplication and isn't layer out as nice

I've considered doing something like this as an add-on to the AL1 or AL2 Firemotes, or possibly making a new layout. If this is something that interests you, please sketch some ideas for me, and include them when you open a new Feature Request. It could end up being a popular feature if we can create something that everyone likes.

In regards to this:

I am using app launcher 2 for my roku and love it. ...Thanks for your work on this. Super helpful!!

Thank you for your kind words! This is a passion project of mine, and I'm always happy to hear from folks who get some enjoyment or benefit from using it!

I hope this helps!

-Doug

PRProd commented 2 months ago

@siesta5787 ~

Did you find my reply to be helpful enough that this issue can be closed? If not, we can leave it open until all of your concerns have been addressed. Please let me know either way. Thanks.

-Doug

siesta5787 commented 2 months ago

Yes thank you very much for the helpful rely. I will put a thought together on the layout. Sorry I missed the closed issue.

PRProd commented 2 months ago

That's great news, @siesta5787! I'm glad I could help!