home-assistant
Ecovacs Deebot X2 don't working
The problem
I have Ecovacs Deebot X2 CN version.
My vacuum is detected, i see sensors (problems, time to change brush or to clean sensors, etc...)
I can see map builded by my vacuum
However I cant even start it. - when I pressing start, stop, home, area buttons nothing happens, vacuum stays at home and does nothing. Attached logs and json.
What version of Home Assistant Core has the issue?
core-2024.9.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Ecovacs
Link to integration documentation on our website
https://www.home-assistant.io/integrations/ecovacs/
Diagnostics information
config_entry-ecovacs-01J8W51FJTWPH0W0GFY49X2FEV.json home-assistant_ecovacs_2024-09-28T11-15-43.249Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
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 closeCloses the issue. -
@home-assistant rename Awesome new titleRenames the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign ecovacsRemoves the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-informationRemove 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)
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
I have a similiar problem. I can configure and login with the integration and see my vacuumer and the sensors. But when I try to controle it, it doesn't work.
These are the only messages what I've got in the log file.
2024-10-11 20:06:44.267 INFO (MainThread) [deebot_client.hardware.deebot] No capabilities found for y79a7u, therefore not all features are available. trying to use fallback...
Looks like your problem is different, and you should open new issue... looks like your device isn't supported at all, even sensors are unavailable...
Any chances to make this damn vacuum work? )) @mib1185 @edenhaus May be u need some additional info?
Thinking about throw my vacuum into bin, and buy something more usable
The Home Assistant was last chance to make my DAMN CHINA SPEAKING DEVICE more user-friendly
@OlegVekhov Hey, buddy, did you fix it? I had the same problem.
@mib1185, @edenhaus, @Augar, Here's my diagnosis
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2024.10.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.12.4",
"docker": true,
"arch": "x86_64",
"timezone": "Asia/Shanghai",
"os_name": "Linux",
"os_version": "6.6.54-haos",
"supervisor": "2024.10.3",
"host_os": "Home Assistant OS 13.2",
"docker_version": "27.2.0",
"chassis": "vm",
"run_as_root": true
},
"custom_components": {
"hacs": {
"documentation": "https://hacs.xyz/docs/configuration/start",
"version": "2.0.1",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"bemfa": {
"documentation": "https://github.com/larry-wong/bemfa",
"version": "1.4.0",
"requirements": [
"paho-mqtt==1.6.1"
]
},
"xiaomi_miot": {
"documentation": "https://github.com/al-one/hass-xiaomi-miot",
"version": "0.7.21",
"requirements": [
"construct>=2.10.68",
"python-miio>=0.5.12",
"micloud>=0.5"
]
},
"midea_ac_lan": {
"documentation": "https://github.com/georgezhao2010/midea_ac_lan#readme",
"version": "v0.3.22",
"requirements": []
}
},
"integration_manifest": {
"domain": "ecovacs",
"name": "Ecovacs",
"codeowners": [
"mib1185",
"edenhaus",
"Augar"
],
"config_flow": true,
"documentation": "https://www.home-assistant.io/integrations/ecovacs",
"iot_class": "cloud_push",
"loggers": [
"sleekxmppfs",
"sucks",
"deebot_client"
],
"requirements": [
"py-sucks==0.9.10",
"deebot-client==8.4.0"
],
"is_built_in": true
},
"setup_times": {
"null": {
"setup": 3.153103170916438e-05
},
"01JAGGEABAF3F239P2RXJVSPM0": {
"wait_import_platforms": -0.060141588968690485,
"wait_base_component": -0.0005324250087141991,
"config_entry_setup": 1.320937151031103
}
},
"data": {
"config": {
"created_at": "2024-10-18T19:07:34.122590+00:00",
"data": {
"username": "**REDACTED**",
"password": "**REDACTED**",
"country": "CN"
},
"discovery_keys": {},
"disabled_by": null,
"domain": "ecovacs",
"entry_id": "01JAGGEABAF3F239P2RXJVSPM0",
"minor_version": 1,
"modified_at": "2024-10-22T14:31:19.293413+00:00",
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"title": "**REDACTED**",
"unique_id": null,
"version": 1
},
"devices": [
{
"did": "**REDACTED**",
"name": "**REDACTED**",
"class": "coldel",
"resource": "jOir",
"company": "eco-ng",
"bindTs": 1705937044957,
"service": {
"jmq": "jmq-ngiot-cn.dc.cn.ecouser.net",
"mqs": "api-ngiot.dc-cn.cn.ecouser.net"
},
"deviceName": "DEEBOT X2",
"icon": "https://portal.ecouser.net/api/pim/file/get/64ddb904b052340008c83cb0",
"ota": true,
"UILogicId": "x2white_cn_h_x2omnih5",
"materialNo": "110-2228-0802",
"pid": "649a83658bbb3f0009ce7a12",
"product_category": "DEEBOT",
"model": "X2_OMNI_WH",
"updateInfo": {
"needUpdate": false,
"changeLog": ""
},
"nick": null,
"homeId": "**REDACTED**",
"homeSort": 1,
"status": 1,
"offmap": true,
"btName": "ECOVACS-coldel-0127",
"btMac": "40:80:E1:9C:03:EF",
"otaUpgrade": {}
}
],
"legacy_devices": []
}
}
@OlegVekhov Hey, buddy, did you fix it? I had the same problem.
No)) looks like guys have no time for now. We're only have to wait... Ecovacs changing his damn commands very often...
Tried to add ecovacs to other apps, like google home, but with no luck, too.
There were many improvements to the underlying library in the last few HA versions - please re-check with the latest HA core version, thx :+1:
I found a solution, if developers fix it it will be great!!
Deebot X2 china codename coldel. The only thingbwe need is to symlink coldel.py to e6ofmn.py
Working flawleslly for a month in my HA installation, modified directly in docker fs.
Make it in upstream, please @edenhaus
@OlegVekhov feel free to contribute your fix to the DeebotUniverse/client.py library, there is also a pinned issue, with a short instruction set how to do it.
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.
![issue-triage-workflows[bot] avatar](https://avatars.githubusercontent.com/u/13844975?v=4 "Published by a pub.dev verified publisher"){kind=small}