-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ecovacs deebot x2 won't start #110177
Comments
Hey there @OverloadUT, @mib1185, @edenhaus, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) ecovacs documentation |
Please add the config entry diagnostic information. Without I cannot help you. Thanks |
where can i find the config entry diagnostic information.
…________________________________
Van: Robert Resch ***@***.***>
Verzonden: maandag 12 februari 2024 09:30
Aan: home-assistant/core ***@***.***>
CC: bce626 ***@***.***>; Author ***@***.***>
Onderwerp: Re: [home-assistant/core] ecovacs deebot x2 won't start (Issue #110177)
Please add the config entry diagnostic information. Without I cannot help you. Thanks
—
Reply to this email directly, view it on GitHub<#110177 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFNGURCMAFIGDWNF2R3J4XTYTHHJLAVCNFSM6AAAAABDCU7IS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYGIZDQMRTGI>.
You are receiving this because you authored the thread.
|
here you can find the diagnostics data |
You have still installed the custom component |
I took Ecovacs out of devices and services and then a reboot. Then took it out of HACS and rebooted again. After the restart, I looked up the application in devices and services and installed it on new, but the problem remains. Logger: deebot_client.message Could not parse getCleanInfo: {'code': 20003, 'msg': 'rcp not support'} |
It looks like Ecovacs introduced a new cleaning command, which is currently unsupported by |
@bce626 Does the Map work with your X2? I get all the status information, but the map only returns HTTP 500, but I did not investigate any further until now... |
@chrfin No, the Map does not work. I get a broken logo sign. |
I have the same issue, the map was working before the migration. Now it's a broken logo sign. |
Same to me. Map not working. |
Same to me. Map not working. 500 code |
It will not help to comment "Same to me". Please use reactions on the issue descriptions. I don't own an X2 and therefore I cannot implement support for it. Someone with an X2 needs to add the missing commands to the client. |
Dear @edenhaus, I have a Omni X2 available for testing. If you could give some guidance how to experiment with the coding? I have some experience. |
I have an x2 Omni too. If the X1 working fully now, how to get at the config data in python 3.12(have searched, cant find the whole dir ^^) As i have seen, the classfile and the reference is missing (must be "class": "lf3bn4"), but without to come into the deebot-client directory in python... But as i sayed, without access to deebot-client directory i cant give it a try to make some files. Any hint how to come into the magic parts would be great(i'm not an programmer nor did i anything with homeassistant scripting, but be an sysadmin) |
Should be fixed with #116025 |
I am on 2024.5.0 and map is still not working for x2. |
X2 got the device file in 7.0.0 deebot_client(this is the main component for functionality) But it is referenced to the Deebot T20, 7.0.1 gives the X2 his own featureset but with the map settings from T20(still) I would love to test it in my own HA installation first, but i can't find a way to go into the needed container at file level. there are some things that will be better with deebot_client 7.0.1, more sensors(round mop, voice etc), but the map and the rooms are obvious bound together and need some try and error with the v2 map generation(my hope that this will do the trick then later) generally my x2 send the rooms in debuglog, but at the end they are not in the vaccum entity at the moment |
While the map is fixed, this specific issue is not in deebotclient 7.2.0
@edenhaus I know this is not something you can fix, but could you re-open the issue? |
I have an Ecovacs Deebot X2. When I try to start it, it won't work. In the logs, I see the error message: 'Command "clean" was not successful. Body={'code': 20003, 'msg': 'rcp not support'}.' any help, please. |
Hi, I have the same problem. Start, stop and pause don't work! :( |
I cannot analyze and debug the problem as I don't have the model. The only one who can solve it is you all by analyzing the traffic of the app and checking what is different |
Hi, how can I analyse the traffic of the app ? What application do you use to analyze the frames ? |
Hi @edenhaus, you can find attached my wireshark data of my iphone. Thanks |
@sebcbien37 Did you use a proxy in between otherwise we cannot inspect the traffic as it is encrypted. |
Hi, {"body":{"data":{"act":"go"}},"header":{"channel":"iOS","reqid":"XXXXXX","ts":"XXXXXX","ver":"0.0.50","m":"request","pri":1,"tzm":120}} {"body":{"data":{"act":"stop"}},"header":{"channel":"iOS","reqid":"XXXXXX","ts":"XXXXXX","ver":"0.0.50","m":"request","pri":1,"tzm":120}} {"body":{"data":{"act":"pause"}},"header":{"channel":"iOS","reqid":"XXXXXX","ts":"XXXXXX","ver":"0.0.50","m":"request","pri":1,"tzm":120}} { |
The important part is probably |
I've finally had some time to enter the game using mitmproxy. The ecovacs deebot x2 also uses clean_v2:
And this is the stop command:
|
I just bought a Ecovacs Deebot X2 Omni on the Amazon Prime day. Most items are working with HA (including the map) except the following commands. They all use clean_v2. I managed to capture the commands using mitmproxy. `Start - no specific rooms Pause Resume Stop Clean laundry room only (room number 6) Clean two rooms (14 & 11) ` |
Please feel free to extend the client library at https://github.com/DeebotUniverse/client.py |
The attached code files fix stop, start and pause for the X2 Omni. Tested with my X2. service: vacuum.send_command
target:
entity_id: vacuum.deebot
data:
command: clean_V2
params:
act: start
content:
type: freeClean
value: 1,6 I'm not familiar with how changes are promoted to Github. |
@edenhaus |
As I'm following any changes of this issue, pinging me will not help. |
It confirmed working for me in my Hass Dev instance :) Great work !!! |
Hi, could you push the update ? Thanks. |
The problem
Ecovacs Deebot X2 won't start when you give the command to clean via home assistant.
Next in the log
"
Logger: deebot_client.commands.json.common
Source: components/ecovacs/vacuum.py:319
First occurred: 12:23:22 (2 occurrences)
Last logged: 12:23:25
Command "clean" was not successfully. body={'code': 20003, 'msg': 'rcp not support'}
"
home-assistant_ecovacs_2024-02-10T11-24-41.525Z.log
What version of Home Assistant Core has the issue?
2024.2.1
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
home-assistant_ecovacs_2024-02-10T11-24-41.525Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: