[New Device Support]: Please add support for the Firestick 4K Max 2nd Gen #201
Assignees
Labels
enhancement
New feature or request
Needs More Information
Cannot continue resolution of this issue without more information
New Device Support
Request to add support of a currently unsupported Amazon Fire device
Comments
GlenWi
added
enhancement
|
@GlenWi - Thanks for your request! I've added the entry for this new Firestick model into the supported Amazon Devices wiki page and created the corresponding product data page. Unfortunately, this is all that I can do at this time. I need one or more of the following items to continue with your request:
|
PRProd
added
the
Needs More Information
|
Here's the result of a Device Interrogation for a 4k Max new version: |
|
Thanks for working on this. I tried event6 but no joy. |
|
I don't even need a Compatibility Mode. It generally seems to work as-is. |
|
Yes - seems setup correctly to me: type: custom:firemote-card |
|
This is odd. So the 4k Max doesn't work for you, either in default or
event6?
Mine works just fine...
J
…On Sat, Oct 14, 2023, 22:14 GlenWi ***@***.***> wrote:
Yes - seems setup correctly to me:
type: custom:firemote-card
entity: media_player.fire_tv_10_1_1_42
device_family: amazon-fire
device_type: fire_tv_stick_4k_max
compatibility_mode: default
defaultRemoteStyle_override: ''
—
Reply to this email directly, view it on GitHub
<#201 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB32XY333GL7GZQVSJAOAZLX7NII5ANCNFSM6AAAAAA5P2BB2U>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Correct, some keys work, like Home, but not mute or volume up/down. |
|
Ahh, volume can be tricky. Your physical remote works fine, right?
Try covering the entire front of the remote with your hand, turn away from
the TV, bury the remote with your hand on it under a pillow, anything to
stop any IR from escaping and reaching your TV. I'll bet the physical
remote won't work when well-covered, which is why the virtual remote can't
simulate it.
There may be no integration to the volume controls from the fire stick...
If you have a network connected TV in Home Assistant, you can remap virtual
remote buttons to call volume controls on the TV directly...
…On Sun, Oct 15, 2023, 01:35 GlenWi ***@***.***> wrote:
Correct, some keys work, like Home, but not mute or volume up/down.
—
Reply to this email directly, view it on GitHub
<#201 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB32XY3JW4PCECPC3SNTJETX7N72JANCNFSM6AAAAAA5P2BB2U>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
The physical remote works fine, and I don't believe it's using IR (must be bluetooth/RF). I can cover the front of the remote completely and it works fine, even from another room with the doors shut. |
|
All ~ Please accept my apologies for my absence. Thank you for discussing this between yourselves! We will get this sorted out together. 😄 The main thing we need to accomplish together (assuming I don't buy one for myself) is exactly what "event number" needs to be used as a default. Let me explain a little more about what I mean. @Jeppedy - Thank you for the device interrogation that you posted to this thread! What's interesting about your interrogation is that it seems to conflict with your comment where you posted some of your working YAML. Your interrogation showed that the correct "event number" to use as default should be event6, but when you use In case either of you are wondering, the way I attempt to determine the default Compatibility Mode is to first look at what the device spits out when I ask for an Interrogation. (Interrogation is my word, the more accurate term is to request a dump of the device input data) Specifically, I look for an entry that correlates with a remote control (bluetooth) or an IR (infrared) input. In the large dump of data above, you can find this section: This is why my suggestion above was to use event6 as your Compatibility Mode. If the Interrogation that @Jeppedy preformed for us was a typical response from this stick, it should have also worked for @GlenWi. After getting these dumps/Interrogation results, I update the documentation wiki. In this case, after receiving the results from @Jeppedy I added an entry to the Existing Amazon Devices Support Chart for the Fire TV Stick 4K Max 2nd Gen (2023). On that page, you will find a much easier to read chart that diagrams the "event number" and what kind of input the devices are using them for. When you compare that page with the page for the Fire TV Stick 4K Max 1st Gen (2021), you will note that the remote control input is expected to be event5 for that one. What should we do next? I have some testing that I'd like both of you to try:
|
|
I'll do a more thorough review and post results.
J
…On Tue, Oct 17, 2023, 11:07 Doug Nelson ***@***.***> wrote:
All ~
Please accept my apologies for my absence. Thank you for discussing this
between yourselves! We will get this sorted out together. 😄
The main thing we need to accomplish together (assuming I don't buy one
for myself) is exactly what "event number" needs to be used as a default.
Let me explain a little more about what I mean.
@Jeppedy <https://github.com/Jeppedy> - Thank you for the device
interrogation that you posted to this thread
<#201 (comment)>!
What's interesting about your interrogation is that it seems to conflict
with your comment
<#201 (comment)>where
you posted some of your working YAML. Your interrogation showed that the
correct "event number" to use as default should be *event6*, but when you
use device_type: fire_tv_stick_4k_max the default event number that is
used is actually *event5*. It's not impossible that both *event5* and
*event6* would work, but unusual in my experience. (keep in mind, I don't
own this specific stick, so things might be different)
In case either of you are wondering, the way I attempt to determine the
default Compatibility Mode is to first look at what the device spits out
when I ask for an Interrogation
<https://github.com/PRProd/HA-Firemote/wiki/How-Can-I-Help%3F#device-interrogation-for-new-device-support>.
(Interrogation is my word, the more accurate term is to request a dump of
the device input data) Specifically, I look for an entry that correlates
with a remote control (bluetooth) or an IR (infrared) input. In the large
dump of data above, you can find this section:
125: Amazon Fire TV Remote
Classes: 0x80000021
Path: /dev/input/event6
Enabled: true
This is why my suggestion above
<#201 (comment)>
was to use *event6* as your Compatibility Mode. If the Interrogation that
@Jeppedy <https://github.com/Jeppedy> preformed for us was a typical
response from this stick, it should have also worked for @GlenWi
<https://github.com/GlenWi>.
After getting these dumps/Interrogation results, I update the documentation
wiki <https://github.com/PRProd/HA-Firemote/wiki/>. In this case, after
receiving the results from @Jeppedy <https://github.com/Jeppedy> I added
an entry to the Existing Amazon Devices Support Chart
<https://github.com/PRProd/HA-Firemote/wiki/Existing-Amazon-Devices---Support-Chart>
for the Fire TV Stick 4K Max 2nd Gen (2023)
<https://github.com/PRProd/HA-Firemote/wiki/Fire-TV-Stick-4K-Max-2nd-Gen-(2023)>.
On that page, you will find a much easier to read chart
<https://github.com/PRProd/HA-Firemote/wiki/Fire-TV-Stick-4K-Max-2nd-Gen-(2023)#device-interrogation>
that diagrams the "event number" and what kind of input the devices are
using them for. When you compare that page with the page for the Fire TV
Stick 4K Max 1st Gen (2021)
<https://github.com/PRProd/HA-Firemote/wiki/Fire-TV-Stick-4K-Max---1st-Gen-(2021)>,
you will note that the remote control input is expected to be *event5*
for that one.
What should we do next? I have some testing that I'd like both of you to
try:
- @GlenWi <https://github.com/GlenWi>
- Please take note of the first bullet point in the Why don't any
of the buttons on the Firemote work at all?
<https://github.com/PRProd/HA-Firemote#why-dont-any-of-the-buttons-on-the-firemote-work-at-all>
section of the README.md file. There is a known annoyance with all Amazon
Fire devices that requires a physical button press on the physical remote
control to establish the "event" connection. It's possible that
*event5* or *event6* (whichever one it might be) doesn't even exist
on your device UNTIL you press a button on your remote first.
- @Jeppedy <https://github.com/Jeppedy> and @GlenWi
<https://github.com/GlenWi>
- I would be interested to know if another device interrogation
<https://github.com/PRProd/HA-Firemote/wiki/How-Can-I-Help%3F#device-interrogation-for-new-device-support>
would yield a different result than what was posted by @Jeppedy
<https://github.com/Jeppedy>. @GlenWi <https://github.com/GlenWi>,
this could be a good way to see if you actually have a physical remote
control attached to your device. If you don't see one in the list, that
would be the answer to your issues.
- If both of you DO see an Amazon Fire TV Remote in the output of
your interrogation, (or even if you choose not to do that step), I'd also
be interested to know what happens when you do the last bullet point in the Why
don't any of the buttons on the Firemote work at all?
<https://github.com/PRProd/HA-Firemote#why-dont-any-of-the-buttons-on-the-firemote-work-at-all>
section of the README.md file. At least one of those will work (assuming
your physical remote is actually connected) but now I'm wondering if maybe
more than one might work?
—
Reply to this email directly, view it on GitHub
<#201 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB32XY3XLSC2JZRGXGPTLTTX72UNHAVCNFSM6AAAAAA5P2BB2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRWG4ZTAMRUGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I'll work through this in the evening, 0750 here.Regards,Glen WilsonThis message has been scanned before sending to be error and virus-free. Unfortunately, email could be infected, intercepted, or corrupted in transit so the recipient should check the email with proper software. The sender does not accept liability for any damage caused by the contents of this email.
-------- Original message --------From: Doug Nelson ***@***.***> Date: 18/10/23 05:07 (GMT+12:00) To: PRProd/HA-Firemote ***@***.***> Cc: GlenWi ***@***.***>, Mention ***@***.***> Subject: Re: [PRProd/HA-Firemote] [New Device Support]: Please add support for the Firestick 4K Max 2nd Gen (Issue #201)
All ~
Please accept my apologies for my absence. Thank you for discussing this between yourselves! We will get this sorted out together. 😄
The main thing we need to accomplish together (assuming I don't buy one for myself) is exactly what "event number" needs to be used as a default. Let me explain a little more about what I mean.
@Jeppedy - Thank you for the device interrogation that you posted to this thread! What's interesting about your interrogation is that it seems to conflict with your comment where you posted some of your working YAML. Your interrogation showed that the correct "event number" to use as default should be event6, but when you use device_type: fire_tv_stick_4k_max the default event number that is used is actually event5. It's not impossible that both event5 and event6 would work, but unusual in my experience. (keep in mind, I don't own this specific stick, so things might be different)
In case either of you are wondering, the way I attempt to determine the default Compatibility Mode is to first look at what the device spits out when I ask for an Interrogation. (Interrogation is my word, the more accurate term is to request a dump of the device input data) Specifically, I look for an entry that correlates with a remote control (bluetooth) or an IR (infrared) input. In the large dump of data above, you can find this section:
125: Amazon Fire TV Remote
Classes: 0x80000021
Path: /dev/input/event6
Enabled: true
This is why my suggestion above was to use event6 as your Compatibility Mode. If the Interrogation that @Jeppedy preformed for us was a typical response from this stick, it should have also worked for @GlenWi.
After getting these dumps/Interrogation results, I update the documentation wiki. In this case, after receiving the results from @Jeppedy I added an entry to the Existing Amazon Devices Support Chart for the Fire TV Stick 4K Max 2nd Gen (2023). On that page, you will find a much easier to read chart that diagrams the "event number" and what kind of input the devices are using them for. When you compare that page with the page for the Fire TV Stick 4K Max 1st Gen (2021), you will note that the remote control input is expected to be event5 for that one.
What should we do next? I have some testing that I'd like both of you to try:
@GlenWi
Please take note of the first bullet point in the Why don't any of the buttons on the Firemote work at all? section of the README.md file. There is a known annoyance with all Amazon Fire devices that requires a physical button press on the physical remote control to establish the "event" connection. It's possible that event5 or event6 (whichever one it might be) doesn't even exist on your device UNTIL you press a button on your remote first.
@Jeppedy and @GlenWi
I would be interested to know if another device interrogation would yield a different result than what was posted by @Jeppedy. @GlenWi, this could be a good way to see if you actually have a physical remote control attached to your device. If you don't see one in the list, that would be the answer to your issues.
If both of you DO see an Amazon Fire TV Remote in the output of your interrogation, (or even if you choose not to do that step), I'd also be interested to know what happens when you do the last bullet point in the Why don't any of the buttons on the Firemote work at all? section of the README.md file. At least one of those will work (assuming your physical remote is actually connected) but now I'm wondering if maybe more than one might work?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Okay, here's the latest. It's definitely positively a Fire TV Stick 4k Max My YAML Card is: Every control about this FireTV works just fine (accepting for the Volume complexity, as my TV looks for IR from the remote, not RF, so I have to control the audio separately. Is it possible the "default" compatibility mode is set right for this Fire Stick model?
|
|
Hi mine is also event5. I did try them all but none worked. I did not restart the integration - just changed the event id 13 times and saved each time. 3: Amazon Fire TV Remote The physical remote works fine using RF |
|
OK - got it working by chosing Fire TV Cube 3rd Gen 2022 and strong slower compatibility mode! |
|
@Jeppedy & @GlenWi ~ @GlenWi ~ I suspect that the reason some of your Firemote buttons do not work as expected is that you need to enable CEC mode. I suggest looking at this article I wrote to learn more about it, and how to set it up: Using CEC Controls Ideally, it's better to avoid using the strong (slower) compatibility mode unless you absolutely have to. |
|
I have CEC on which is working OK. Looka like I absolutely need the stron (slower) mode. |
|
Thanks for your support by the way! |
|
Official release version v3.0.1 has just been published. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Device Name
Firestick 4K Max 2nd Gen
Which compatability mode event number works BEST with your device?
None
Additional Comments (optional)
No response
Interrogation ADB Response (optional but EXTREMELY helpful)
No response
The text was updated successfully, but these errors were encountered: