Update Ecovacs documentation (#33075)

Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
Co-authored-by: Robert Resch <robert@resch.dev>
This commit is contained in:
Lorenzo Monaco 2024-06-09 09:20:10 +02:00 committed by GitHub
parent fbceaf7164
commit e3b34cd496
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -140,6 +140,54 @@ Alternatively, you can use the `ecovacs_error` event to watch for errors. This e
Finally, if a vacuum becomes unavailable (usually due to being idle and off its charger long enough for it to completely power off,) the vacuum's `status` attribute will change to `offline` until it is turned back on.
### Getting device and chargers coordinates
The integration has a `raw_get_positions` service to retrieve device and chargers coordinates.
Example:
```yaml
service: ecovacs.raw_get_positions
target:
entity_id: vacuum.deebot_n8_plus
```
{% details "Service response example" %}
The service call returns a raw response with a list of coordinates available in `resp -> body -> data` like this:
```yaml
vacuum.deebot_n8_plus:
ret: ok
resp:
header:
pri: 1
tzm: 480
ts: "1717748487712"
ver: 0.0.1
fwVer: 1.2.0
hwVer: 0.1.1
body:
code: 0
msg: ok
data:
deebotPos:
x: 1
y: 5
a: 85
invalid: 0
chargePos:
- x: 5
y: 9
a: 85
t: 1
invalid: 0
mid: "200465850"
id: 5o81
payloadType: j
```
{% enddetails %}
## Self-hosted configuration
Depending on your setup of the self-hosted instance, you can connect to the server using the following settings: