homebridge-roborock-matter 3.12.3 → 3.12.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +12 -0
- package/README.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.12.4
|
|
4
|
+
|
|
5
|
+
**A correction. For one release this README said the opposite of the truth about how your robots reach Apple Home.**
|
|
6
|
+
|
|
7
|
+
3.12.3 rewrote the paragraph on Matter fault reporting around 2 beliefs: that Homebridge puts every Matter accessory on 1 shared node, and that the field tests which found Apple Home drawing no vacuum faults had therefore been run on a bridge. Both are wrong, and the evidence was in the maintainer's own log the whole time.
|
|
8
|
+
|
|
9
|
+
Homebridge has never bridged a robot vacuum. Its Matter layer keeps a list of device types that must be published on a dedicated Matter server of their own, and `RoboticVacuumCleaner` has been on that list since the first Matter commit landed on 23 February 2026 — before any released Homebridge could speak Matter at all. Every robot gets its own server, its own port and its own pairing code. On the maintainer's host that is ports 5532, 5533 and 5534 and 3 distinct bridge identifiers, printed in the Homebridge log at every startup.
|
|
10
|
+
|
|
11
|
+
So the sentence 3.12.3 deleted was correct and the one it added was not. "Bridged versus not" cannot explain why Apple Home drew nothing in those 3 controlled tests and drew the tap icon on this maintainer's own tile on 20 August, because every one of those measurements was taken on a standalone node. The condition is still unknown, and the README says so again.
|
|
12
|
+
|
|
13
|
+
The wrong version was live for 17 minutes. Nothing in the plugin changed in this release; the code shipped by 3.12.3 is untouched.
|
|
14
|
+
|
|
3
15
|
## 3.12.3
|
|
4
16
|
|
|
5
17
|
**A robot asked to mop said it was vacuuming — for the 40 seconds it spent driving home.**
|
package/README.md
CHANGED
|
@@ -139,7 +139,7 @@ Everything is configurable from the Homebridge UI. The essentials:
|
|
|
139
139
|
|
|
140
140
|
By default a robot that has stopped for any reason shows as **Ready** in Apple Home — whether it finished the job or is wedged under the sofa. Since 3.12.0 it does not: a robot that is stuck, has a blocked brush or wheel, a missing dust bin, a flat battery or a dock it cannot reach reports the Matter **Error** state instead of Ready. The cost of that is real — a robot in Error may be refused a Start command by Apple Home — but that is the correct answer for a robot which cannot run, and the old silence is a `enableMatterFaultReporting: false` in `config.json` away.
|
|
141
141
|
|
|
142
|
-
**Dock and tank conditions are not reported through Matter, and this is worth explaining.** The plugin can read them all accurately — empty clean-water tank, full waste-water tank, missing dust bag, blocked air duct — and two releases tried to surface them through Matter's fault attribute (`OperationalError`). 3 controlled tests on an S8 Pro Ultra with a genuinely empty clean-water tank showed it does not work: Apple Home drew no warning when the fault was published beside a Charging state, and drew no warning in the final test either, where the robot was raised all the way to the Matter **Error** state carrying "Clean water tank empty" — the tile simply kept reading Ready. **Apple Home drew nothing in any of those tests** — which is also why an earlier version removed the same write back in 1.4.61. The condition under which it _does_ draw one
|
|
142
|
+
**Dock and tank conditions are not reported through Matter, and this is worth explaining.** The plugin can read them all accurately — empty clean-water tank, full waste-water tank, missing dust bag, blocked air duct — and two releases tried to surface them through Matter's fault attribute (`OperationalError`). 3 controlled tests on an S8 Pro Ultra with a genuinely empty clean-water tank showed it does not work: Apple Home drew no warning when the fault was published beside a Charging state, and drew no warning in the final test either, where the robot was raised all the way to the Matter **Error** state carrying "Clean water tank empty" — the tile simply kept reading Ready. **Apple Home drew nothing in any of those tests** — which is also why an earlier version removed the same write back in 1.4.61. The condition under which it _does_ draw one is still not known, and it is **not** "bridged versus not" — Homebridge has never bridged a robot vacuum. Its Matter layer keeps a list of device types that must be published on a dedicated Matter server of their own, `RoboticVacuumCleaner` has been on that list since the first Matter commit, and on this maintainer's host the 3 robots run as 3 separate Matter servers on ports 5532, 5533 and 5534, with 3 pairing codes and no aggregator between them. Reporting the rest was therefore pure cost, and those attributes are not published.
|
|
143
143
|
|
|
144
144
|
**The empty clean-water tank is now the exception, and 3.12.0 publishes it.** A counterexample arrived in [#9](https://github.com/mathiashornbek/homebridge-roborock-matter/issues/9) after those tests: another bridge showing Apple Home a `WaterTankEmpty` fault, rendered properly, with a tap icon on the play button and a translated string. So "Apple never draws these" is too strong. The plugin now publishes Matter's `WaterTankEmpty` when the robot reports no clean water, and clears it when the tank is refilled. The robot is **not** forced into the Error state along with it — Wazza151's third test did exactly that and Apple still drew nothing, so it buys nothing measured and would cost a docked robot its Start command. No re-pairing is needed for this one: an error attribute is a live value, not a capability.
|
|
145
145
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "homebridge-roborock-matter",
|
|
3
|
-
"version": "3.12.
|
|
3
|
+
"version": "3.12.4",
|
|
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.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": {
|