A faulty plugin brought down my HA out of nowhere? (Ecovacs)

Configuration
1

I just woke up and noticed that HA is down, I checked my docker logs and noticed that there are bunch of repeating logs of the Ecovacs extension having issues.
I did not update or mess around in any way with my setup which confuses me why it would break out of nowhere? The whole docker logs was repeating this issue below:

        1 ^[[33m2026-07-21 07:28:59.835 WARNING (MainThread) [deebot_client.command] Could not execute command getWorkState for c8rj4y
       2 Traceback (most recent call last):
       3   File "/usr/local/lib/python3.14/site-packages/deebot_client/command.py", line 76, in execute
       4     result, response = await self._execute(
       5                        ^^^^^^^^^^^^^^^^^^^^
       6         authenticator, device_info, event_bus
       7         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       8     )
       9     ^
      10   File "/usr/local/lib/python3.14/site-packages/deebot_client/command.py", line 110, in _execute
      11     response = await self._execute_api_request(authenticator, device_info)
      12                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      13   File "/usr/local/lib/python3.14/site-packages/deebot_client/command.py", line 157, in _execute_api_request
      14     credentials = await authenticator.authenticate()
      15                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      16   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 374, in authenticate
      17     self._credentials = await self._auth_client.login()
      18                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      19   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 115, in login
      20     login_password_resp = await self.__call_login_api(
      21                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      22         self._account_id, self._password_hash
      23         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      24     )
      25     ^
      26   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 186, in __call_login_api
      27     return await self.__do_auth_response(
      28            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      29         url, self.__sign(params, self._meta, _CLIENT_KEY, _CLIENT_SECRET)
      30         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      31     )
      32     ^
      33   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 165, in __do_auth_response
      34     raise AuthenticationError(msg)
      35 deebot_client.exceptions.AuthenticationError: failure code 1013 (Please update to the latest version to continue.) for call https://gl-us-api.ecovacs.com/v1/private/us/EN/ZJT8DMQ2/global_e/1.6.3/google_play/1/user/login^[[0m
      36 ^[[31m2026-07-21 07:30:00.567 ERROR (MainThread) [deebot_client.authentication] call to https://gl-us-api.ecovacs.com/v1/private/us/EN/ZJT8DMQ2/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the
      37 ^[[33m2026-07-21 07:30:00.567 WARNING (MainThread) [deebot_client.command] Could not execute command getBattery for c8rj4y
      38 Traceback (most recent call last):
      39   File "/usr/local/lib/python3.14/site-packages/deebot_client/command.py", line 76, in execute
      40     result, response = await self._execute(
      41                        ^^^^^^^^^^^^^^^^^^^^
      42         authenticator, device_info, event_bus
      43         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      44     )
      45     ^
      46   File "/usr/local/lib/python3.14/site-packages/deebot_client/command.py", line 110, in _execute
      47     response = await self._execute_api_request(authenticator, device_info)
      48                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      49   File "/usr/local/lib/python3.14/site-packages/deebot_client/command.py", line 157, in _execute_api_request
      50     credentials = await authenticator.authenticate()
      51                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      52   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 374, in authenticate
      53     self._credentials = await self._auth_client.login()
      54                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      55   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 115, in login
      56     login_password_resp = await self.__call_login_api(
      57                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      58         self._account_id, self._password_hash
      59         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      60     )
      61     ^
      62   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 186, in __call_login_api
      63     return await self.__do_auth_response(
      64            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      65         url, self.__sign(params, self._meta, _CLIENT_KEY, _CLIENT_SECRET)
      66         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      67     )
      68     ^
      69   File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 165, in __do_auth_response
      70     raise AuthenticationError(msg)
      71 deebot_client.exceptions.AuthenticationError: failure code 1013 (Please update to the latest version to continue.) for call https://gl-us-api.ecovacs.com/v1/private/us/EN/ZJT8DMQ2/global_e/1.6.3/google_play/1/user/login^[[0m
      72 ^[[31m2026-07-21 07:31:00.872 ERROR (MainThread) [deebot_client.authentication] call to https://gl-us-api.ecovacs.com/v1/private/us/EN/ZJT8DMQ2/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the

Any idea what happend here? And why it crashed my HA?

2

Ecovacs integration is having issues, I have it mine for last couple of days and there are some bugs capturing it already.

But, it is not supposed to take down your HA given that it is just a failing integfation. It is interesting.

3

Yeah that may have been a red herring. I disabled it and it crashed again (this time raising some MQTT and hatch integration issues). Best I can think of is that some system component went down and/or an update was auto-applied that messed with the system. Doing a clean re-install and then will reboot and see how it goes.