From what you’ve described, It sounds like TV’s manufacturer decided to use the version of Netflix designed for mobile devices com.netflix.mediaclient instead of the version designed for Android TV devices com.netflix.ninja. That is why the Firemote card isn’t working as expected for you.
You described trying some ADB commands which resulted in errors. I see these sorts of things all of the time, so I’m confident that we can get it working for you! Unfortunately, it might take some back and fourth between us before we find something that works. Let’s try these steps. If one of them works for you, there is no need to go onto the next one:
Is it possible to download the Android TV version of the Netflix app for your TV? I’m guessing that it isn’t, but if it is, it would fix this immediately.
What is the result or error that you see when running the following ADB command? adb shell am start -n com.netflix.mediaclient/.ui.launch.UIWebViewActivity
What is the result or error that you see when running the following ADB command? adb shell am start -n com.netflix.mediaclient/.ui.launch.UIWebViewTabletActivity
What is the result or error that you see when running the following ADB command? adb shell am start -a com.netflix.action.NETFLIX_KEY_START com.netflix.mediaclient
If you run the command adb shell pm dump com.netflix.mediaclient, what do you see under Activity Resolver Table → Non-Data Actions? As an example, the com.netflix.ninja app produces this:
adb_response: >-
Starting: Intent {
cmp=com.netflix.mediaclient/.ui.launch.UIWebViewTabletActivity }
Error type 3
Error: Activity class
{com.netflix.mediaclient/com.netflix.mediaclient.ui.launch.UIWebViewTabletActivity}
does not exist.
I think this is what was requested, if you want the whole message, I’ll add it, although the dump is very big, I don’t know if there is a spoiler bubble to hide it:
Yay! I’m so glad that it’s working for you! Also, your answers to my questions were perfect!
To answer your question about “adb shell pm dump xxxx”, I usually don’t start with that method. To start, I follow the procedure I posted in the Firemote wiki article named Providing Details for App Launcher Requests. First, you launch the app on your device, then while it’s open you run this command: adb shell dumpsys window windows | grep -E 'mCurrentFocus|mFocusedApp|mInputMethodTarget|mSurface'
After reviewing the response from that command, I attempt to use that data to write a workable ADB command. if I’m unable to make an ADB command that works properly, then I’ll go for the “adb shell pm dump xxxx” to hopefully provide me with some additional information or other things to try.
Love the card, Problem I’m having is the controls stop being responsive. Anything related to the thumb pad or volume will stop working after awhile. However, the shortcut buttons to apps work fine, Only thing that seems to fix the issue temporarily is rebooting the server
What you are describing is a known limitation with how the Amazon Fire TV remote controls and their devices communicate. Since Firemote uses multiple ways to control your devices, it can sometimes be subject to this hardware issue.
Since this is a common thing, I’ve written a few help articles about it over on the Firemote Github page:
I’ve done counteless hours of research and tried many things to try to work around this hardware issue, but as of right now it appears that there isn’t a solution.
To work around it, you could keep the physical remote handy to just simply press a button on it to regain control (as mentioned in the above linked help articles) , or you could set your Compatibility Mode option to Strong (Slower), if you are OK with the tradeoff that your navigation will likely be less responsive.
Doug, this is a fantastic card. Thanks for all of your hard work on this. I am wondering though, is there any way to make it a pop-up, so if I touch the entity on my dashboard, it comes up over the top?
Hi!
Meanwhile, congratulations on this WONDERFUL card
I also have the same problem:
I left everything at “default”, but (only) the following 3 buttons don’t work:
volume-up
volume-down
mute-button
I cleared the cache and tried on different browsers…
I would like to avoid using the “Button Overrides” feature.
Do you have any suggestions?
Thanks
My configuration is the following:
type: custom:firemote-card
entity: media_player.fire_tv_192_168_1_155
device_family: amazon-fire
device_type: fire_tv_stick_4k_second_gen
compatibility_mode: default
visible_name_text: Fire TV
visible_name_text_color: '#ffffff'
name_position: top
scale: '80'
app_launch_1: prime-video
app_launch_2: netflix
app_launch_3: function-app-switch
app_launch_4: amazon-music
Another “small nitpick”, if you allow me:
the color of the ‘Amazon music’ button on the card appears to be a light blue but, in reality, on the physical remote control it is a fairly dark blue.
Could you please change the CSS ?
(in the meantime can I solve it in another way?)
Thanks for the encouragement! I’m glad that you like my card!
This is happening because volume control isn’t handled in your fire stick itself. Typically during the setup process, you would train your physical remote to properly control your TV using infra-red (IR) signals.
There is a way to make Firemote do this without a physical remote by configuring your Firestick to send volume commands through the HDMI cable instead. I recommend taking a look at the section Why won’t the volume, mute, and/or power buttons work from my Firemote card? in the Firemote readme FAQ section. It will walk you through the procedure.
I had originally created that button and its colors based off of some official logo I found somewhere. Now that I look at how the logo appears in the menu and the logo in the appstore, I’m inclined to change it from this
(background color #00a8e1)
to this
(linear-gradient(141deg, rgba(139,226,235,1) 0%, rgba(43,199,211,1) 100%)
However, since you mentioned that you have a physical remote with this button on it, I did a quick search and found an image of your remote online and tried to sample the colors. I came up with this:
(background color #373e8f)
and now I’m conflicted. Both of the new options have much better contrast, so I should switch to one or the other of those new options. What do you think?
Also, how close is #373e8f to the color you have on your physical remote?
It’s true!
I hadn’t thought about the fact that the physical remote control of the Fire Stick sends (also) IR signals.
For everyone’s benefit in the following photo you can see that the remote control sends infrared signals when you press audio buttons or power button, and then directly control the TV:
I also experienced that, instead, by pressing the Alexa button the remote control sends another type of signal (I don’t think it’s IR) via a blue LED photodiode… Does anyone know what type of signal it is?
For all the other buttons No LED on the remote control lights up. So (I think) wifi signals are used… correct?
Anyway:
I followed the guide for enabling the CEC controls (even though I already had them enabled in the settings menu).
I tried both ‘Manual’ and ‘Auto’ modes but they don’t work on the card.
Instead the controls of the audio work with the physical remote control.
If there’s no alternative I think I’ll have to use scripts with buttons… I’ll try
I would say that the second new option is definitely more faithful to the original.
Perhaps the blue should be even more accentuated…
To give you an idea, I will send you a photo of the physical remote control directly
(I hope the photo is of good quality):
Did you remember to also check the settings of your TV as well? Typically CEC needs to be enabled on both the Fire stick AND the TV / Audio Receiver to function properly. I’ve also seen this fail sometimes if there is a poor quality HDMI cable connecting the two devices together. I’m not sure if that applies to your case or not.
Close. The physical remotes use Bluetooth wherever possible.
I agree. You’ll see it this way in the next official release.
Because of the way Firemote sends commands to your media devices, currently there is no path to making voice commands work. That is why I have replaced the alexa button with a keyboard button. It comes in VERY handy when you need to type into an input field. The keyboard button is actually my favorite/main use case for Firemote.
Now I dash by another idea in his head…
I configured the card to control my Android TV and, even in this case, I managed (at least partially) to make it work.
The question is:
Is there a way to replace the card skin with an image of my physical TV remote control?
You can select any of the 24 options from the Remote Style menu that you would like:
If none of those are what you are looking for, then go over to the discussion Poll: Vote for what gets added next! and vote for your request. There are a lot of other users who are also requesting new things, so I try to be fair.
)
Both of the new options have much better contrast, so I should switch to one or the other of those new options. What do you think?
YAY!
