Shield TV Filling Logbook With "Unavailable" and "Off" Entries

JDIacobbo · June 19, 2023, 12:54pm

I was troubleshooting an unrelated issue and noticed that in my logbook one of my two Nvidia Shield TV’s is constantly becoming unavailable then registering as off. Strangely the other Shield doesn’t present this behavior. Any ideas why this is happening and how to fix it. It happens so often that it makes the logbook hard to use.

rongten · July 7, 2023, 6:50pm

Same here. Shield TV cigar edition. Both (shield and ha) on Ethernet.

JDIacobbo · July 8, 2023, 12:50pm

This appears to have resolved itself on its own.

1aranzant · July 27, 2023, 9:27am

Same issue here ! It keeps on being unavailable, so I cannot control it with the nvidia shield ios remote app, I have to physically turn it on for it to appear again.
It only happens on one my shields (the old one, first model).
It’s like it goes on sleep mode and thus disconnects from the network…

EDIT:
my temp fix: set the shield as always on in dev settings. but you’ll have to disable CEC otherwise it’ll turn on your receiver/tv when it periodically wakes up from sleep.

jellytotz · January 3, 2024, 7:51pm

Same issue here (Nvidia Shield Pro). My Chromecast and FireTV devices don’t cause this issue, only the Nvidia Shield keeps becoming “Unavailable” even if the device is on.

glenviewjeff · February 29, 2024, 2:55am

Same here, only happening on one of my two shields right now.

getz1234 · March 7, 2024, 1:09pm

same here - and identical behavior on 2 identical Shields ( Nvidia Shield TV Pro 4k).

Its about every 5 seconds flooding my log file in HA.

Anyone a quick fix ?

mightymouse · April 21, 2024, 9:47pm

github.com/home-assistant/core

Android TV integration - TV unavailable when turned of.

opened 01:11PM - 09 Jan 24 UTC

n3on4s

integration: androidtv_remote

### The problem So I encoutered problem with my Android TV (TCL), where whenver… I shutdown TV, it becomes unavailable in HA: ![image](https://github.com/home-assistant/core/assets/19694051/38f75883-b712-440e-aa9b-e5b8eb464c5e) I did some debuging, and narrowed down problem to android TV itself. When TV is on, NMAP results: ``` nmap 192.168.0.82 Starting Nmap 7.80 ( https://nmap.org ) at 2024-01-09 14:42 FLE Standard Time Nmap scan report for 192.168.0.82 Host is up (0.0017s latency). Not shown: 995 closed ports PORT STATE SERVICE 5555/tcp open freeciv 8008/tcp open http 8009/tcp open ajp13 8443/tcp open https-alt 9000/tcp open cslistener MAC Address: XX:XX:XX:XX:XX:XX ``` After TV gets shutdown, by any way remote/HA/auto sleep: ``` nmap 192.168.0.82 Starting Nmap 7.80 ( https://nmap.org ) at 2024-01-09 14:47 FLE Standard Time Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 1.02 seconds ``` I tried to change every tipe of settings in Android TV and nothing helped. After some time I tried to wake up TV with WakeOnLan option and at first seems like TV had'nt woke up, however, nmap started responding with OK results, and TV become available (visible as turned off again) in HA again: ![image](https://github.com/home-assistant/core/assets/19694051/b0b4efe9-c768-49e7-a7e4-4b7bb623584a) ``` nmap 192.168.0.82 Starting Nmap 7.80 ( https://nmap.org ) at 2024-01-09 14:53 FLE Standard Time Nmap scan report for 192.168.0.82 Host is up (0.00017s latency). Not shown: 995 closed ports PORT STATE SERVICE 5555/tcp open freeciv 8008/tcp open http 8009/tcp open ajp13 8443/tcp open https-alt 9000/tcp open cslistener MAC Address: ``` I know this happend not to all android TVs, however maybe you could add configuration option to enable, automaticaly resending WakeUpOnLan command, before the Heartbeat request, if tv is in Off/unavailable state? ### What version of Home Assistant Core has the issue? core-2024.1.0 ### 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 TV Remote ### Link to integration documentation on our website https://www.home-assistant.io/integrations/androidtv_remote/ ### Diagnostics information [config_entry-androidtv_remote-369036337b86e55921657a6ff3d5d5b9.json.txt](https://github.com/home-assistant/core/files/13874071/config_entry-androidtv_remote-369036337b86e55921657a6ff3d5d5b9.json.txt) ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt [Living Room TV(192.168.0.82):8009] Heartbeat timeout, resetting connection 2:43:35 PM – (WARNING) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py - message first occurred at 1:28:34 PM and shows up 25 times Disconnected from Living Room TV at 192.168.0.82 2:38:41 PM – (WARNING) Android TV Remote - message first occurred at 1:28:30 PM and shows up 47 times [Living Room TV(192.168.0.82):8009] Failed to connect to service ServiceInfo(type='mdns', data='Smart-TV-Pro-6e0231880edf1cc85f26ad05671960b1._googlecast._tcp.local.'), retrying in 5.0s 2:20:49 PM – (ERROR) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py - message first occurred at 1:29:04 PM and shows up 14 times ``` ### Additional information For anyone looking for fast fix, setting automation every 10s. to send magic wakeup packet, to TV's MAC when TV is off/unavailable fixed the issue for me.

This seems to have fixed it for me.