-
Notifications
You must be signed in to change notification settings - Fork 85
Open
Description
Linking home-assistant/core#161038 here as this repo seems to be a root cause:
Logger: homeassistant
Quelle: components/tado/config_flow.py:85
Erstmals aufgetreten: 07:17:21 (8 Vorkommnisse)
Zuletzt protokolliert: 07:32:32
Error doing job: Task exception was never retrieved (task: None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/tado/config_flow.py", line 82, in _wait_for_login
await self.hass.async_add_executor_job(self.tado.device_activation)
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.13/site-packages/PyTado/interface/interface.py", line 107, in device_activation
self._http.device_activation()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/PyTado/http.py", line 584, in device_activation
if self._check_device_activation():
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/PyTado/http.py", line 575, in _check_device_activation
raise TadoException(f"Login failed. Reason: {token_response.reason}")
PyTado.exceptions.TadoException: Login failed. Reason: Bad Request
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/tado/config_flow.py", line 85, in _wait_for_login
raise CannotConnect from ex
homeassistant.components.tado.config_flow.CannotConnect
https://github.com/home-assistant/core/blob/dev/homeassistant/components/tado/config_flow.py#L82
UPDATE: re-linking this to more relevant: home-assistant/core#160472
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels