@homebridge-plugins/homebridge-eufy-security 5.0.0-beta.1 → 5.0.0-beta.2
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/README.md +4 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -19,8 +19,8 @@
|
|
|
19
19
|
|
|
20
20
|
> [!IMPORTANT]
|
|
21
21
|
> **V5 is a beta and not yet a replacement for the stable V4 plugin.** Every capability area is
|
|
22
|
-
> implemented, covered by the contract suite, and exercised against a real device fleet.
|
|
23
|
-
>
|
|
22
|
+
> implemented, covered by the contract suite, and exercised against a real device fleet. It is published
|
|
23
|
+
> on the `beta` dist-tag while that fleet keeps reporting; 4.x stays on `latest`.
|
|
24
24
|
>
|
|
25
25
|
> **V5 does not adopt V4 HomeKit accessories.** It registers its own, so expect to remove the V4
|
|
26
26
|
> accessories and reassign rooms, names, and automations once. A V4 configuration block is not loaded
|
|
@@ -91,13 +91,11 @@ temporary authentication flow, and the runtime never falls back to interactive l
|
|
|
91
91
|
| Battery, charging, and low-battery enrichment | Implemented |
|
|
92
92
|
| Guided diagnostics and redacted support archives | Implemented |
|
|
93
93
|
| Continuous validation against a real device fleet | Ongoing |
|
|
94
|
-
| Qualification of an immutable pilot artifact, then public beta approval | Remaining |
|
|
95
94
|
|
|
96
95
|
Support is capability-led rather than model-led, so capability evidence decides coverage instead of product
|
|
97
96
|
naming, and a newly recognized model that exposes an already-adapted capability works without an allowlist.
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
without, an explicit HomeKit adapter for their primary purpose.
|
|
97
|
+
Most rows in the coverage matrix are diagnostic-only rather than adapted, so a recognized device appears in
|
|
98
|
+
the dashboard before, or without, an explicit HomeKit adapter for its primary purpose.
|
|
101
99
|
|
|
102
100
|
Device behaviour is grounded in measurement rather than inference: [`docs/architecture.md`](./docs/architecture.md)
|
|
103
101
|
records the observed timings and outcomes behind the live, recording, and control decisions, and
|
package/package.json
CHANGED