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
Tado component suddenly broken #35038
Comments
Hey there @michaelarnauts, @bdraco, mind taking a look at this issue as its been labeled with a integration ( |
It looks like you have an old version of the Do you have a custom tado installed that may need to be removed? |
Don't know. Will check it now! |
Do you know perhaps, if this is the case, how to remove it? |
I don't think that I am using a custom tado. After rebooting I get the following errors:
|
Would you try manually installing python-tado in your home assistant environment
|
I am trying but I don't know how to get in the right environment to do this. I am using Raspbian on a raspberry pi 4 with an external SDD. Can connect using ssh to pi@ip_address. But then what? Sorry for being such a noob ;-) And thank you for your help!! |
This comment has been minimized.
This comment has been minimized.
Ok I managed to get into my docker container and to execute the command!
Did not work. |
Its possible you have an old version installed as well Please try the above to force uninstall and reinstall |
Thank you for your help! The same problem remains.
|
It worked perfectly. I did not tweak anything and after pushing an update of home-assistent it just stopped working. |
I'm not sure what is going on with your instance. It doesn't seem like something I'm going to be able to diagnose as the problem appears to be outsite of tado and a problem with the python install stack. It might be best to do a backup, reinstall, and then restore your configuration. |
Thank you! reinstalling worked. |
The problem
Since updating to home assistant 0.108 the tado component in my installation has suddenly stopped working resulting in the errors below.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: