Ecovacs Deebot X5 OMNI won't receive any command

[naked-head]

The problem

I am experiencing the same issue as described in (#110177) with X2 model. Specifically, the robot does not accept any commands, and the error I receive is identical:

Command "clean" was not successfully. body={'code': 20003, 'msg': 'rcp not support'}

Details:

• Robot Model: Recognized by the system.
• Map: Working and dynamically updated.
• Sensors: Most are working, except for the IP address, WiFi SSID, WiFi RSSI and Last Work.
• Settings Changes: The robot receives and applies changes such as water level, clean count, true detect, and continuous cleaning.

Commands:

• Working: "Find my position" is the only command that currently works.
• Not Working: Start, stop, pause, and send_command do not function.

What version of Home Assistant Core has the issue?

core-2024.8.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

ecovacs

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ecovacs/

Diagnostics information

home-assistant_ecovacs_2024-08-21T12-43-31.125Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

024-08-21 14:43:18.579 DEBUG (MainThread) [deebot_client.mqtt_client] Command clean does not support p2p handling (yet)
2024-08-21 14:43:18.654 DEBUG (MainThread) [deebot_client.authentication] Success calling api url=https://portal-eu.ecouser.net/api/iot/devmanager.do, params={'mid': '4jd37g', 'did': '743dca60-af45-496a-9201-339f770a83f4', 'td': 'q', 'u': 'ihonjm249035907b', 'cv': '1.67.3', 't': 'a', 'av': '1.3.1'}, json={'cmdName': 'clean', 'payload': {'header': {'pri': '1', 'ts': 1724244198.335647, 'tzm': 480, 'ver': '0.0.50'}, 'body': {'data': {'act': 'start', 'type': 'spotArea', 'content': '10', 'count': 1}}}, 'payloadType': 'j', 'td': 'q', 'toId': '743dca60-af45-496a-9201-339f770a83f4', 'toRes': 'bGR4z2MD', 'toType': '4jd37g'}, response={'ret': 'ok', 'resp': {'body': {'code': 20003, 'msg': 'rcp not support'}, 'header': {'fwVer': '1.66.0', 'hwVer': '0.1.1', 'pri': 1, 'ts': '1724244197074', 'tzm': 480, 'ver': '0.0.1', 'wkVer': '0.1.54'}}, 'id': 'RARK', 'payloadType': 'j'}
2024-08-21 14:43:18.654 WARNING (MainThread) [deebot_client.commands.json.common] Command "clean" was not successfully. body={'code': 20003, 'msg': 'rcp not support'}
2024-08-21 14:43:23.844 DEBUG (SyncWorker_3) [deebot_client.map] [get_svg_map] No need to update
2024-08-21 14:43:27.247 DEBUG (SyncWorker_6) [deebot_client.map] [get_svg_map] No need to update

Additional information

No response

[home-assistant]

Hey there @mib1185, @edenhaus, @Augar, mind taking a look at this issue as it has been labeled with an integration (ecovacs) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ecovacs can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ecovacs Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

ecovacs documentation
ecovacs source
_{^{(message by IssueLinks)}}

[edenhaus]

Please provide the diagnostic information. How you can download, can be found here

[naked-head]

I think I have already uploaded, is not this what you search for?
home-assistant_ecovacs_2024-08-21T12-43-31.125Z.log

[edenhaus]

Nope you have uploaded only the logs and not the diagnostic information. Without it we cannot help you

[naked-head]

I apologize for the repeated mistakes. I'm sorry about that. Here is the correct file.

config_entry-ecovacs-01J5ACP7675WCN57CV1YCJ160M.json

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[edenhaus]

Probably the same issue as #110177. Can you add your model to the client library?

[naked-head]

Excuse me for the delayed response, but I haven't been able to access my HomeAssistant during this period.
How can I do that?
Please let me know what to add and in which file.
Thanks

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[leoazz]

The deebot X5 OMNI still don't receive any command. It seems like this model is not added in the ecovacs integration. Please add the X3 OMNI

[nicoh88]

Same here. Please add X5 OMNI.

[nicoh88]

@edenhaus

Shouldn't the problem be solved with the merge on September 5? Or is the merge not yet included in the current Home Assistant version?

home-assistant_2024-10-23T06-31-45.731Z.log

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.