core: Massive error log from Telldus component
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:
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 27
Commits related to this issue
- Change api.telldus.com to pa-api.telldus.com Hi, I had to do this fix to be able to connect to Telldus using Home Assistant. It was suggested by @GFBsoul in this thread: https://github.com/home-assis... — committed to glye/tellduslive by glye 5 years ago
- Change api.telldus.com to pa-api.telldus.com (#20) Hi, I had to do this fix to be able to connect to Telldus using Home Assistant. It was suggested by @GFBsoul in this thread: https://github.com/home... — committed to molobrakos/tellduslive by glye 4 years ago
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.
@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.
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