Connection lost every few days, everything unavailable, no control

[capstan1]

Checks

• [X] I have searched the existing issues and no issue is describing my issue
• [X] I have checked the FAQ
• [X] I have checked the documentation
• [X] I have installed the latest version

The problem

After some time (usually days) the ecovacs integration loses connection. It's similar to #226 with the difference that that all atributes are "not available" and I cannot control the deebot. (Actually had the same as #226 before, but some months ago it changed to the new behaviour.) Restarting HA or the integration solves the issue temporarily. I kinda got the impression it happens when the robot gets trapped somewhere and goes to standby to save battery (when the app shows it as offline). Like it doesn't establish connection to HA afterwards. But frankly: the T8+ gets trapped a lot, so I'm not really sure 😄

Hope there is something useful in there

Diagnostics information

didn't find where to dowload ot in HA devices

That's what the logs show: (for info :it did a cleaning job started by HA on 2022-08-15 01:00:00 hours, didn't start on 2022-08-16 at the same time, noticed it went offline in the morning)

1) The error HA shows at the top:

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: custom_components.deebot.hub
Source: custom_components/deebot/hub.py:113
Integration: Deebot 4 Home Assistant (documentation, issues)
First occurred: 13. August 2022 um 13:05:54 (3 occurrences)
Last logged: 14. August 2022 um 02:26:14

failure (3002) on getting devices
Traceback (most recent call last):
  File "/config/custom_components/deebot/hub.py", line 103, in _check_status_task
    await self._check_status_function()
  File "/config/custom_components/deebot/hub.py", line 113, in _check_status_function
    devices = await self._api_client.get_devices()
  File "/usr/local/lib/python3.10/site-packages/deebot_client/api_client.py", line 61, in get_devices
    raise ApiError(
deebot_client.exceptions.ApiError: failure  (3002) on getting devices

2) The startup logs

2022-08-13 09:49:26.391 INFO (MainThread) [custom_components.deebot]
-------------------------------------------------------------------
deebot
Version: 1.4.1
This is a custom component
If you have any issues with this you need to open an issue here:
https://github.com/DeebotUniverse/Deebot-4-Home-Assistant/issues
-------------------------------------------------------------------
2022-08-13 09:49:31.073 INFO (MainThread) [homeassistant.components.vacuum] Setting up vacuum.tuya
2022-08-13 09:49:31.628 DEBUG (MainThread) [custom_components.deebot.hub] New vacbot found: E09514103B09HEKR0001
2022-08-13 09:49:31.628 DEBUG (MainThread) [custom_components.deebot.hub] Hub setup complete
2022-08-13 09:49:31.682 INFO (MainThread) [homeassistant.components.vacuum] Setting up vacuum.deebot

3)every line containing deebot:

2022-08-13 09:49:26.391 INFO (MainThread) [custom_components.deebot]
deebot
https://github.com/DeebotUniverse/Deebot-4-Home-Assistant/issues
2022-08-13 09:49:31.628 DEBUG (MainThread) [custom_components.deebot.hub] New vacbot found: E09514103B09HEKR0001
2022-08-13 09:49:31.628 DEBUG (MainThread) [custom_components.deebot.hub] Hub setup complete
2022-08-13 09:49:31.682 INFO (MainThread) [homeassistant.components.vacuum] Setting up vacuum.deebot
2022-08-13 13:05:54.395 ERROR (MainThread) [custom_components.deebot.hub] failure (3002) on getting devices
File "/config/custom_components/deebot/hub.py", line 103, in _check_status_task
File "/config/custom_components/deebot/hub.py", line 113, in _check_status_function
File "/usr/local/lib/python3.10/site-packages/deebot_client/api_client.py", line 61, in get_devices
deebot_client.exceptions.ApiError: failure (3002) on getting devices
2022-08-13 23:54:04.532 ERROR (MainThread) [custom_components.deebot.hub] failure (3002) on getting devices
File "/config/custom_components/deebot/hub.py", line 103, in _check_status_task
File "/config/custom_components/deebot/hub.py", line 113, in _check_status_function
File "/usr/local/lib/python3.10/site-packages/deebot_client/api_client.py", line 61, in get_devices
deebot_client.exceptions.ApiError: failure (3002) on getting devices
2022-08-14 00:30:00.204 INFO (MainThread) [custom_components.deebot]
deebot
https://github.com/DeebotUniverse/Deebot-4-Home-Assistant/issues
2022-08-14 00:30:03.343 DEBUG (MainThread) [custom_components.deebot.hub] New vacbot found: E09514103B09HEKR0001
2022-08-14 00:30:03.344 DEBUG (MainThread) [custom_components.deebot.hub] Hub setup complete
2022-08-14 00:30:03.368 INFO (MainThread) [homeassistant.components.vacuum] Setting up vacuum.deebot
2022-08-14 02:26:14.625 ERROR (MainThread) [custom_components.deebot.hub] failure (3002) on getting devices
File "/config/custom_components/deebot/hub.py", line 103, in _check_status_task
File "/config/custom_components/deebot/hub.py", line 113, in _check_status_function
File "/usr/local/lib/python3.10/site-packages/deebot_client/api_client.py", line 61, in get_devices
deebot_client.exceptions.ApiError: failure (3002) on getting devices
2022-08-15 00:30:00.215 INFO (MainThread) [custom_components.deebot]
deebot
https://github.com/DeebotUniverse/Deebot-4-Home-Assistant/issues
2022-08-15 00:30:00.982 DEBUG (MainThread) [custom_components.deebot.hub] New vacbot found: E09514103B09HEKR0001
2022-08-15 00:30:00.983 DEBUG (MainThread) [custom_components.deebot.hub] Hub setup complete
2022-08-15 00:30:00.995 INFO (MainThread) [homeassistant.components.vacuum] Setting up vacuum.deebot
2022-08-15 01:00:00.654 DEBUG (MainThread) [custom_components.deebot.vacuum] async_send_command spot_area with {'rooms': '0, 5', 'cleanings': 2}
2022-08-15 09:00:00.140 DEBUG (MainThread) [custom_components.deebot.vacuum] async_send_command setAutoEmpty with {'act': 'start'}
2022-08-15 09:00:30.356 DEBUG (MainThread) [custom_components.deebot.vacuum] async_send_command custom_area with {'coordinates': '-837,138,1811,-2857'}
2022-08-15 09:02:10.608 DEBUG (MainThread) [custom_components.deebot.vacuum] async_send_command setAutoEmpty with {'act': 'start'}`

Additional information

No response

[edenhaus]

To download the diagnostic information do the following: Unter Einstellungen -> Geräte & Dienste -> Auf 1 Gerät klicken unter Deebot 4 Home Assistant (bzw. auf Geräte falls du mehrere hast und anschließend wählst du das Gerät aus) -> unter Geräte Informationen kommt leicht verzögert ein Download Button.

Also when I understand German, please keep all information here in English so everyone can understand it.

[capstan1]

Thanks a lot! Did search in this page, but apperantly didnt spot it! deebot-30c260ab4237d488b4b0cb6d42c73ccb-Moppi-ede59806cf7a6d078e11f35296152eb9.json.txt

[edenhaus]

@mrbungle64 do you know what the error 3002 of get_devices means?

[mrbungle64]

@mrbungle64 do you know what the error 3002 of get_devices means?

@edenhaus

No, unfortunately I don't know what the error 3002 means

[capstan1]

Anything else I can provide to debug this? Getting an offline robot pretty much every day. Have to restart HA everytime it happens. Some months ago, reload_config_entry worked but this throws out an error now (probably smth. Changed in HA)

Is there any command to reload the integration like I can do from the integrations overview?

[LucaBors]

Same problem here. I've an automation that launch cleaning of my 2 deebot. It always work, what does not work is the status update to cleaning. My problem is that i've another automation that, when my alarm is on and cleaning start, it deactivate movement sensor. Since it result non available (it stay in idle state) there is no way to change alarm status and my alarm trigger :D

[edenhaus]

@LucaBors Are you getting also the error 3002 like in the logs above?

[edenhaus]

@capstan1 Can you please check your logs also for gmqtt logs. It‘s the library used to connect via mqtt and over mqtt the status updates are coming. The problem is, we need to find out, what the error 3002 means. Unfortunately I don‘t can reproduce your issue.

[LucaBors]

Hi @edenhaus can you please provide me instruction on how to provide you those logs? Thank you

[edenhaus]

Sorry @LucaBors I did forgotten to answer you. Please check out https://deebot.readthedocs.io/integrations/home-assistant/issues/ to activate debug logs

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[redford-jones]

I have this issue, but I've found it's only limited to the status retrieval from the Ecovac API. I'm able to send operation commands to the Vacuum successfully, e.g. start an auto clean works, return to dock works.

issue was also raised in #226