roborock-bridge

This service connects to RR's servers and provides status information from your robot to your mqtt broker. It can also send simple commands and requests to the robot.

Setup & Start

To start experimenting you can start the application with docker compose. If you want to use the application for real you'll have to start it the regular way.

Quickstart with docker compose

To get started quick you can use docker compose. This will start:

• the bridge itself
• an mqtt broker
• the web ui

Create an env file that contains

USERNAME=<email>
PASSWORD=<password>

Start up everything with

docker compose --env-file <your-env-file> up

Now open up a browser and navigate to http://localhost:8080.

The regular way

You need at least Java 17 to run the application.

Create an application.yaml file with the following content. Replace username, password and bridge-mqtt.url, etc. (don't change the app_secret_salt).

username: user   # your roborock account username (email address)
password: secret # your roborock account password
roborock-mqtt:
  nonce_generation_salt: ThisIsASecret # just a random string for entropy
  endpoint: aAbBz0                     # 6 char string to use as an identifier
bridge-mqtt:
  url: tcp://localhost:1883            # connection url to your mqtt broker (use ssl:// for ssl)
  # If you don't use anonymous access to the broker, also set these
  # username: username
  # password: secret
  client_id: mqtt-bridge-service       # how the client appears to your broker
  base_topic: mqtt-bridge              # everything th service does will be below this topic string

Start the application with:

java -jar file.jar

How to use

What you'll get:

topic	description
home/<homeId>	All devices and routines are associated to a room. This topic contains the home name and the id.
home/<homeId>/rooms	Homes have rooms. This topic contains a list of the defined rooms.
home/<homeId>/routine/<routineId>	Routines are predefined cleanup tasks (i.e. first vacuum, the mop room A). Routines can be executed with /action.
home/<homeId>/device/<deviceId>	This topic contains basic information of the device and is the parent various property topics.
home/<homeId>/device/<deviceId>/<property>	Topics associated with properties of the device. e.g. current state, remaining battery charge, map data, ...
home/<homeId>/device/<deviceId>/<property>/options	Send an empty body to this topic to get a list of possible values for the property

List of some of the available properties:

• map
• path
• virtual_walls
• robot_position
• charger_position
• state
• battery
• ...

Commands

Commands are topics which will invoke certain functionality on the bridge. Each command is a prefix that immediately follows the path to the resource the command should be invoked upon.

Example: If you with to perform a get command on a home node, you would publish a message on topic <base-topic>/home/12345/get

Currently available commands:

postfix	description
/get	request data from remote servers
/action	invoke action (e.g. return to dock, start cleanup routine)

What can you request with get?

target	body	description
home	empty	update home and devices via rest (some device states not included) Example: <base-topic>/home/12345/get
device	state	request update of all states via mqtt Example: <base-topic>/home/12345/device/asjnkd978732/get with body state
device	map	request update of map data via mqtt Example: <base-topic>/home/12345/device/asjnkd978732/get with body map

What can you do with actions?

target	body	description
routine	empty	Start the cleanup routine Example: <base-topic>/home/12345/routine/34544/action
device	home	Send device back to base station Example: <base-topic>/home/12345/device/asjnkd978732/action with payload home
device	{"action": "segments", "clean_mop": int?, "clean_order_mode": int?, "repeat": int?, "segments": int[]}	Clean selected segments / rooms. Possible values are the mqttRoomIds for segments and 0 or 1 for the other values (to be verified) Example: <base-topic>/home/12345/device/asjnkd978732/action with payload {"action": "segments", "segments": [18,19,20]}
device	{"action": "clean_mode", "fan_power": int,"mop_mode": int, "water_box_mode": int}	Set cleanup options. Possible property values can be found in the Interpreter for your robot e.g. S8 Pro Ultra, MOP_MODE_UNKNOWN, FAN_POWER_123, WATER_BOX_124. Example: <base-topic>/home/12345/device/asjnkd978732/action with payload {"action": "clean_mode", "fan_power": 103,"mop_mode": 300, "water_box_mode": 202}
device	{"action": "clean_mode", "fan_power": string,"mop_mode": string, "water_box_mode": string}	Set cleanup options via string values (see next section to find out allowed values). Example: <base-topic>/home/12345/device/asjnkd978732/action with payload {"action": "clean_mode", "fan_power": "max","mop_mode": "deep", "water_box_mode": "off"}
device	start or {"action": "start", "clean_mop": 1}	Start / Resume current cleanup task. Example: <base-topic>/home/12345/device/asjnkd978732/action with payload start
device	pause	Pause current cleanup task. Example: <base-topic>/home/12345/device/asjnkd978732/action with payload pause

What values are allowed for which property

If you want to know which values are allowed for which property you can ask the bridge for it. Send a message to home/<homeId>/device/<deviceId>/<property>/options with an empty body (important). The bridge will reply on the same topic with a map of values and their meaning. If there is no interpreter for your device available or the interpreter has no information about possible values it won't reply.

Example: <base-topic>/home/12345/device/asjnkd978732/fan_power/options

Something is wrong

Try resetting the authentication by deleting the auth.json file.

Short excursion on RR's APIs (completely optional read)

Sadly RR does not provide a public interface (i.e. APIs) for developers to create their own solutions. Some people smarter than me started to decompile RR's apps and reverse engineered a lot of the protocol. Today, with a little help by a couple of extracted secrets and a bit of mitm traffic sniffing, we can see what the official app does and recreate some of it.

A few things you should know about the communication between the app and roborock servers (even if it's only to understand some of the errors this application might produce) are:

• There are a couple of REST APIs that are used for
  • Authentication (login api), is where you log in and get a set of credentials for other operations
  • Home (home api), is where you get information about a home, which is the root node where everything else is assigned to
  • Interaction with devices (user api), requests available devices and their status, also allows starting predefined cleanups
• There also is an MQTT connection. This is used for
  • IPC request/responses. Used for live updates of the robot status (e.g. idle/cleaning/drying/charging)
  • There are also "special" IPC requests that request the map of your place as seen by the robot

This application hides all the different ways of communication and provides a single way of communication with your device via mqtt. IF you already have a mqtt broker running for things like zigbee2mqtt, this service should be right up your alley. However, if you have never heard of mqtt, and you have no idea what it is, you may want to continue RR's app.

Todo-List

Status	What
✅	Use request memory to determine avg request to response time
✅	Create "idle mode"
✅	Disconnect roborock mqtt when idle, reconnect on activity
❌	Detect routine finished to send bridge into idle mode
✅	poll frequent updates during active phase
✅️	Room cleaning
✅	Set Cleanup modes
✅	Verify room cleaning parameters
✅	Pause & Resume (e.g. to pause when certain area is entered)
📝	Verify Pause & Resume
✅	Detect Device MQTT unreachable and stop polling
✅	Fix POC ui after renaming room property names
✅	Add room cleaning parameters to POC ui
📝	Find out how to get status of dock (probably not much to do)
📝	Allow resetting consumables (set on properties)
📝	Start / Stop drying at base
📝	trigger mop cleanup?
✅	create way to ask about possible prop values and meaning
📝	Selected area cleaning (via mqtt? tricky!)

Help reverse engineering the protocol

Instructions on breaking and entering the protocol

I only own an S8 Ultra, and I have no idea how the protocol varies between models. Theoretically you should be able to use this service for other robots as well, if not, you can help by adding the functionality for it.

Most likely you will have to create a SchemaValueInterpreter for your robot, which should be a simple copy & paste & adapt (you might even find the data you need in some other services that do something similar). In case the application doesn't work at all for you, bigger changes might be necessary. You can help by figuring out what these changes are on the protocol level by following the instruction behind the link above.

Feel free to

• open a pull request for
  • compatibility patches
  • bugfixes
  • new features / improvements
• report issues

Other ways to support

If you have no idea how to code, but really want to use this application, you can sponsor me an additional roborock robot or lend me yours for a while. The actual extraction of what I need shouldn't take long. I cannot give any guarantees to how long it might take to make the required adjustments to the application. Contact me if interested.