homebridge-roborock-matter 3.26.0 → 3.27.0

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## 3.27.0
+
+**The scene resource named its one write verb, and it is the one that deletes. So the search moves off that resource and onto its siblings — asked safely, and this time with controls, so the round either finds the route or proves there is nothing left to find.**
+
+3.26.0 asked `user/scene/<id>` which methods it accepts. Issue #22's reporter ran it and the answer came back on the first try:
+
+```
+OPTIONS user/scene/<id> → "" — the resource allows: DELETE,OPTIONS
+```
+
+That is an answer, and not one of the two the thread had planned for. The plan said an `Allow` naming a write verb means the next step is a promised no-op, and a missing `Allow` means we are near the end of what can be measured from outside. What arrived names exactly one method that changes anything, and it removes a schedule rather than toggling one. There is no write there to put behind a HomeKit switch, and a destructive verb is not something to try against someone's live account to see what happens.
+
+**What that rules out is the resource, not the feature.** The plugin's own scene-run path reaches `user/scene/<id>/execute`, so sub-resources under a scene id exist and carry verbs the scene itself does not. This release asks the same safe question of the routes that are left:
+
+- `user/scene` — the collection, where a REST API most often keeps an update
+- `user/scene/<id>/enable` — the literal candidate for the nested `TIMER` flag the reporter's app flips
+
+**And of two controls, which is the part that makes the answers mean anything.** An `Allow` header on its own is not evidence:
+
+- `user/scene/device/<duid>` — a **positive** control. This same probe run already read it successfully, so it is mapped beyond doubt. If `OPTIONS` cannot describe even that, the instrument does not see routes and no other answer in the set is worth reading. It is also why the control is this route and not `/execute`: a control must not be a path whose real verb starts a robot.
+- `user/scene/<id>/no-such-subresource-control` — a **negative** control. If a path with nothing behind it also answers with an `Allow` header, the server answers everything and every positive here is an artefact.
+
+Together they bound the search instead of extending it: this round either names a route or shows that no later round would.
+
+Everything that made the probe safe to ship is unchanged and still bound by tests — silent unless debug logging is on, safe methods only, once per robot per session, cannot throw into the poll it rides on, and only the `Allow` header is taken from a response rather than the header block, which carries session material. A source guard now also pins the two properties that would otherwise fail invisibly: every candidate is narrowed to a safe method at one point, and the negative control cannot be dropped.
+
 ## 3.26.0
 
 **The refused route answered, and what it said was that the route exists — just not for the verb we asked with. So this release asks it which verb it does take, without attempting one.**

package/README.md

@@ -37,7 +37,7 @@ This is the most feature-packed, most thoroughly engineered Roborock plugin for
 - 📍 **See where it's cleaning — live.** Apple Home shows _"Cleaning — Kitchen"_ with the room the robot is actually inside, updating as it moves from room to room. Works even for cleans started from the robot's button or the Roborock app. No other Homebridge plugin does this.
 - 🧭 **One robot, one tile — and as many robots as you own.** Sign in once and your whole fleet comes along: every vacuum on your account appears as its own clean, native accessory in Apple Home. No clutter of fake fans and helper switches, and rooms appear with the names you gave them in the Roborock app.
 - ⚡ **Fast and reliable.** Commands go directly to the robot over your own network whenever possible, with the Roborock cloud as automatic backup — and built-in diagnostics in the settings if you ever want to look under the hood.
-- 🛡️ **Verified by Homebridge.** Reviewed and endorsed by the Homebridge team. 1854 automated tests, zero known vulnerabilities, no analytics, and a startup designed to never crash your Homebridge — even when your Wi-Fi or the Roborock cloud has a bad day.
+- 🛡️ **Verified by Homebridge.** Reviewed and endorsed by the Homebridge team. 1862 automated tests, zero known vulnerabilities, no analytics, and a startup designed to never crash your Homebridge — even when your Wi-Fi or the Roborock cloud has a bad day.
 
 ## Features
 
@@ -258,7 +258,7 @@ The complete path — robot → plugin → Homebridge → matter.js store — wa
 
 ## Contributing
 
