homebridge-roborock-matter 3.4.3 → 3.4.4

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 3.4.4
+
+- **Nine Saros 10 status fields are now mapped.** 3.4.3 started naming unknown `get_status` fields once instead of once a minute, and asked owners to paste that line into a model report. skmzwanke did exactly that for his `roborock.vacuum.a144` ([#8](https://github.com/mathiashornbek/homebridge-roborock-matter/issues/8)), so `home_sec_status`, `voice_chat_status`, `home_sec_enable_password`, `extra_time`, `sterilize_status`, `rst`, `cleaning_info`, `exit_dock` and `seq_type` are known from now on and his log is quiet. None of them drive behaviour — control, battery, rooms and state come from a model-agnostic path — so this is purely about not pestering the owner of a new model about fields the plugin had simply never met.
+
 ## 3.4.3
 
 **A robot with no model profile no longer fills your log with the same request forever.** Models the plugin has no dedicated profile for — the Saros 10 in [#8](https://github.com/mathiashornbek/homebridge-roborock-matter/issues/8), the Qrevo CurvX in [#6](https://github.com/mathiashornbek/homebridge-roborock-matter/issues/6) — run on the capability-derived path, which works, but every status field the profile did not name produced its own `Unsupported attribute … Please contact the dev` warning on every status poll. For the Saros 10 that is eight warnings a minute: about 11,500 requests a day to report the same eight fields. Both issues were promised this would be quietened.

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. 378 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. 419 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
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "homebridge-roborock-matter",
-  "version": "3.4.3",
+  "version": "3.4.4",
   "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/lib/deviceFeatures.js

@@ -153,6 +153,27 @@ const deviceStates = {
   rdt: "number",
   camera_status: "number",
   distance_off: "number",
+  // Reported by the Saros 10 (roborock.vacuum.a144) and siblings. Added from
+  // skmzwanke's field report in issue #8, which is exactly the round trip the
+  // "no mapping for" log line asks for: 3.4.3 named the nine fields once, he
+  // pasted the line, and they are now known.
+  //
+  // None of them drive behaviour — control, battery, rooms and state come
+  // from a model-agnostic path — so mapping them is about not pestering the
+  // owner of a brand-new model about fields the plugin simply had not met
+  // yet.
+  home_sec_status: "number",
+  home_sec_enable_password: "number",
+  voice_chat_status: "number",
+  sterilize_status: "number",
+  exit_dock: "number",
+  extra_time: "number",
+  seq_type: "number",
+  rst: "number",
+  // An object: {target_segment_id, segment_id, fan_power, water_box_mode, ...}
+  // — the same convention as adbumper_status and events, which are also
+  // non-scalar.
+  cleaning_info: "string",
 };
 
 // Shared shape for the work-time consumables that both consumablesInt and