Telldus API error in log and switches unavailable

Configuration
1

Lately I’ve started to get telldus switches showing up as unavailable in lovelace UI. The switches are working if I go to telldus directly.

Looking in home assistant log I have loads of these lines:

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 ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at 0x6fc11650>, ‘Connection to api.telldus.com timed out. (connect timeout=10)’))

Any idea how to solve these? I’ve removed and added telldus live cloud api numerous times and it works for a while with switches and sensors showing up in HA automatically and then switches turn unavailable again after a while.

2

I have the same problem for about two or three days.
Same lines in my log.
I see in my firewall that HA is making the requests to api.telldus.com. Sometimes gets timeouts (SYN Timeout).

Feels like maby Telldus having some problems with their API?
Their operating status page tells me that the service is working as i should thou.
I think I will send them an email anyway…

3

I’v had the same issue since I upgraded to .87 (though it might be a coincidence).
I have tried to remove telldus live and add it all again as well but it keeps koming back. In the logs it seems like it misses every 2-3 call. It also means that telldus swithces are unstable. Sometimes it works and sometimes it doesn’t trigger them.

4

I’m still on version 0.82 and haven’t upgraded for a while.

This is how it looks in my history-tab (all the small lines are “unavailable”):

2019-03-05%2014_01_17-Home%20Assistant
2019-03-05%2014_01_17-Home%20Assistant1390×31 3.99 KB

Currently have a ticket at Telldus support. Unfortunatly we haven’t found any errors yet.

5

Alright, that’s “good” to hear that I’m not alone with the issue at least. I’m gonna go to Telldus forum and report it as well somehow.

Do you have a link to your issue report?

6

Hi,
Same problem for me but switches seem to work still, for me atleast.
But log is filled with telldus errors so hard to se other errors. I’m not sure when this showed up for me in the logs but not that long ago, maybe last week? It could be same as @haqwin is writing. I’m on latest hassio and HA on Ri3, update as versions come out.

I’m honestly working to get rid of all telldus stuff from my home just because of what @ols shows, they are very unreliable sadly. :frowning: and have been for a long time, i use only 433mhz with telldus so not a hard choice to go z-wave and zigbee :slight_smile:

7

Yeah I’m doing the same as @sabbath , just have 3 more swithces on telldus and a couple of temperature sensors. Then I’m done with the shift.

I tried to find a place to report this on telldus but were unable to find it currently. If anyone has a link it would be great to show that we are more with the same issues.

8

Not sure how easy it is to mod this but I thought I’ll post it here anyway.

9

Same here in 0.89.1

10

Found that this is caused by new version of SSL. I changed (maybe you do not want that cause it is not safe, but I did) to lower requirements. Found this on the net:

You don’t have to downgrade OpenSSL.

With the introduction of openssl version 1.1.1 in Debian the defaults are set to more secure values by default. This is done in the /etc/ssl/openssl.cnf config file. At the end of the file there is:

[system_default_sect]
MinProtocol = TLSv1.2
CipherString = DEFAULT@SECLEVEL=2

Debian now require as minimum the TLS 1.2 version instead TLS 1.0. If the other side does not support TLS 1.2 or higher you will get some connection errors.

I recommend upgrade openvpn on server to newer version which support TLS 1.2. .

Second options (not much secure) is modify MinProcotol to TLSv1 or TLSv1.1.

==> I changed to TSLv1 and rebooted my hassbian…now it works.

2 Likes