-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
Error while setting up platform androidtv #22324
Comments
Can you check if the TV is connected to |
Using the adb add on its states connected [16:02:02] INFO: Connecting to device: 192.168.1.184... |
I did fix a couple issues with the |
Will your new version work as a custom component as I'm on hass.io Rebooting hasn't fixed the issue TV on or off |
Yes, it will work as a custom component as long as it successfully installs the But I have no idea why that ADB command fails. |
Cheers |
Try disconnecting and reconnecting from the ADB server, or just restart the ADB server. |
Okay I turned the USB adb on my TV and turned it back on again, then restarted HA and it reconnected. |
I've connected to my Kindle via ADB in the past and 1) I have to first connect over a USB cable before connecting over Wi-Fi and 2) when I turn off the device, I have to reconnect via USB again. This sounds like it might be similar. I don't know if there's a way to keep the connection to your TV alive, but it looks like the issue is with the ADB connection and not the Android TV component / Home Assistant. |
Does it make any difference my TV is connected via ethernet |
I don't see why it would. Also, you should fix your TV's IP address, if you haven't already. |
My guess is that your TV does some sort of reboot each night at, say, 3 am. If you never check some sort of box telling it to always allow connections from this device, then the ADB server won't be able to reconnect. |
@JeffLIrion, I'm getting an error as well trying to connect to an Nvidia Shield. I've authorized the hass box on the Shield, and 'adb connect' works just fine. I'm able to execute shell commands and the like. I've copied the 'adbkeys' into my homeassistant directory (I'm using Raspbian with venv setup, not Hassio).
My config, which is more or less the same as I was using on my Fire TV.
Oh, and I have both an adbkey and adbkey.pub file. |
@mmotley999 you need to use the ADB server option. |
The discussion in this issue about preventing the device from going completely offline may be relevant. |
@JeffLIrion Ok, I fired up ADB server('adb start-server') and changed the config:
However, now getting this:
I verified that issuing a "adb connect " works just fine from the command line/shell, even as the 'homeassistant' user, right after seeing the message. I'm able to execute shell commands against the Shield, so it doesn't appear the Shield is offline or not responding to network traffic.... |
@mmotley999 and @aav7fl, your issue is different. Please re-post here: #22485. |
Right... in my case, I'm not running Home Assistant or adb in a Docker container. Home Assistant is running on a RPi3+ in a Python venv, and I've fired up adb via "adb start-server" from the command line prior to restarting Home Assistant. Looking at 22485, it doesn't appear to apply to my situation. |
Restart the Android device... That takes care of the error for me. |
Error while trying to connect to my IPTV box:
|
@stast1 your issue is different. Please create a new issue and I'll submit a fix. IMO, this issue should be closed. The original poster was able to setup both of his devices, but the problem was that one of those devices would eventually disconnect and become unavailable. This is more of an issue with that device itself, and the problem is not with the Home Assistant component. |
@JeffLIrion Thanks! |
@JeffLIrion > let me know if this fixes it. |
@JeffLIrion Could you explain why you answered this #22324 (comment) here? |
@pattyland https://www.home-assistant.io/components/androidtv/#adb-troubleshooting
|
@JeffLIrion Thanks for the explanation! This article also says "If you receive the error message |
@pattyland please read the full page. https://www.home-assistant.io/components/androidtv#adb-setup
|
@JeffLIrion Ok ok, you convinced me ;) With |
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! |
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. |
Having issues since updating to 0.98.1. Rebooted host, rebooted ShieldTV. Restarted ADB server add on. Still doesn't connect. Worked fine up until 0.98.x Verified ADB is still turned on in ShieldTV settings. Any other thoughts on this? Anything I could look into that I may have missed above?
|
@rpitera it looks like the required version of the
|
@JeffLIrion - Running hass.io in Virtualbox. I have dev access set up though so I'll try this and get back to you. EDIT: Didn't even need dev access, just went to my deps folder and removed the old folders and rebooted - everything loaded fine - thanks very much for the pointer! |
Closing this issue as it seems all have been resolved. If you experience this issue, please open a new one. |
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io 90.0
Component/platform:
https://www.home-assistant.io/components/androidtv/
Description of problem:
i connected my sony bravia android tv to HA everything works fines, yet after a reboot it doesn't show up and i have the below error in the logs
my nvidia doesn't have this issue stay connected without any errors
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: