Core: Massive error log from Telldus component

[jonare77]

Home Assistant release with the issue:

0.88.2

Last working Home Assistant release (if known):
0.88.0

Operating environment (Hass.io/Docker/Windows/etc.):

Hassio on Docker. Host Ubuntu 18.04.2
Component/platform:

https://www.home-assistant.io/components/tellduslive/

Description of problem:
Telldus integration is working,, but log is spammed with Failed Request errors (see Traceback).

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

Traceback (if applicable):

Failed request: HTTPSConnectionPool(host='api.telldus.com', port=443): Max retries exceeded with url: /json/devices/list?supportedMethods=915&includeIgnored=0 (Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at 0x7f443286e2b0>, 'Connection to api.telldus.com timed out. (connect timeout=10)'))

Additional information:

[jamesw4]

I am seeing this same issue but still on 0.87. While it's working it sometimes seems laggy. I tried increasing scan interval but log is still getting spammed with these errors.

[filipdarj]

Also seeing this with same setup

[blindahl]

Same issue here. I'm on 0.88.2 but had the issue on 0.88.1 as well. Removed integration with tellduslive in admin gui and readded it numerous times but the error message continue to show up and with that switches and sensors start to appear unavailable in HA GUI.

I'm running Hassbian on a Raspberry Pi 3B+.

[jonare77]

Im also having problems with api calls failing. Will find the error messages for this. It may be telldus servers thats the problem and not HA.

[jamesw4]

I've had similar in the past and it was down to one of there severs in particular. Out of interest if you enable debugging then have a look near this error for the text HASRV this will tell you which server the request went to. Currently mine are going to sasha and it's temprementle .

[jamesw4]

Got this back from telldus support

Hi James!
We are currently having very high load on api.telldus.com. We are in the process of adding another load balancer and redirect some traffic there. Meanwhile, could you test pa-api.telldus.com (public access api) instead and see if you get better results there? Please let us know if that works better.

[jonare77]

Good work James, that confirms it. I guess this issue should be closed, but I let it stand open for others to see.

[blindahl]

But is it really solved? It seems like a thing to try alternative server) but until the load balancer proven to make the error go away, should the ticket be considered solved? Or if it's proven to be problem with Telldus and not home assistant.

[xydix]

I have an HA instance version 0.64 and it uses the older version of telldus live component. I have the same problem so this is probably a telldus server issue

[blindahl]

I guess it's a good thing for as many as possible to report the issue to Telldus so they escalates it on their end.

For the time being, is it complicated changing API endpoint being used for my system to pa-api.telldus.com?

[filipdarj]

Hm. Updated to 89.0 now and all of a sudden the telldus live integration works better than ever before.

[xydix]

This (https://github.com/home-assistant/home-assistant/pull/21705) is an big improvement if you ask me. But the error in the log is probably related to the telldus live server.

[filipdarj]

aha. Yes, that seemed to make a big difference and well I was too fast. Now the errors are back.

[AcidSleeper]

Failed request: HTTPSConnectionPool(host='api.telldus.com', port=443): Max retries exceeded with url: /json/sensors/list?includeValues=1&includeScale=1&includeIgnored=0 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] Try again'))

Im getting errors like this all the time. Latest hour more than 20 in log.

[filipdarj]

Also still having them

[thepapamaan]

Maybe if Telldus introduce push so we don't have to poll it so often.

[GFBsoul]

Kind of related to this, I have a problem with adding telldus to my HA, but I'm getting a SSL error.

[2019-10-09 17:15:57 ERROR (SyncWorker_19) [tellduslive] Failed to retrieve authorization URL: HTTPSConnectionPool(host='api.telldus.com', port=443): Max retries exceeded with url: /oauth/requestToken (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'ssl_choose_client_version', 'unsupported protocol')])")))

From api.telldus.com, it might seem like a good idea to switch to pa-api.telldus.com

Update 2018-02-28:
As some of you have noticed, there is a difference between servers regarding what SSL versions they accept. We are only using api.telldus.com for TelldusCenter and that URL is now considered legacy. If you are connecting to our API using SSL, you should use pa-api.telldus.com instead.

[jamesw4]

Who knows what’s going on with their api. I’m suffering sporadic http 502 errors. They told me today to use ca-api.telldus.com?!

[GFBsoul]

After some editing of tellduslive.py in site packages, the authentication with Telldus Live servers now works. Control of the devices also works as intended.
All the lines in tellduslive.py tha read api.telldus.com was changed to pa-api.telldus.com

TELLDUS_LIVE_API_URL = "https://pa-api.telldus.com/json/"
TELLDUS_LIVE_REQUEST_TOKEN_URL = "https://pa-api.telldus.com/oauth/requestToken"
TELLDUS_LIVE_AUTHORIZE_URL = "https://pa-api.telldus.com/oauth/authorize"
TELLDUS_LIVE_ACCESS_TOKEN_URL = "https://pa-api.telldus.com/oauth/accessToken"

[glye]

@GFBsoul Hi, I had the same problem as you, could not add Telldus Net to HA, same SSL error. Your fix worked. Thanks! Will you do a pull request for that, or shall I? Seems to me a separate issue from what's reported at the top.

[glye]

Slightly related, I'm getting lots of 'Connection timed out' and "error communicating with local " from the bluetooth tracker, though it's working fine. Would be nice to be able to silence these.

[GFBsoul]

@glye No problem! Happy to help. You please go ahead and do that pull request. I'm not fully skilled in the github world :)

[glye]

I don't think anyone is fully skilled in the github world, except maybe Linus Thorvalds on a good day. I'm not familiar with python. The file in question is, on my system: /srv/homeassistant/lib/python3.7/site-packages/tellduslive.py
I haven't found that file, or it's contents, anywhere in HA github. It might be a separate script supplied by Telldus, perhaps.

[stale[bot]]

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.

[glye]

For the record, the wrong-URL problem mentioned by @GFBsoul has been merged in the tellduslive repo: https://github.com/molobrakos/tellduslive/pull/20

[TechnoX]

Thanks for the fix @glye! That fix the problem for me as well. But I had to manually edit /srv/homeassistant/lib/python3.7/site-packages/tellduslive.py on my machine.

It is not updated when running HASS 0.108.6 on a fresh installation (Raspbian Buster). Do you know when it will be integrated?

[glye]

@TechnoX Hi! Sorry, no idea. I see they haven't made any releases in over a year. Someone already asked about it in my pull request, no response since then.