-Model reports, diagnostics exports, and pull requests are very welcome. The codebase ships with 1854 tests (protocol fixtures verified against the [python-roborock](https://github.com/Python-roborock/python-roborock) reference), strict TypeScript checking, and CI across Node 22/24 × Homebridge 1.11/2.x — `npm test` before you push and you're set.
+Model reports, diagnostics exports, and pull requests are very welcome. The codebase ships with 1862 tests (protocol fixtures verified against the [python-roborock](https://github.com/Python-roborock/python-roborock) reference), strict TypeScript checking, and CI across Node 22/24 × Homebridge 1.11/2.x — `npm test` before you push and you're set.
 
 ## Support the project
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "homebridge-roborock-matter",
-  "version": "3.26.0",
+  "version": "3.27.0",
   "description": "The most complete Roborock plugin for Apple Home. Supports the entire Roborock lineup — from the classic S-series to the new 2025 Q7 series that no other plugin can control. Sign in with your Roborock account and get native start/stop, room cleaning, suction levels, battery, and live 'cleaning in the kitchen' room tracking. Verified by Homebridge.",
   "license": "MIT",
   "author": {

package/roborockLib/roborockAPI.js

@@ -299,6 +299,15 @@ const B01_STATUS_FORCED_GAP_MS = 1500;
 const B01_STATUS_ACTIVE_GAP_MS = 12000;
 const B01_STATUS_IDLE_GAP_MS = 25000;
 
+// The last path segment of the cloud schedule probe's negative control.
+//
+// The probe asks candidate routes which methods they take. An `Allow` header
+// coming back is only evidence if a route that CANNOT exist stays silent, so
+// one deliberately unmappable path is asked the same question. It is a fixed
+// literal rather than a random string so that the same reading is reproducible
+// across restarts and legible in a log a user pastes into an issue.
+const ABSENT_ROUTE_PROBE_SEGMENT = "no-such-subresource-control";
+
 // How many keys of an arbitrary diagnostic object survive compaction.
 const DIAGNOSTIC_KEY_LIMIT = 30;
 
@@ -4845,6 +4854,62 @@ class Roborock {
         { label: "sceneMethods", path: scenePath, method: "options" },
         results
       );
+
+      // And that question was answered: the resource allows DELETE and
+      // OPTIONS. It is an answer, and not one of the two the thread's own
+      // decision rule anticipated. The singular scene resource takes exactly
+      // one method that changes anything, and it destroys a schedule rather
+      // than toggling one — so there is no write here to put behind a HomeKit
+      // switch, and a destructive verb aimed at a stranger's live account to
+      // see what happens is not a measurement this project will take.
+      //
+      // That rules out the resource, not the feature. Our own `executeScene`
+      // reaches `user/scene/{id}/execute`, so sub-resources under a scene id
+      // demonstrably exist and carry verbs the scene itself does not. Whether
+      // one of them is the toggle is the last question this instrument can
+      // ask, and it is asked WITH CONTROLS, because on its own an `Allow`
+      // header proves nothing:
+      //
+      //   - `user/scene` — the collection, where a REST API most often keeps
+      //     an update;
+      //   - `user/scene/{id}/enable` — the literal candidate for the nested
+      //     flag the reporter's app flips;
+      //   - `user/scene/device/{duid}` — the POSITIVE control. This run has
+      //     ALREADY read it successfully, so it is mapped beyond doubt. If
+      //     OPTIONS cannot describe even that, the instrument does not see
+      //     routes and every other answer in this set is noise. It is also
+      //     why the control is this route and not `/execute`: a control must
+      //     not be a path whose real verb runs a robot.
+      //   - a path that cannot exist — the NEGATIVE control. If THAT comes
+      //     back with an Allow header, the server answers everything and no
+      //     positive here means anything.
+      //
+      // Together they bound the search rather than extend it: this round
+      // either names a route or shows that no later round would.
+      //
+      // Asking costs nothing that could alter a schedule, and that is
+      // measured rather than assumed: the OPTIONS of the scene resource came
+      // back with an EMPTY body and an Allow header, which is a servlet
+      // container answering the request itself instead of handing it to the
+      // handler behind the path.
+      for (const candidate of [
+        { label: "sceneCollectionMethods", path: "user/scene" },
+        { label: "sceneEnableMethods", path: `${scenePath}/enable` },
+        {
+          label: "mappedRouteControl",
+          path: `user/scene/device/${duid}`,
+        },
+        {
+          label: "absentRouteControl",
+          path: `${scenePath}/${ABSENT_ROUTE_PROBE_SEGMENT}`,
+        },
+      ]) {
+        await this.probeOneCloudScheduleRoute(
+          duid,
+          { ...candidate, method: "options" },
+          results
+        );
+      }
     }
 
     await this.updateRoborockDiagnostics(