search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.16k stars 29.84k forks source link

Tautulli component: lot of failures connection ! #19421

Closed vincegre closed 5 years ago

vincegre commented 5 years ago

Home Assistant release with the issue: since 0.83.3 (currently running 0.84.3) Last working Home Assistant release (if known): N/A as it was first release where component was usable ! Operating environment (Hass.io/Docker/Windows/etc.): Hass.io (supervisor 141 HaasOS 1.13) Component/platform: https://www.home-assistant.io/components/sensor.tautulli/ Description of problem: generates a lot of noise in logs with problem of connection all the time (unless my Tautulli server is running fine all the time and same for HA and everything is on same LAN). The component still works in front-office but with all these errors of connection all the time in logs

Can not load data from Tautulli: http://192.168.1.70:8181/api/v2?apikey=XXXXXXXX&cmd=get_activity -

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

sensor:
  - platform: tautulli
    api_key: myapikeyishere
    host: 192.168.1.70
    monitored_conditions:
      - ip_address # local IP for client
      - ip_address_public # Public IP for client
      - player # Player name
ludeeus commented 5 years ago

I have had this running since the introduction and other than during restarts I have not seen this error, how often does it occur?

vincegre commented 5 years ago

Sorry for late answer but I had to reinstall my config for some other reasons ;) The problem still appears but it's completely randomly (well have not found yet the link with something else !). It can sometimes make the error few times in a raw in logs and some days without anything ! I'll keep an eye on it and try to find if it's linked with something else...

ludeeus commented 5 years ago

I have discovered that when there are no messages after the - in the log message, it is a timeout issue. Home Assistant uses longer than 5 sec to fetch update from the endpoint.

somar05 commented 5 years ago

@ludeeus , just to clarify. What's the cause for the timeout?. My case is the same about radomly error over the log, but working correctly all the time. Just "error noise".

ludeeus commented 5 years ago

Can be any number of things @somar05. Currently, the timeout is 5sec, I'm testing out with 8 now, that should allow more slack from this.

vincegre commented 5 years ago

It looks definitively like a too short timeout on API request ! Is there a way to correct that easily ? It fills my HA logs just with these time-out errors all the time !!

ludeeus commented 5 years ago

Is there a way to correct that easily ?

yes, run HA and tautulli on better HW and/or use IP and not DNS names if you are not.

It fills my HA logs just with these time-out errors all the time !!

You can "disable" that by setting the logger level to critical for pytautulli https://www.home-assistant.io/components/logger/

Protip @vincegre: Your usage of ! in your messages can be interpited as you "screaming" to us, the people investing our limited spare time to add features/fix bugs ;)

vincegre commented 5 years ago

yes, run HA and tautulli on better HW and/or use IP and not DNS names if you are not.

Tautulli is running already on a very powerful server where Plex server is running too and HA is on a dedicated Pi 3B+ and I use only IP for config and setup never DNS or mdns names..

You can "disable" that by setting the logger level to critical for pytautulli https://www.home-assistant.io/components/logger/

Thanks for the info, will do that to keep it more quiet !

Protip @vincegre: Your usage of ! in your messages can be interpited as you "screaming" to us, the people investing our limited spare time to add features/fix bugs ;)

Sorry it was not my goal, and didn't expect two ! to be understood like that :(

stale[bot] commented 5 years ago

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.