On an Raspberry Pi in a virtual_env I had the same problem. Solution: the path to the adbkey file has to be absolute:
“/home/homeassistant/.homeassistant/config/android/adbkey”
1 Like
Thank you Moooof, I spent forever trying to figure out what I was doing wrong. Added that as an example on the component documents, hopefully they’ll accept that so others don’t spend hours tweaking file locations and permissions >.<
I want to integrate my fire tv stick 4k, where can I get the two files? Thanks.
look on this forum for the custom version of the androidtv component. The developer has simplified the integration to automatically create the adbkey files you’re referring to–you only need to accept the ADB connection when the prompt appears on the Fire TV UI.
the custom version may be included in the latest HA release, but I haven’t checked.
1 Like
this works, thanks!
Can you post a link?
[Edit]
Found it !!! Well maybe. 
https://github.com/hassio-addons/addon-adb/blob/a9900d1f42123a60fc7322f7c4ccc177faadfefc/README.md
The built-in androidtv component (at least as of Hass 0.102.3) also supports auto ADB-key generation. I run Hass on a nuc in a docker and I was having a weird issue with needing to re-generate the keys every few days unless I explicitly defined the adbkey parameter for the androidtv integration to point to the path of the androidtv_adbkey file in configuration.yaml. It seems to be working now due to some sequence of restarting the fire tv stick and the nuc and editing configuration.yaml.
But if you are still experiencing key issues using the “Python ADB implementation” (i.e., letting the integration auto-generate the ADB key), you may need to explicitly define adbkey to point to where it is auto-generated, like so:
media_player:
- platform: androidtv
name: Android TV
device_class: firetv
host: HOST_IP
adbkey: "/config/.storage/androidtv_adbkey"
I’d be interested in hearing if others had this same issue.