core: Unable to get adb server connected to docker HA
Home Assistant release with the issue: 0.90.2
Last working Home Assistant release (if known): Unknown
Operating environment (Hass.io/Docker/Windows/etc.): Home Assistant docker (unraid) ADB server on ubuntu vm (unraid)
Component/platform: media_player.androidtv
adb connectivity
Description of problem: So my setup is above but after setting up the component, connecting the fire sticks to the server and restart hass it says that its failed to connect. I have tested it locally with HA running on that same vm as adb and it works using localhost, but no luck between servers. Below is my setup. The adb path is white listed.
config:
- platform: androidtv
name: sandra firetv
host: 192.168.0.254
adb_server_ip: 192.168.0.90
adbkey: "/config/firetv/adbkey"
- platform: androidtv
name: mike firetv
adb_server_ip: 192.168.0.90
host: 192.168.0.206
adbkey: "/config/firetv/adbkey"
(ubuntu vm adb server)
mike@ubuntuvm:~$ adb devices
List of devices attached
192.168.0.254:5555 device
192.168.0.206:5555 device
Wed Mar 27 2019 17:58:55 GMT-0400 (Eastern Daylight Time)
Could not connect to mike firetv at 192.168.0.206:5555 using ADB server at 192.168.0.90:5037
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 46 (23 by maintainers)
I reworked the script to:
But why is a separate ADB server needed?
@aav7fl @JeffLIrion forgive me but where does the script get placed?
I believe I read a while back that the pure-python-adb package only worked when the ADB server is on the same machine. It sounds like yours is on a different computer. I assume your reason for this is because you’re not using Hass.io and so you can’t use the addon. However, you can still run an ADB server. As an example of how to do this, see this post: https://community.home-assistant.io/t/native-support-for-fire-tv/64448/300
Also, you don’t need
adbkeyin your config when using an ADB server. It doesn’t hurt anything, it’s just unnecessary.