Roborock Vacuum

此變更新增了對兩種新的 Roborock 吸塵器型號的支援：roborock.vacuum.a140 和 roborock.vacuum.ss07。 --- *PR created automatically by Jules for task 748787851069192169 started by @tasict*

Excerpt saved from GitHub on 2026-10-22.

Problem Newer Roborock models that use the L01 local transport (AES‑256‑GCM behind a protocol‑0 HELLO handshake on TCP `58867`) never actually establish a local connection. The socket connects, but every local RPC times out with `Local connect state: true` and the plugin falls back to cloud for everything: [code] Reported in #45 (Saros 10 / `a147`) and #31 (Q7 Max), among others. Root cause The L01 handshake added in `6d50ebf5` builds a malformed HELLO frame. `ensureL01Handshake()` calls `buildRoborockMessage(duid, 1, …)`, which emits a frame that includes a `payloadLen` field and a CRC (23 …

Excerpt saved from GitHub on 2026-10-22.

此變更新增了對兩種新的 Roborock 吸塵器型號的支援：roborock.vacuum.a140 和 roborock.vacuum.ss07。 --- *PR created automatically by Jules for task 748787851069192169 started by @tasict*

Excerpt saved from GitHub on 2026-10-22.

Problem On newer models like the Roborock Qrevo (`roborock.vacuum.a185`), the device accepts the local TCP connection but never answers the local control protocol, so every local request times out (10s each). The existing fallback only switches to the cloud/MQTT path when the local socket is *disconnected*, but here it stays "connected yet mute", so it never falls back and remains on the dead local path. Cloud/MQTT works fine for these models. Root cause `messageQueueHandler.sendRequest` only sets `useCloudConnection` on `!localConnectionState`, and `localConnector.isConnected()` returns the …

Excerpt saved from GitHub on 2026-10-22.

Issue #36 reports model `roborock.vacuum.a159` as unsupported, but investigation confirms full support exists in codebase since initial commit. Current State Model a159 is configured in `roborockLib/lib/deviceFeatures.js`: 14 feature actions in `modelConfig` (lines 1016-1031) Included in 4 feature support arrays (isMopForbiddenSupported, isShakeMopStrengthSupported, isWaterBoxSupported, isAvoidCarpetSupported) Listed in README.md as supported Root Cause Published npm version is 1.3.2; current code is 1.3.5. User experiencing issue is on older published version. Resolution No code changes …

Excerpt saved from GitHub on 2026-10-22.

Thanks for reporting this. I added support for `roborock.vacuum.a147` (Saros 10) so it is no longer treated as an unsupported model. I also fixed the minimum-data refresh path for this model to make sure the related settings are actually queried and updated, including: carpet mode carpet clean mode water box custom mode So this should address both the unsupported-model warning and the stale/missing state updates for Saros 10. If you still have problems after updating, please attach your Homebridge log in debug mode so I can check whether there are any additional model-specific issues.

Excerpt saved from GitHub on 2026-10-22.

I am using this plugin now for a few weeks and yes, routines and schedules show up once you connect the plugin via the provided HomeKit child bridge to your home. Routines then can be put in any automations like vacuuming once you leave your house. The switches for schedules turn them on or off in case you want to deactivate them for some time. Thee plugin also provides optional switches and sensors. For example I am using the “is cleaning” sensor m the floor so the robot won’t drive into them.

Excerpt saved from Arctic Shift Reddit archive on 2026-10-22.

Hi 👋 first of all, thank you for your great work on this plugin! I’ve been using Homebridge for a while and just got a new Roborock Q10 S5 (roborock.vacuum.ss07). I set up everything correctly with my Roborock credentials in the plugin, but unfortunately, the device does not appear in Homebridge. ⸻ 🧩 Details: • Region: DE / EU • Roborock App used (Mi Home not compatible) • Model: Roborock Q10 S5 • Released: 2025 • Firmware: 03.10.19 ⸻ 🧾 What happens When Homebridge starts, the logs end with: [RoborockVacuum] Discovering vacuum devices No further entries are shown, no “device found” or …

Excerpt saved from GitHub on 2026-10-22.

Hi there, I've got the Costo QX Revo Plus, any chance of adding this model? I would greatly appreciate it.

Excerpt saved from GitHub on 2026-10-22.