androidtv component spams log when player in stand-by mode

[bieniu]

Home Assistant release with the issue:
0.92.2

Last working Home Assistant release (if known):
None

Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian, python 3.7.2, virtualenv

Component/platform:
media_player/androidtv

Description of problem:
When my Android TV player (Xiaomi Mi Box TV 4K) is in stand-by mode there are a lot warnings in log.

2019-05-11 18:15:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.mibox is taking over 10 seconds
2019-05-11 18:15:53 WARNING (MainThread) [homeassistant.components.media_player] Updating androidtv media_player took longer than the scheduled update interval 0:00:10
2019-05-11 18:16:04 WARNING (MainThread) [homeassistant.components.media_player] Updating androidtv media_player took longer than the scheduled update interval 0:00:10
2019-05-11 18:16:15 WARNING (MainThread) [homeassistant.components.media_player] Updating androidtv media_player took longer than the scheduled update interval 0:00:10
2019-05-11 18:16:26 WARNING (MainThread) [homeassistant.components.media_player] Updating androidtv media_player took longer than the scheduled update interval 0:00:10
2019-05-11 18:16:37 WARNING (MainThread) [homeassistant.components.media_player] Updating androidtv media_player took longer than the scheduled update interval 0:00:10
2019-05-11 18:16:48 WARNING (MainThread) [homeassistant.components.media_player] Updating androidtv media_player took longer than the scheduled update interval 0:00:10
2019-05-11 18:16:59 WARNING (MainThread) [homeassistant.components.media_player] Updating androidtv media_player took longer than the scheduled update interval 0:00:10

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

- platform: androidtv
  host: !secret mibox_hostname
  adb_server_ip: 127.0.0.1
  name: MiBox

[stale]

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.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.