-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Error from Telldus live component #8747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This relly affect the use of Telldus live for me, the Telldus is not responding to to commands from HASS. Do you know what possible can trigger this errors @molobrakos ? |
No changes has been made to the Tellduslive component (as far as I know) so I asume this error is because of some change within Hass core. (maybe because the component is not rewritten to being async yet?) |
Can you please turn on logging for the tellduslive component as well as for the tellduslive library?
|
I have terminated my Telldus due to all the latest issues so I can't test this. Maby @pappajohan can help, I know he have the same issue |
Closing this for now, @pappajohan, please reopen this bug if you are able to reproduce it and are willing to help out testing/debugging it (since I can not reproduce it myself). |
Thanks! I have no clue on what to attach but below are a few lines. Please advice what I can do further. Kind regards, 2017-10-19 23:59:38 DEBUG (Thread-6) [tellduslive] Request https://api.telldus.com/json/device/turnOff {'id': '1632847'} |
I believe I have found the reason for this bug. I wasn't aware of the fact that HA expected the library to be thread safe. I have now protected the internal state by a lock and I hope it will be included in the next release of HA. |
Uh oh!
There was an error while loading. Please reload this page.
**Home Assistant release: 0.50.1
**Python release: Python 3.4.2
**Component/platform: Telldus Live
**Description of problem:
Error from Telldus Live component in log. The component is not as reliable as it as previous this errors showed up.
The text was updated successfully, but these errors were encountered: