roomba-cli

<quick_start> The roomba CLI follows this pattern:

roomba <command-group> <action> [arguments] [options]

Task	Command
Quick status check	roomba status
List robots	roomba robots list --table
Start cleaning	roomba control start
Stop cleaning	roomba control stop
Send to dock	roomba control dock
Find robot (beep)	roomba control find
Evacuate bin	roomba control evac
Detailed status	roomba control status
</quick_start>

<essential_principles> MANDATORY: Consult the adjacent usage.json at <cli-tools-root>/_repo/skills/<tool>-cli/usage.json before executing ANY roomba command. This file contains complete command syntax, all arguments, all options, and usage instructions for every command. Never guess at command syntax.

<reference_index> usage.json -- Complete command tree with arguments, options, defaults, and usage instructions for every command. </reference_index>

<success_criteria>

• Command executes without error
• Output is displayed in requested format
• Correct command and flags used (verified against usage.json) </success_criteria>

<cloud_reads> Verified 2026-10-20 against successful authorized app traffic and live CLI reads. cloud import-capture PRIVATE_PATH imports temporary AWS credentials through the CLI-tools secret manager, cloud inventory, and exact supported successful GET request templates. The decoder runs through pinned mitmproxy 12.2.3 via uv. It requires a successful app /v2/login in the capture. A matching Gigya session is verified before enabling automatic AWS/MQTT renewal. Captured old login proofs and account/robot passwords are never retained. Requests must match that login's access key, or another captured login with identical Cognito identity and robot/deployment membership. Keep captures and raw output in private non-synced storage.

Use cloud robots list to inspect multiple captured vacuums, cloud select NAME_OR_ID for the local cloud default, or cloud read history --robot NAME_OR_ID for explicit selection. Robot history/setup templates are isolated by exact cloud robot ID. cloud read schedule and cloud read entitlements are shared household/account reads. A resource absent from that vacuum's capture fails explicitly. Local LAN configuration and robot passwords are preserved. Temporary tokens renew automatically when a verified reusable Gigya session was imported. Rejection or expiration of that underlying session requires a fresh authorized app login capture.

Label this evidence Local source. Cloud data never establishes live device status or robot execution. The existing LAN path remains separate. This group supports both captured vacuum models; model-specific repair guidance still requires the appropriate hardware source. See the CLI README for redacted provenance and operating limits. Consult the adjacent generated usage map before commands. </cloud_reads>

<read_surface> cloud status --robot NAME_OR_ID reports model-specific observed telemetry with per-field metadata age; snapshots never prove current physical online status. cloud schedules --robot NAME_OR_ID reads both household and stored robot schedules. Household membership must match the selected robot. Empty household schedules do not establish that stored robot schedules are empty. cloud favorites list/get reads actual favorite definitions and enforces exact robot membership. Favorites are never started by a read command.