Missing connection state awareness results in endless connection attempt loops (Android TV powered off) and log flooding

[bcutter]

I discovered the same as this user here, unfortunately it seems he didn't raise an issue in this repo as recommended at the end of the issue:

Android TV integration very chatty in log when configured Android TV device is not available (turned off)
home-assistant/core#69672
(here the problem is already described)

Problem: python-androidtv constantly (every 80 seconds) trys to connect to the tv. If it is powered off, it will go on like forever. On every failed connect attempt an error is written to the log. This floods logs pretty fast pretty heavily.

This is what Home Assistant log contains for ONE single failed connection attempt:

Logger: androidtv.adb_manager.adb_manager_async
Source: /usr/local/lib/python3.9/site-packages/androidtv/adb_manager/adb_manager_async.py:298
First occurred: 30. Mai 2022, 16:21:17 (1445 occurrences)
Last logged: 00:50:11

Couldn't connect to xxx.xxx.xxx.xxx:5555. TcpTimeoutException: Connecting to xxx.xxx.xxx.xxx:5555 timed out (1.0 seconds)

This is what HA's GUI presents:

The experts from HA (see referenced issue) told this is nothing HA can fix but this only can to be done in this library repo.

By the way: Not related to #15

[JeffLIrion]

python-androidtv/androidtv/setup_async.py

Line 23 in f63687a

log_errors=True,

As long as HA continues to call setup with log_errors=True, this package will continue to log failed setup attempts. This should be fixed in HA.

[bcutter]

Ah come on guys... you ping pong users from one side to the other :-D Why don't you talk with each other to find a solution ;-)

So here we go: home-assistant/core#72851

[JeffLIrion]

Until someone submits a fix, I suggest setting the log level to critical for the Android TV integration.

[bcutter]

That's a workaround. So let's look/wait for a fix.

[kevincaradant]

Hi any news about this? :)

I have hundred and hundred message like that, just after 1 or 2 days :(.
The other thread is locked, I can't open it again

Thanks