ecovacs-skills-deebot-control — ecovacs-技能s-dee机器人-control

Ecovacs Dee机器人 control What you need 输入 Notes AK (访问 Key) 创建 or view it in the Ecovacs Open 平台 “服务 overview” (China: https://open.ecovacs.cn/, Global: https://open.ecovacs.com/), then copy it into env vars, a config file, or chat yourself. Pick the portal region that matches your account. Do not hand account passwords to 自动化; this 技能 does not 记录 in on your behalf. Gateway base URL (optional) Defaults to the same host as the Open 平台 (China https://open.ecovacs.cn, Global https://open.ecovacs.com). Override with ECOVACS_PORTAL_URL for a self-hosted or local gateway (e.g. mcp_portal_服务s). Device nickname fragment Used to pick one ro机器人. Take a substring of nick or name from the device 列出 (fuzzy match).

If the AK is invalid (e.g. errno 3000), refresh it on the Open 平台—do not try to replace user 记录in with other APIs.

Three steps 配置 AK → 2. Device 列出 → 3. 发送 commands

• 配置 AK (pick one)

导出 ECOVACS_AK="YOUR_AK" # or: python3 scripts/ecovacs.py 设置-ak # writes ~/.ecovacs_会话.json with {"ak":"..."} only

• Device 列出

python3 scripts/ecovacs.py devices

Note the nick / name fragment you will use as below.

• Common 命令行工具 operations

Let SCRIPT=scripts/ecovacs.py.

Queries Battery: python3 "$SCRIPT" battery Work 状态 (清理 / charge / station): python3 "$SCRIPT" 状态 清理ing Whole-home auto 清理: python3 "$SCRIPT" 清理 启动 暂停 / 恢复 / 停止: python3 "$SCRIPT" 清理 暂停 or 恢复 / 停止 Charging Go charge / 停止 go-charge: python3 "$SCRIPT" charge go or 停止 HTTP gateway (no Python)

BASE_URL is the same as ECOVACS_PORTAL_URL (defaults to the regional Open 平台 host).

Device 列出

curl -sS "${BASE_URL}/ro机器人/技能/device列出?ak=YOUR_AK"

Control: POST /ro机器人/技能/ctl with JSON ak, optional nickName (fuzzy match on 列出), and ctl.cmd / ctl.data.

curl -sS -X POST "${BASE_URL}/ro机器人/技能/ctl" -H 'Content-Type: 应用/json' \ -d "{\"ak\":\"${AK}\",\"nickName\":\"nick-fragment\",\"ctl\":{\"cmd\":\"Charge\",\"data\":{\"act\":\"go\"}}}"

CloudCtl expects Charge, 清理, etc. with official casing—not lowercase charge.

More JSON examples (e.g. zone 清理) are in references/API.md.

Errors and enums (troubleshooting)

响应s are usually two layers: outer msg / code; inner cloudctl payload under nested ctl.data with ret (ok/fAIl), errno, optional error.

Situation Meaning / next step 应用endix F 5009 Command or parameter combo not supported on this 模型 (casing, firmware); 验证 模型, try 获取Work状态 / 获取Battery信息 naming 应用endix F 10004 Offline / timeout / powered off / re-provisioned 应用endix F 10000 Low battery, cannot 运行 应用endix F 10005 Host fault (lifted, dustbin missing, …) 清理 10006 / Charge 10006 Internal host fault (应用endix C/D) 应用endix F 4000 Malformed JSON 应用endix F 4504 令牌 检查 fAIled—验证 AK ret=fAIl Read errno and error to获取her

Water level: In sweep-only mode (no mopping / tank inactive), 设置Water信息 often fAIls (ret=fAIl); switch to a mopping-capable mode first.

清理 enums: act = s/p/r/h; workMode 0–3; zone 清理 uses type=spotarea + AId from 获取Area列出 mssid. Charge: go / 停止Go.

Full tables: see “CloudCtl errors and enums” at the end of references/API.md.

How to read the docs File Audience Contents This 技能.md End users 输入s, three steps, 命令行工具, HTTP references/API.md Integrators Paths, bodies, enums, curl references/代理-internal.md Internal Smart 清理, rooms, polling, 获取Work状态 heuristics

Prefer this page for user-facing 图形界面dance; use references/代理-internal.md only when you need implementation-level troubleshooting.