- Changes
- 2
- Tracking since
- Sep 2023
- Latest
- Feb 18, 2025
- Net movement
- Classification stable
- 2025
-
Home Assistant community ships local-only S5 integration bypassing cloud
Local-network control of the S5 via Home Assistant's Roborock integration has been a long-standing capability predating 2025.
Full assessment
AutonomyL3 capabilities expandedReadinessNot Recommended unchangedScoreScores unchangedScheduling, zone cleaning, and map retrieval operate entirely on-device for owners who configure it, eliminating the cloud-account migration risk documented in 2023. A subsequent integration update improved token retrieval automation and map parsing reliability for the S5's firmware-level map format. The watch item is whether Roborock firmware updates for successor models inadvertently break the LAN protocol the S5 relies on, since the S5 receives no active firmware updates of its own.
Impact on autonomy
- Local scheduling restores autonomous runs independent of cloud account status
- Zone and room-targeted cleaning accessible without Roborock app cloud session
- Map data retrieval now available via LAN; no cloud authentication required for map access
Impact on readiness
- Cloud-dependency risk eliminated for owners who configure local integration
- Setup complexity increased: Home Assistant configuration requires technical capability beyond typical owner profile
- Functional lifespan extended for the existing installed base; does not affect new-buyer assessment
Claim check3 claims reviewed
Roborock cloud integration provides reliable schedulingCloud routing remained a single point of failure; local integration removes this dependency for configured ownersS5 is a discontinued product with no ongoing developmentThird-party community development continues to extend capability; LAN protocol reverse-engineered and documentedHome Assistant integration is plug-and-playConfiguration requires manual token extraction and network-level setup; not suitable for non-technical ownersBottom lineFor technically capable owners, local control converts a cloud-dependent discontinued robot into a network-autonomous device; for typical owners, the setup barrier is not cleared by the reliability gain.
Technical notes4 sections
- Integration Architecture
-
The Home Assistant Roborock integration uses the documented LAN protocol to send commands and retrieve status directly from the S5 on the local network. This LAN control path has been available for several years and predates 2025. The integration improvement automated token retrieval and improved map parsing reliability for the S5’s specific firmware-level map format; it refined an established capability rather than introducing a new one.
- Capabilities Enabled Locally
-
Start, stop, pause, dock, zone-clean, and room-targeted-clean commands all route via LAN. Real-time status (battery, mode, error codes) is polled locally. Map retrieval and no-go zone configuration still require at least one initial cloud session for map initialization; subsequent access is local.
- Limitations
-
Firmware-level changes by Roborock on successor models sometimes update shared LAN protocol elements. Because the S5 receives no firmware updates, it cannot respond to protocol changes that break older command formats. Community maintainers have historically patched integration-side within weeks of protocol shifts, but there is no manufacturer commitment to protocol compatibility.
- Owner Profile
-
Owner reports across Home Assistant community forums indicate the integration is used primarily by owners who have S5 units functioning well and want to remove the cloud dependency following the 2023 account migration event.
SourcesHome Assistant Community Forums 2025-02-14GitHub home-assistant/core Roborock integration changelog 2025-02-17 - 2023
-
Roborock app backend migration drops legacy S5 account support
Roborock's cloud account system migration severed remote scheduling and voice-assistant commands for S5 units still linked to older Mi Home credentials.
Full assessment
AutonomyL3 unchangedReadinessPromising progress strengthenedScoreScores unchangedOwners who did not migrate accounts in time lost remote access until re-pairing under the updated Roborock app. The watch item: whether further backend deprecations will sever local LAN control, which currently keeps the S5 functional without cloud dependency.
Impact on autonomy
- Scheduled autonomous runs require cloud link; local manual start unaffected
- Voice-assistant integrations (Alexa, Google Home) broke for non-migrated accounts
- Map storage and no-go zones remained intact after account re-pair
Impact on readiness
- Remote scheduling unavailable for owners who did not complete account migration
- Re-pairing process documented as 15-30 minutes; required app update to current Roborock version
- Owners relying on voice control faced multi-step re-setup before restoration
Claim check3 claims reviewed
Cloud connectivity enables seamless remote controlAccount migration severed remote access for a subset of S5 owners; re-pair requiredApp updates improve experience over timeApp update that enabled migration also dropped support for older login paths; not backward-compatibleLiDAR mapping persists across updatesOwner reports confirm map data survived migration after re-pair; no map data loss documentedBottom lineCloud dependency introduced a setup burden for a robot marketed on autonomous scheduling; local LAN control remains the functional fallback for affected owners.
Technical notes3 sections
- Account Migration Scope
-
Roborock consolidated its device authentication away from the shared Mi Home (Xiaomi) account system onto its own platform. S5 units originally paired via Mi Home required manual re-registration in the standalone Roborock app. Units already on the Roborock app were migrated automatically or with a prompted confirmation step.
- Feature Impact
-
Remote scheduling, real-time status, and third-party integrations (Alexa, Google Home, IFTTT) all route through Roborock’s cloud layer. Owners who did not complete migration lost these features until re-pair. Local LAN commands remained available for users with home-assistant integrations (Home Assistant, Valetudo) that bypass cloud routing entirely.
- Firmware Version Context
-
No new firmware was pushed with this migration. The change was server-side and affected authentication, not robot capability. S5 firmware version series remained on its existing branch throughout.