Debug logging
Debug logging shows each poll, and why a map was or was not downloaded. Add this toconfiguration.yaml and restart:
configuration.yaml
Diagnostics
The diagnostics download on the integration’s device holds the last map, both as downloaded and as parsed, with the credentials, token, address and MAC removed.- For a vacuum on the Xiaomi map API it also holds the last value read from each MIoT property.
- For the Xiaomi Robot Vacuum S20+ it holds the last trajectory downloaded, with the account and device IDs taken out of object names.
Common problems
Signing in fails
Signing in fails
Sign in with the Xiaomi account the Xiaomi Home app uses. A Roborock or Dreame app account is a different account, and Xiaomi’s cloud does not know it.
The map is empty
The map is empty
Is map empty turns on when the last map came back with nothing in it. Check that the vacuum shows a map in the Xiaomi Home app, press Force map update, and turn on debug logging to see what the cloud returned.
The map looks blocky or the path looks thin
The map looks blocky or the path looks thin
The entry may predate 0.8.0 and still draw at a scale of 1. Raise Image dimensions → Scale, and Map elements’ sizes by the same factor. See Scale.