Roborock & Home Assistant
The core Roborock integration controls the current Roborock line (S, Q, Qrevo, and Saros series) from Home Assistant. It prefers local communication on the LAN (port 58867, roughly 30-second polling) for start and stop, return-to-base, fan speed, and per-room cleaning, which keeps it fast and responsive day to day.
It is not cloud-independent, though. Setup requires a Roborock account, maps and routines come from Roborock’s cloud, and when the robot loses internet it blocks its own local API until it can reach Roborock’s servers again. It is the best-supported path for current hardware, but for a fully offline build, root a supported robot and run Valetudo instead.
HA DocumentationHow Roborock Works with Home Assistant
Getting Roborock connected to Home Assistant and running reliably.
Sign in with a Roborock account
The integration authenticates through your Roborock app credentials, discovers the robots on the account, and then prefers local control on the LAN.
Control locally, map from the cloud
Start and stop, return-to-base, and fan speed run over the local API on port 58867 with about 30-second polling, while maps and saved routines are fetched from Roborock's cloud.
Map rooms and automate
Once segments are matched to Home Assistant areas, per-room cleaning and clean-when-away or after-dinner automations work, with the caveat that the robot needs its cloud reachable to stay controllable.
Common Roborock Issues
The problems installers run into with Roborock and Home Assistant — and how a managed setup prevents them.
A Roborock account is required
The integration authenticates through your Roborock app credentials, so a cloud account is mandatory even though most control is local afterward.
Blocks its local API when offline
If the robot cannot reach Roborock's servers it stops answering on its local API until connectivity returns, so fully air-gapping it on an IoT VLAN breaks control.
Maps and routines live in the cloud
Floor plans and saved routines are stored and served by Roborock, not locally, and the integration polls every ~30 seconds rather than the app's ~2-second rate.
Newer Q-series variants can fail to connect
Compatibility varies across the fast-moving lineup; some newer variants have trouble with local connections until firmware and the integration catch up.
Why installers choose managed Roborock setups
- Account and local-control setup handled, with credentials kept current
- Segments mapped to Home Assistant areas for reliable per-room cleaning
- Cloud-dependency limits documented so automations degrade predictably
- Privacy-critical sites steered to Valetudo-rootable hardware instead
Roborock devices we deploy
Hardware from the Selora catalog that runs on this integration. Every unit is tested and supported as part of a managed installation.
Robot Vacuums
3 devicesQrevo Curv
A current Roborock flagship with a dual anti-tangle system and AdaptiLift chassis. The core Roborock integration gives fast local control on the LAN, but it needs a Roborock account and leans on the cloud for maps and when offline.
S8 MaxV Ultra
The prior-generation Roborock flagship with PreciSense LiDAR and the RockDock Ultra. The core Roborock integration gives local control on the LAN, with the same Roborock-account and cloud-map caveats as the current line.
Saros 10R
Roborock's current ultra-slim flagship. The core Roborock integration gives fast local control on the LAN, though it needs a Roborock account to set up and pulls maps from the cloud. Day-to-day commands and polling stay on the network.
Frequently Asked Questions
Ready to Install Roborock Professionally?
Stop troubleshooting Roborock integration issues. Let Selora handle the setup, monitoring, and maintenance so you can focus on your clients.