> Execution rule: use the exec tool to run the shell wrapper in scripts/jojo.sh. Do not use sessions_spawn or ACP for routine Jojo commands.
This skill turns a Roborock vacuum into a conversational device companion.
It is designed for:
It is not a replacement for low-level Roborock tooling. It is the higher-level layer that makes a vacuum feel like its own agent.
Use it for:
clean the kitchenclean the living areaclean the housepausego homestatuswhich rooms do you knowCreate jojo.env in this skill folder from jojo.env.example.
Minimum required value:
JOJO_DEVICE_IDOptional:
JOJO_DEVICE_NAMEROOM_ mappings such as ROOM_KITCHEN="17"Resolve the skill directory, then call:
bash <skill_dir>/scripts/jojo.sh status
bash <skill_dir>/scripts/jojo.sh start
bash <skill_dir>/scripts/jojo.sh pause
bash <skill_dir>/scripts/jojo.sh stop
bash <skill_dir>/scripts/jojo.sh home
bash <skill_dir>/scripts/jojo.sh rooms
bash <skill_dir>/scripts/jojo.sh room kitchen
bash <skill_dir>/scripts/jojo.sh room "master bedroom"
status, what are you doing, battery, where are you -> statusclean the house, start cleaning, go clean -> startpause, wait, hold on -> pausestop cleaning -> stopgo home, dock, charge, return to dock -> homewhich rooms, what rooms, rooms -> roomsclean the -> room "" If room intent is ambiguous, ask one short follow-up.
The wrapper supports user-defined aliases through env vars:
ROOM_KITCHEN="17"
ROOM_MASTER_BEDROOM="19"
ROOM_LIVING_AREA="21"
To bootstrap aliases from the live Roborock map:
bash <skill_dir>/scripts/refresh_room_aliases.sh
robo-rock or the raw roborock CLI when you only want direct device control.jojo-bot when you want a conversational robot companion with room aliases, short replies, and a dedicated device identity.python-roborock builds use roborock login --email ...app_start, app_pause, app_stop, app_charge, and app_segment_clean共 1 个版本