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

Android Debug Bridge does not return app_id for Fire TV 4K Max Stick (2nd gen) #102565

Closed
markwiese opened this issue Oct 23, 2023 · 6 comments · Fixed by JeffLIrion/python-androidtv#348

Comments

@markwiese
Copy link

The problem

When sending the ADB command GET_PROPERTIES to the Fire TV Max stick (2nd gen), the response does not contain the app_id:

adb_response: >-
  {'screen_on': True, 'awake': True, 'wake_lock_size': 2, 'current_app': None,
  'media_session_state': None, 'running_apps': None, 'hdmi_input': None}
hdmi_input: null
device_class: tv
friendly_name: Fire TV
supported_features: 22961
entity_picture: >-
  /api/media_player_proxy/media_player.fire_tv?token=

This means it isn't possible to detect the source, or to use custom state detection which relies on the app_id.

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Android Debug Bridge

Link to integration documentation on our website

https://www.home-assistant.io/integrations/androidtv/

Diagnostics information

config_entry-androidtv-bc94467ea900cb0c4b6aafe1c8c26f75.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

This is only occurring with the second generation Fire TV 4K Max stick. I recently switched from the first generation where app_id was working fine (state detection was a hot mess, though).

@home-assistant
Copy link

Hey there @JeffLIrion, @ollo69, mind taking a look at this issue as it has been labeled with an integration (androidtv) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of androidtv can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign androidtv Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


androidtv documentation
androidtv source
(message by IssueLinks)

@KaBoomtown
Copy link

Same. I am unable to select a source using app_id with new 4k (AFTKM) FireStick. It used to work on my older FireStick.

@Killface1980
Copy link

Same here. Working fine on the 4k, but not on the 4k Max 2nd gen.

@Killface1980
Copy link

Killface1980 commented Nov 7, 2023

Found a workaround, look here JeffLIrion/python-androidtv#292 (comment)

Re-adding the device as Android did the trick. In the configuration, there's still no app list populated, but it's working from everywhere else.

@markwiese markwiese changed the title Andoird Debug Bridge does not return app_id for Fire TV 4K Max Stick (2nd gen) Android Debug Bridge does not return app_id for Fire TV 4K Max Stick (2nd gen) Nov 7, 2023
@markwiese
Copy link
Author

Found a workaround, look here JeffLIrion/python-androidtv#292 (comment)

Re-adding the device as Android did the trick. In the configuration, there's still no app list populated, but it's working from everywhere else.

I've just tested this workaround and confirmed it works for me! Thanks, @Killface1980 👍

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants