Skip to content
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.

Command to send Deebot to coordinate #410

Open
1 task done
Denkra opened this issue Aug 26, 2023 · 4 comments
Open
1 task done

Command to send Deebot to coordinate #410

Denkra opened this issue Aug 26, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@Denkra
Copy link

Denkra commented Aug 26, 2023

Is there an existing issue for this?

  • I have searched the existing issues and no issue is describing my feature request or idea

Is your feature request related to a problem?

I have the T9 AIVI and I miss the function of sending the vacuum cleaner to a specific coordinate and then stopping it. I noticed in the logs that {"type":"mapPoint","value":"707,271"} is being transmitted. Can this be integrated somehow?

Suggested solution

Include the "mapPoint" command so that you can send the vacuum cleaner to a specific coordinate without it starting a suction process there.

Api example request

No response

Alternatives you've considered

No response

Additional information

No response

@Denkra Denkra added the enhancement New feature or request label Aug 26, 2023
@edenhaus
Copy link
Contributor

Please feel free to add this command to https://github.com/DeebotUniverse/client.py
As my robot does not support this command, I don't have any knowledge for adding it.
But I can give you tips and feedback if you want :)

As a first step, I would suggest activating debug logs or even better capturing the traffic of the ecovacs app while sending the command multiple times. It is needed to find out the permutation/combinations of the new command.

@Denkra
Copy link
Author

Denkra commented Aug 28, 2023

Unfortunately I'm not familiar with that. So help would be really great. When I look in the debug log I always find the same line when I send the vacuum cleaner to a certain position.
Here I think that "value" is then the coordinates where I send it and "mappoint" is then the command. If I do an area cleaning, it is structured the same way, only then there are four coordinates and a different command.

{"pri":1,"tzm":480,"ts":"1693232817140","ver":"0.0.1","fwVer":"1.4.9","hwVer":"0.1.1"},"body":{"data":{"trigger":"app","state":"clean","cleanState":{"cid":"122","router":"plan","motionState":"working","content":{"type":"mapPoint","value":"307,571"}}}}}'

What I also saw was the line

[deebot_client.mqtt_client] Command getMapPoint does not support p2p handling (yet)

Does that have anything to do with it?

@grandmastermarco
Copy link

I dont know which bot you have. But maybe try this setup in home assistant :

Service : vacuum: send command
Command: clean_v2
Parameters:

act: start
content:
type: customArea
total: 0
donotClean: 1
count: 1
value: "307,571,307,571"

@grandmastermarco
Copy link

OR based on your last comment (very wild guess).

Service :
vacuum: send command

Command:
clean

Parameters:
act: start
content:
type: mapPoint
value: "307,571"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants