[Deprecated] Native support for Fire TV

https://gist.github.com/mcfrojd/9e6875e1db5c089b1e3ddeb7dba0f304#start-apps-on-your-shield

Try this:

{"entity_id" :"media_player.shield", "command": "am start -a android.intent.action.VIEW -d -n com.netflix.ninja/.MainActivity"}
1 Like

It works like a charm. Thank you so much

Hi, i got hassio to connect to firetv using ADB add on. On/off and pause/play work, but the volume controls are not working. I tried calling androidtv.adb_command with command VOLUME_UP, and also media_player.volume_up service, both do not work. I have info logging enabled for hassio, i do not see any errors or anything in log. please help. thank you.

Fire TV devices don’t support volume control. At least, my 2nd generation Fire TV sticks do not, not have I heard of anyone with a newer device reporting that it supports volume control.

Hello, I have been trying to get my firestick set up using
Hassio
ADB - Android Debug Bridge

media_player:

  • platform: androidtv
    name: Firestick
    device_class: firetv
    host: 192.168.0.7
    adb_server_ip: 127.0.0.1

I can’t see my media_player.firestick entity

Please tell me whats wrong thank you
adb logs say i am connected to the IP adress

I’m not sure of the details of previous issue but I just tried it with media_player volume_up service which worked and I have it set with a key_event in a script also and both change the volume on my Toshiba with FireTV built in… if I can provide anymore info let me know.

Edit: it seems I have two entities though and the Volume_up service is working with one that I think possibly got generated from my Alexa App having the fire tv linked. (Would have been pulled from the alexa as media player custom component most likely)

@acraig91 Same issue here, asked on discord, they said I wasn’t the first person with the problem, so I’m just waiting for something to be mentioned in the changelog.

@Ericthegreat @acraig91 Same issue here, too. Please let me know as soon as you have any solution.

@Ericthegreat, @acraig91, @Cello92 what does the Home Assistant log say?

I followed this guideline: https://www.home-assistant.io/components/androidtv/
Android Debug Bridge Add On is installed and connected to my Fire TV:

[14:27:28] INFO: Connecting to device: 192.168.2.129...
already connected to 192.168.2.129:5555

The Home Assistant log says this:

2019-05-22 13:26:52 WARNING (SyncWorker_11) [root] Couldn’t connect to host: 192.168.2.129:5555, error: Connection reset by peer
2019-05-22 13:26:52 WARNING (SyncWorker_11) [homeassistant.components.androidtv.media_player] Could not connect to Fire TV at 192.168.2.129:5555
2019-05-22 13:26:52 WARNING (MainThread) [homeassistant.components.media_player] Platform androidtv not ready yet. Retrying in 30 seconds.

Any ideas why the connection is being rejected?

I think you need to add adb_server_ip: 127.0.0.1 to your config.

I don’t have the add-on, as my setup was manual, so things may be a bit different.
Not entirely sure but it looks like the adb daemon successfully logged into your fireTV the first time
(the INFO log says its “already connected”).

Once connected, in my case, I got a pop-up on the FireTV saying something about USB debugging and wanted to confirm that some computer (i.e. HA) was allowed to connect to it (then click “OK”).

You may also need to set the developer options on FireTV per the instructions “Connecting to Fire TV Through adb” that are mentioned here:

It could be, that its rejecting your HA connection due to failure to authenticate. In my setup, keys are generated by the adb daemon and are used by HA to communicate with FireTV. If you didn’t perform any setup on your FireTV, its possible the adb daemon did not generate any keys…
OR
I think also, that FireTV only allows one connection at a time. It may be that you need to reboot your FireTV to remove a stale connection, and try again.

1 Like

Thanks, I will give it a try when I’m home later.

Sorry for the late reply.
There was actually a pop-up on the FireTV which I had to confirm, and after this it worked like a charm.
Thank you very much.

(I posted this in the ADB add-on thread but haven’t gotten any feedback yet, so I’m re-posting it here.)

A recent pull request for the python-adb package might fix the issues that the Python ADB implementation had with newer devices. If you’d like to test it, please use this as a custom component and report back!

https://github.com/JeffLIrion/home-assistant/tree/patch-19/homeassistant/components/androidtv

You’ll need to follow the instructions for generating an adbkey file:

https://www.home-assistant.io/components/androidtv#2-python-adb-implementation

You’ll also need to stop the ADB server and restart your Android TV / Fire TV device.

1 Like

For some reason I can start the ADB BRIDGE addon and it connects to my fire tv but I’m not finding the entity to add to Lovelace after configuring in config.yaml. any ideas. Not getting any errors in the logs for the -platform: androidtv

any help would be greatly appreciated

Set the log level to debug for the Android TV component and post the log.

logger:
  default: critical # or whatever your default is
  logs:
    homeassistant.components.androidtv: debug

I’ve setup HA manually, so no hass.io. I’ve setup an ADB server on the same machine my HA is running, using this script. But when I restart my machine:

  1. How do I run this script on boot?
  2. How would I start HA after my ADB server is up and running?

Upgrade to HA 0.101 and use the Python ADB approach. The documentation has been updated, so give that a read (especially the ADB Troubleshooting section in the event that you run into issues). If the Python ADB approach works, then forget about the ADB server.

1 Like

Ah that is good to hear! Thanks, will do! :slight_smile: