@camstack/addon-provider-unifi 0.2.79 → 0.2.80

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.
Files changed (3) hide show
  1. package/dist/addon.js +500 -365
  2. package/dist/addon.mjs +500 -365
  3. package/package.json +1 -1
package/dist/addon.mjs CHANGED
@@ -1,4 +1,4 @@
1
- //#region ../types/dist/event-category-zAv7pMUz.mjs
1
+ //#region ../types/dist/event-category-CnLqLOKs.mjs
2
2
  var EventCategory = /* @__PURE__ */ function(EventCategory) {
3
3
  EventCategory["SystemBoot"] = "system.boot";
4
4
  EventCategory["SystemAddonsReady"] = "system.addons-ready";
@@ -193,6 +193,19 @@ var EventCategory = /* @__PURE__ */ function(EventCategory) {
193
193
  EventCategory["ProcessCrashed"] = "process.crashed";
194
194
  EventCategory["ProcessRestartScheduled"] = "process.restart_scheduled";
195
195
  EventCategory["ProcessRestarted"] = "process.restarted";
196
+ /**
197
+ * The SET of storage locations changed — one was created, edited, enabled,
198
+ * disabled or deleted through `storage.upsertLocation` / `deleteLocation`.
199
+ *
200
+ * Telemetry, not a transaction (D8/D11): every consumer that re-resolves on
201
+ * it must also converge on its own periodic path, because a dropped event
202
+ * must not leave a node writing to yesterday's disk set forever. It exists
203
+ * because there was NO signal at all — an operator who added a second
204
+ * recordings disk in the admin UI got nothing, and the recorder kept its
205
+ * resolved locations until something else happened to re-resolve them
206
+ * (D387). Payload `StorageLocationsChangedPayload`.
207
+ */
208
+ EventCategory["StorageLocationsChanged"] = "storage.locations-changed";
196
209
  EventCategory["RecordingStarted"] = "recording.started";
197
210
  EventCategory["RecordingStopped"] = "recording.stopped";
198
211
  EventCategory["RecordingError"] = "recording.error";
@@ -8535,6 +8548,21 @@ var StorageCleanupJobSchema = object({
8535
8548
  });
8536
8549
  var StorageCleanupStatusInputSchema = object({ jobId: string().optional() });
8537
8550
  /**
8551
+ * The one typed state of a storage location. Authoritative Zod schema — the TS
8552
+ * alias below is `z.infer<>` of it, never a second spelling.
8553
+ */
8554
+ var StorageLocationModeSchema = _enum([
8555
+ "active",
8556
+ "readonly",
8557
+ "drain",
8558
+ "disabled"
8559
+ ]);
8560
+ _enum([
8561
+ "normal",
8562
+ "never",
8563
+ "drain"
8564
+ ]);
8565
+ /**
8538
8566
  * `StorageLocationType` — an addon-declared id that identifies the *kind* of
8539
8567
  * storage a location serves. Defined here (not in `capabilities/storage.cap.ts`)
8540
8568
  * so the persisted record schema and the consumer-facing cap can both consume it
@@ -8600,6 +8628,21 @@ var StorageLocationSchema = object({
8600
8628
  * stops existing rather than being re-derived on every read.
8601
8629
  */
8602
8630
  enabled: boolean().optional(),
8631
+ /**
8632
+ * THE state of this location (D385), and the only authority on what may be
8633
+ * written, read or evicted here. Interpreted in exactly one place —
8634
+ * `storage-location-mode.ts` — which also folds the legacy
8635
+ * `enabled` / `config.readOnly` pair into a mode so an old row is never
8636
+ * ambiguous.
8637
+ *
8638
+ * OPTIONAL only for the wire and for rows written before D385: absence is
8639
+ * resolved by `resolveLocationMode`, and the orchestrator stamps every
8640
+ * unstamped row ONCE at hydrate so absence stops existing rather than being
8641
+ * re-derived on every read. `enabled` survives one release as a DERIVED
8642
+ * mirror (`mode === 'active'`); `withLocationMode` is the only writer of
8643
+ * either, so the two cannot disagree.
8644
+ */
8645
+ mode: StorageLocationModeSchema.optional(),
8603
8646
  /** COMPUTED at read time by the orchestrator (statfs of the backing volume
8604
8647
  * for node-local locations it can reach) — never persisted, absent when the
8605
8648
  * volume is remote/unreachable. The single capacity truth every UI reads. */
@@ -8607,11 +8650,46 @@ var StorageLocationSchema = object({
8607
8650
  totalBytes: number(),
8608
8651
  availableBytes: number()
8609
8652
  }).nullable().optional(),
8653
+ /**
8654
+ * How much of that volume CamStack ITSELF holds on this location (D388) —
8655
+ * COMPUTED at read time from the `storage-occupancy` providers' own figures,
8656
+ * never persisted, never a filesystem walk.
8657
+ *
8658
+ * **ABSENT MEANS UNKNOWN, never zero.** No provider has reported for this
8659
+ * location yet — nobody stores here, the owning addon is down, or the first
8660
+ * refresh has not completed. A UI must omit the segment rather than draw it
8661
+ * at zero, which would claim we occupy nothing (D315). It is an OBJECT and
8662
+ * not a bare number precisely so that a `?? 0` on the consuming side has to
8663
+ * be spelled out loud instead of appearing by accident.
8664
+ *
8665
+ * `measuredAtMs` is the OLDEST contributing measurement, so it is honest
8666
+ * about the whole figure rather than about its freshest part.
8667
+ */
8668
+ owned: object({
8669
+ bytes: number().int().nonnegative(),
8670
+ measuredAtMs: number().int().nonnegative()
8671
+ }).optional(),
8610
8672
  createdAt: number(),
8611
8673
  updatedAt: number()
8612
8674
  });
8613
8675
  object({ isDefault: boolean().optional() });
8614
8676
  /**
8677
+ * How far a `drain` has got (D386) — the read a UI renders, and nothing more.
8678
+ *
8679
+ * `estimatedEmptyAtMs` is derived from the growth the ratchet has actually
8680
+ * OBSERVED and is `null` when it has observed none. Never a fabricated date: a
8681
+ * drain with no observed growth has no honest ETA, and inventing one is how an
8682
+ * operator learns not to believe the screen.
8683
+ */
8684
+ var StorageDrainProgressSchema = object({
8685
+ locationId: string(),
8686
+ startedAtMs: number(),
8687
+ startBytes: number(),
8688
+ bytesRemaining: number(),
8689
+ drained: boolean(),
8690
+ estimatedEmptyAtMs: number().nullable()
8691
+ });
8692
+ /**
8615
8693
  * Reference accepted by consumer-facing `api.storage.*` calls.
8616
8694
  * Either:
8617
8695
  * - a `StorageLocationType` (e.g. `'backups'`) → the sole location of that type
@@ -21940,7 +22018,7 @@ method(object({
21940
22018
  }), _void(), {
21941
22019
  kind: "mutation",
21942
22020
  auth: "admin"
21943
- }), method(object({ id: string() }), object({
22021
+ }), method(_void(), array(StorageDrainProgressSchema).readonly()), method(object({ id: string() }), object({
21944
22022
  ok: boolean(),
21945
22023
  error: string().optional()
21946
22024
  }), { auth: "admin" }), method(_void(), array(ProviderListEntrySchema).readonly()), method(object({
@@ -22010,6 +22088,51 @@ method(StorageMigrationInputSchema, StorageMigrationPlanSchema, { auth: "admin"
22010
22088
  kind: "mutation",
22011
22089
  auth: "admin"
22012
22090
  }), method(object({}), array(StorageMigrationJobSchema).readonly(), { auth: "admin" });
22091
+ /**
22092
+ * `storage-occupancy` — how many bytes an addon actually HOLDS on a storage
22093
+ * location (D388).
22094
+ *
22095
+ * ## Why this is not `storage-evictable`
22096
+ *
22097
+ * `storage-evictable.getEvictableUsage` looks like the same question and is
22098
+ * not, in two ways that both matter and both bite hardest on the locations an
22099
+ * operator most wants a figure for:
22100
+ *
22101
+ * - it reports the whole eviction DOMAIN, not the location. `recordings:default`
22102
+ * and `recordingsLow:default` deliberately share one root and evict as one
22103
+ * oldest-first pool, so both answer with the SAME combined total. As an
22104
+ * occupancy figure that double-counts the disk.
22105
+ * - it reports ZERO for a location whose eviction policy is `never` (D385) —
22106
+ * a `readonly` or `disabled` disk. Those are exactly the disks an operator
22107
+ * is retiring and staring at.
22108
+ *
22109
+ * So this is its own contract with its own quantity, and the quantity is
22110
+ * OCCUPIED: every byte the addon holds on that location, whether or not it
22111
+ * would ever be willing to delete it. A provider that can only answer
22112
+ * "evictable" must not register here — a number that silently means different
22113
+ * things per class is worse than no number.
22114
+ *
22115
+ * ## Absence is an answer
22116
+ *
22117
+ * A location nobody reports for is UNKNOWN, never zero (D315). The orchestrator
22118
+ * stamps `StorageLocation.owned` only for locations it has a report for, and
22119
+ * the field is an OBJECT rather than a bare number so that a `?? 0` on the
22120
+ * consuming side has to be written out loud instead of appearing by accident.
22121
+ *
22122
+ * `internal: true` — consumed by the orchestrator's `listLocations` stamp, never
22123
+ * a public client surface. Clients read the stamped `StorageLocation.owned`.
22124
+ */
22125
+ /** One provider's occupancy answer for one location. */
22126
+ var StorageOccupancyReportSchema = object({
22127
+ locationId: string(),
22128
+ /** Bytes this provider holds on THAT location — not its eviction domain, and
22129
+ * not net of what it is willing to delete. */
22130
+ ownedBytes: number().int().nonnegative(),
22131
+ /** When the provider last actually measured this. The orchestrator carries it
22132
+ * through so a UI can say how old the figure is instead of implying "now". */
22133
+ measuredAtMs: number().int().nonnegative()
22134
+ });
22135
+ method(object({ locationIds: array(string()).readonly() }), array(StorageOccupancyReportSchema).readonly(), { auth: "admin" });
22013
22136
  var ProviderInfoSchema = discriminatedUnion("shouldSaveDiskSpace", [object({
22014
22137
  providerId: string().min(1),
22015
22138
  displayName: string().min(1),
@@ -23845,88 +23968,6 @@ onStatusChanged: { data: object({
23845
23968
  volatileStateFields: ["lastUpdated"]
23846
23969
  };
23847
23970
  /**
23848
- * Network-link snapshot. Same shape for every provider (a Reolink wifi
23849
- * camera, a Home Assistant device with a signal-strength sensor, a Tapo
23850
- * plug): one slice under `device.runtimeState['network-link']`, one badge,
23851
- * one Home Assistant projection.
23852
- */
23853
- var NetworkLinkStatusSchema = object({
23854
- /** The link the device is on. `'unknown'` = not read yet, not "no link". */
23855
- type: _enum([
23856
- "wifi",
23857
- "ethernet",
23858
- "cellular",
23859
- "unknown"
23860
- ]),
23861
- /**
23862
- * Link quality, 0..100 inclusive, normalised by the provider from whatever
23863
- * the firmware reports (bars, RSSI, a vendor scale). **`null` means NOT
23864
- * KNOWN or NOT APPLICABLE** — a wired link has no signal, and a wireless
23865
- * one whose reading has not landed must not be drawn at 0 %. Consumers
23866
- * SKIP a null rather than coerce it.
23867
- */
23868
- signalPercent: number().min(0).max(100).nullable(),
23869
- /** Raw received signal strength in dBm, when the firmware reports one. */
23870
- rssiDbm: number().optional(),
23871
- /** Network name of a wireless link, when the firmware reports it. */
23872
- ssid: string().optional(),
23873
- /** Ms epoch of the last observation. Lets consumers reason about freshness. */
23874
- lastUpdated: number()
23875
- });
23876
- var networkLinkCapability = {
23877
- name: "network-link",
23878
- scope: "device",
23879
- deviceNative: true,
23880
- mode: "singleton",
23881
- deviceTypes: [
23882
- DeviceType.Camera,
23883
- DeviceType.Sensor,
23884
- DeviceType.Button,
23885
- DeviceType.Switch,
23886
- DeviceType.Light,
23887
- DeviceType.Lock,
23888
- DeviceType.Siren
23889
- ],
23890
- methods: {},
23891
- events: {
23892
- /**
23893
- * Emitted whenever the cached status changes (a link switch, a signal
23894
- * reading that moved). Mirrored on the parent chain by the
23895
- * DeviceEventPropagator like `battery.onStatusChanged`.
23896
- */
23897
- onStatusChanged: { data: object({
23898
- deviceId: number(),
23899
- status: NetworkLinkStatusSchema
23900
- }) } },
23901
- status: {
23902
- schema: NetworkLinkStatusSchema,
23903
- kind: "push",
23904
- empty: {
23905
- type: "unknown",
23906
- signalPercent: null,
23907
- lastUpdated: 0
23908
- }
23909
- },
23910
- /**
23911
- * Runtime-state slice — every provider stores the same shape under
23912
- * `device.runtimeState['network-link']`, read once by the badge and the
23913
- * Home Assistant projector regardless of the driver.
23914
- */
23915
- runtimeState: NetworkLinkStatusSchema,
23916
- /**
23917
- * Runtime-state durability: **restored** — a link reading is slow to
23918
- * change and a sleeping battery camera may not report for hours; the
23919
- * restored slice is what the badge shows until the next read.
23920
- *
23921
- * See `RuntimeStateDurability`. Enforced by
23922
- * `scripts/check-runtime-state-durability.ts`.
23923
- */
23924
- durability: "restored",
23925
- /** Clock fields: written, but excluded from the compare that decides
23926
- * whether persisting is worth a SQLite commit. */
23927
- volatileStateFields: ["lastUpdated"]
23928
- };
23929
- /**
23930
23971
  * Generic boolean sensor — last-resort fallback when no domain-
23931
23972
  * specific binary cap fits (Home Assistant `binary_sensor` without a
23932
23973
  * known `device_class`, or a domain we haven't typed yet). Pure
@@ -27473,6 +27514,369 @@ var nativeObjectDetectionCapability = {
27473
27514
  volatileStateFields: ["lastFetchedAt"]
27474
27515
  };
27475
27516
  /**
27517
+ * `navigation` — a device-scoped capability that natively expresses the FULL
27518
+ * navigation / action surface of a robot that DRIVES ITSELF and carries an
27519
+ * on-board camera (the Dreame robot-vacuum camera is the first provider).
27520
+ *
27521
+ * Why a NEW cap rather than overloading `ptz`:
27522
+ * - `ptz` moves a *gimbal* on a fixed camera (pan/tilt/zoom of the lens). A
27523
+ * robot vacuum has no gimbal — the whole chassis drives, turns and spins.
27524
+ * The two are different physical models: PTZ is absolute-position + presets,
27525
+ * navigation is momentary drive nudges + discrete robot ACTIONS
27526
+ * (dock / spot-clean / follow-pet / go-to-point / …).
27527
+ * - This cap is the SOURCE OF TRUTH. Two consumers adapt from it rather than
27528
+ * the reverse:
27529
+ * 1. a native CamStack navigation panel (data-driven from `listActions`
27530
+ * / `getOptions`), and
27531
+ * 2. the PTZ surface — a thin adapter mimics `ptz` from `navigation` so a
27532
+ * robot camera shows up in the existing PTZ control path without every
27533
+ * PTZ provider learning about robots. The mapping lives in the adapter,
27534
+ * not here (see the addon design note):
27535
+ * ptz.continuousMove({pan,tilt}) → navigation.move({pan,tilt})
27536
+ * ptz.stop() → navigation.stop()
27537
+ * ptz.goHome() → navigation.runAction('goHome')
27538
+ * ptz.getPresets() → navigation.listActions() (id→preset)
27539
+ * ptz.goToPreset(id) → navigation.runAction(id)
27540
+ *
27541
+ * ## Continuous drive
27542
+ *
27543
+ * `move` is MOMENTARY. Fluid navigation comes from the UI (or the PTZ adapter)
27544
+ * sending `move({pan,tilt})` REPEATEDLY at ~1 Hz while a direction is held, and
27545
+ * one `stop()` on release — exactly like the robot app's remote-drive joystick.
27546
+ * The provider forwards EACH `move` to one drive write; it must NOT debounce or
27547
+ * coalesce them. The UI owns the cadence.
27548
+ *
27549
+ * ## The action dictionary
27550
+ *
27551
+ * The discrete controls (dock / locate / spot-clean / follow / flash / sounds)
27552
+ * are a DATA-DRIVEN dictionary the cap exposes via `listActions()`. Each entry
27553
+ * carries `{ id, kind, label, icon }` (plus `soundId` for sound entries) so the
27554
+ * native panel AND the PTZ mimic render buttons WITHOUT hardcoding a
27555
+ * vendor-specific list. `kind: 'action'` entries are triggered with
27556
+ * `runAction({ actionId })`; `kind: 'sound'` entries with `playSound({ soundId })`
27557
+ * (the entry carries the `soundId` to pass). The general primitives — `move`,
27558
+ * `stop`, `goToPoint` — stay as first-class methods, not dictionary entries.
27559
+ *
27560
+ * NOTE (provider wiring): the first provider (Dreame) drives this with the RAW
27561
+ * `callAction(siid,aiid,in)` / `setProperty({siid,piid,value})` MIoT primitives
27562
+ * that the currently-published `@apocaliss92/nodedreame` already exposes on
27563
+ * every device handle. A future nodedreame publish adds a typed
27564
+ * `DreameCameraController` (drive / playPetSound / spotClean / findPet / …); the
27565
+ * provider can then swap the raw calls for the typed methods with no change to
27566
+ * THIS contract.
27567
+ */
27568
+ /**
27569
+ * A momentary drive nudge. The robot MOVES (no gimbal) for as long as the caller
27570
+ * keeps sending nudges (~1 Hz); an explicit `stop` (or letting the nudges lapse)
27571
+ * halts it.
27572
+ *
27573
+ * - `pan` — turn: negative = left, positive = right, 0 = straight.
27574
+ * - `tilt` — throttle: positive = forward, negative = spin / turn-around.
27575
+ * - `speed` — optional intensity hint [0, 1]; the provider may scale the drive
27576
+ * vector by it (drivers without proportional drive ignore it).
27577
+ *
27578
+ * `pan` / `tilt` are normalized [-1, 1]. Both optional so a caller can nudge one
27579
+ * axis alone; an all-undefined nudge is a no-op.
27580
+ */
27581
+ var NavigationMoveCommandSchema = object({
27582
+ pan: number().min(-1).max(1).optional(),
27583
+ tilt: number().min(-1).max(1).optional(),
27584
+ speed: number().min(0).max(1).optional()
27585
+ });
27586
+ /**
27587
+ * The enumerated discrete actions a navigation-capable robot can perform via
27588
+ * `runAction`. This is the CLOSED vocabulary; a given device advertises the
27589
+ * subset it supports through `listActions`. Sounds are NOT here — they go through
27590
+ * `playSound` (see the `sound` dictionary entries).
27591
+ */
27592
+ var NavigationActionIdSchema = _enum([
27593
+ "goHome",
27594
+ "locate",
27595
+ "spotClean",
27596
+ "findPet",
27597
+ "personFollow",
27598
+ "stop",
27599
+ "startClean",
27600
+ "pauseClean",
27601
+ "dockWash",
27602
+ "autoEmpty",
27603
+ "flashOn",
27604
+ "flashOff"
27605
+ ]);
27606
+ /** Whether a dictionary entry is a `runAction` action or a `playSound` sound. */
27607
+ var NavigationEntryKindSchema = _enum(["action", "sound"]);
27608
+ /**
27609
+ * One entry in the navigation action dictionary — the DATA-DRIVEN unit both the
27610
+ * native panel and the PTZ mimic render as a button.
27611
+ *
27612
+ * - `id` — stable id. For `kind:'action'` it is a {@link NavigationActionId}
27613
+ * (pass to `runAction`); for `kind:'sound'` it is a namespaced id
27614
+ * (`sound:meow`) whose `soundId` is passed to `playSound`.
27615
+ * - `icon` — icon HINT (lucide-style name; the UI maps it to its own set).
27616
+ * - `label` — operator-facing English label.
27617
+ * - `soundId` — wire sound id, present only on `kind:'sound'` entries.
27618
+ * - `enabled` — per-device FEATURE FLAG. `listActions` reports it so the UI /
27619
+ * PTZ render ONLY enabled entries. Data-driven: the provider
27620
+ * flips it from config, never by editing code.
27621
+ */
27622
+ var NavigationActionEntrySchema = object({
27623
+ id: string(),
27624
+ kind: NavigationEntryKindSchema,
27625
+ label: string(),
27626
+ icon: string(),
27627
+ /** Present only on `kind:'sound'` entries — the id to pass to `playSound`. */
27628
+ soundId: number().int().optional(),
27629
+ /** Per-device feature flag — render this entry only when true. */
27630
+ enabled: boolean()
27631
+ });
27632
+ /** Coordinates for `goToPoint` — a point on the robot's live map. */
27633
+ var NavigationPointSchema = object({
27634
+ x: number(),
27635
+ y: number()
27636
+ });
27637
+ /**
27638
+ * Per-device FEATURE-FLAG report for the general (non-dictionary) primitives.
27639
+ * The cap reports which are enabled so the UI / PTZ render only the controls
27640
+ * that are turned on for THIS device. Data-driven: the provider derives these
27641
+ * from config + probe, never hardcoded in the UI. The per-DICTIONARY-entry flags
27642
+ * live on {@link NavigationActionEntrySchema.enabled}; these gate the primitives
27643
+ * that are not dictionary entries.
27644
+ *
27645
+ * - `move` / `stop` — the momentary drive joystick.
27646
+ * - `goToPoint` — send-to-map-coordinate. Ships OFF on Dreame until the
27647
+ * map-coordinate plumbing is wired.
27648
+ * - `runAction` — the discrete action buttons (dictionary `kind:'action'`).
27649
+ * - `playSound` — the sound buttons (dictionary `kind:'sound'`).
27650
+ * - `light` — the on/off fill-light toggle (works anytime).
27651
+ * - `lightMode` — the auto/manual selector + manual level slider (a
27652
+ * camera-service control; needs an active stream).
27653
+ */
27654
+ var NavigationFeaturesSchema = object({
27655
+ move: boolean(),
27656
+ stop: boolean(),
27657
+ goToPoint: boolean(),
27658
+ runAction: boolean(),
27659
+ playSound: boolean(),
27660
+ light: boolean(),
27661
+ lightMode: boolean()
27662
+ });
27663
+ /** Light mode: `auto` lets the camera choose brightness; `manual` uses `level`. */
27664
+ var NavigationLightModeSchema = _enum(["auto", "manual"]);
27665
+ /**
27666
+ * Live navigation state so the UI can reflect what the robot is doing:
27667
+ * - `mode` — coarse activity (idle / cleaning / following / …).
27668
+ * - `following` — person/pet follow is currently armed.
27669
+ * - `flash` — the on-camera fill light is on.
27670
+ * - `lightMode` — auto vs manual fill-light mode.
27671
+ * - `lightLevel` — manual fill-light level (40..100); meaningful when
27672
+ * `lightMode === 'manual'`.
27673
+ */
27674
+ var NavigationStatusSchema = object({
27675
+ mode: _enum([
27676
+ "idle",
27677
+ "cleaning",
27678
+ "spot",
27679
+ "following",
27680
+ "goto",
27681
+ "returning",
27682
+ "paused",
27683
+ "unknown"
27684
+ ]),
27685
+ following: boolean(),
27686
+ flash: boolean(),
27687
+ lightMode: NavigationLightModeSchema,
27688
+ lightLevel: number().min(40).max(100),
27689
+ /** Ms epoch when the slice was last updated. */
27690
+ lastChangedAt: number()
27691
+ });
27692
+ /**
27693
+ * Runtime-state slice owned by this cap (kernel-managed: validated, mirrored,
27694
+ * observable). Adds `lastFetchedAt` on top of the status shape per the
27695
+ * convention.
27696
+ */
27697
+ var NavigationRuntimeStateSchema = NavigationStatusSchema.extend({ lastFetchedAt: number() });
27698
+ var navigationCapability = {
27699
+ name: "navigation",
27700
+ scope: "device",
27701
+ deviceNative: true,
27702
+ mode: "singleton",
27703
+ deviceTypes: [DeviceType.Camera],
27704
+ deviceConfig: { ui: {
27705
+ kind: "widget",
27706
+ widgetId: "host/navigation-panel",
27707
+ tab: "navigation",
27708
+ topTab: true,
27709
+ label: "Navigation",
27710
+ order: 0
27711
+ } },
27712
+ methods: {
27713
+ /**
27714
+ * Momentary drive nudge (the robot moves). `protected` — mirrors
27715
+ * `ptz.continuousMove` so the Viewer navigation panel (and the PTZ-mimic
27716
+ * path) works for any authenticated user, not admin-only. The UI sends
27717
+ * these at ~1 Hz while a control is held; the provider forwards each one to
27718
+ * a single drive write WITHOUT debouncing.
27719
+ */
27720
+ move: method(NavigationMoveCommandSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }),
27721
+ /** Halt all motion immediately (zero drive vector). */
27722
+ stop: method(object({ deviceId: number() }), _void(), { kind: "mutation" }),
27723
+ /** Send the robot to a point on its live map. */
27724
+ goToPoint: method(NavigationPointSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }),
27725
+ /**
27726
+ * Enumerate the discrete controls THIS device supports (data-driven UI +
27727
+ * PTZ mimic). Camera-probed subset of {@link NAVIGATION_ACTION_CATALOG}.
27728
+ */
27729
+ listActions: method(object({ deviceId: number() }), array(NavigationActionEntrySchema)),
27730
+ /**
27731
+ * Run one discrete action (a `kind:'action'` dictionary entry). Invalid /
27732
+ * unsupported action ids are rejected by the provider.
27733
+ */
27734
+ runAction: method(object({
27735
+ deviceId: number(),
27736
+ actionId: NavigationActionIdSchema
27737
+ }), _void(), { kind: "mutation" }),
27738
+ /** Play a sound by its wire id (the `soundId` of a `kind:'sound'` entry). */
27739
+ playSound: method(object({
27740
+ deviceId: number(),
27741
+ soundId: number().int()
27742
+ }), _void(), { kind: "mutation" }),
27743
+ /**
27744
+ * Turn the on-camera fill light on / off (the `OpenFullLight` control —
27745
+ * works anytime, no active stream required).
27746
+ */
27747
+ setLightOn: method(object({
27748
+ deviceId: number(),
27749
+ on: boolean()
27750
+ }), _void(), { kind: "mutation" }),
27751
+ /**
27752
+ * Set the fill-light mode (auto vs manual). `manual` optionally carries the
27753
+ * initial `level`. The auto/manual + level control is a CAMERA-service
27754
+ * action that generally needs an active camera stream/monitor session — the
27755
+ * UI shows the manual level slider ONLY when `mode === 'manual'`.
27756
+ */
27757
+ setLightMode: method(object({
27758
+ deviceId: number(),
27759
+ mode: NavigationLightModeSchema,
27760
+ level: number().min(40).max(100).optional()
27761
+ }), _void(), { kind: "mutation" }),
27762
+ /** Set the MANUAL fill-light level (40..100). Implies `manual` mode. */
27763
+ setLightLevel: method(object({
27764
+ deviceId: number(),
27765
+ level: number().min(40).max(100)
27766
+ }), _void(), { kind: "mutation" }),
27767
+ /**
27768
+ * Per-device FEATURE-FLAG report for the general primitives — drives which
27769
+ * controls the UI shows (the per-entry flags for the dictionary come back on
27770
+ * `listActions`).
27771
+ */
27772
+ getFeatures: method(object({ deviceId: number() }), NavigationFeaturesSchema)
27773
+ },
27774
+ events: { onStatusChanged: { data: object({
27775
+ deviceId: number(),
27776
+ status: NavigationStatusSchema
27777
+ }) } },
27778
+ status: {
27779
+ schema: NavigationStatusSchema,
27780
+ kind: "push"
27781
+ },
27782
+ /**
27783
+ * Runtime-state slice mirrored by the kernel. The navigation panel watches it
27784
+ * for live mode / follow / flash changes.
27785
+ */
27786
+ runtimeState: NavigationRuntimeStateSchema,
27787
+ /**
27788
+ * Runtime-state durability: **session** — like `vacuum-control`, a restored
27789
+ * `mode: cleaning` / `following: true` is a robot that is not actually doing
27790
+ * that. The live handle re-publishes on connect.
27791
+ *
27792
+ * See `RuntimeStateDurability`. Enforced by
27793
+ * `scripts/check-runtime-state-durability.ts`.
27794
+ */
27795
+ durability: "session"
27796
+ };
27797
+ /**
27798
+ * Network-link snapshot. Same shape for every provider (a Reolink wifi
27799
+ * camera, a Home Assistant device with a signal-strength sensor, a Tapo
27800
+ * plug): one slice under `device.runtimeState['network-link']`, one badge,
27801
+ * one Home Assistant projection.
27802
+ */
27803
+ var NetworkLinkStatusSchema = object({
27804
+ /** The link the device is on. `'unknown'` = not read yet, not "no link". */
27805
+ type: _enum([
27806
+ "wifi",
27807
+ "ethernet",
27808
+ "cellular",
27809
+ "unknown"
27810
+ ]),
27811
+ /**
27812
+ * Link quality, 0..100 inclusive, normalised by the provider from whatever
27813
+ * the firmware reports (bars, RSSI, a vendor scale). **`null` means NOT
27814
+ * KNOWN or NOT APPLICABLE** — a wired link has no signal, and a wireless
27815
+ * one whose reading has not landed must not be drawn at 0 %. Consumers
27816
+ * SKIP a null rather than coerce it.
27817
+ */
27818
+ signalPercent: number().min(0).max(100).nullable(),
27819
+ /** Raw received signal strength in dBm, when the firmware reports one. */
27820
+ rssiDbm: number().optional(),
27821
+ /** Network name of a wireless link, when the firmware reports it. */
27822
+ ssid: string().optional(),
27823
+ /** Ms epoch of the last observation. Lets consumers reason about freshness. */
27824
+ lastUpdated: number()
27825
+ });
27826
+ var networkLinkCapability = {
27827
+ name: "network-link",
27828
+ scope: "device",
27829
+ deviceNative: true,
27830
+ mode: "singleton",
27831
+ deviceTypes: [
27832
+ DeviceType.Camera,
27833
+ DeviceType.Sensor,
27834
+ DeviceType.Button,
27835
+ DeviceType.Switch,
27836
+ DeviceType.Light,
27837
+ DeviceType.Lock,
27838
+ DeviceType.Siren
27839
+ ],
27840
+ methods: {},
27841
+ events: {
27842
+ /**
27843
+ * Emitted whenever the cached status changes (a link switch, a signal
27844
+ * reading that moved). Mirrored on the parent chain by the
27845
+ * DeviceEventPropagator like `battery.onStatusChanged`.
27846
+ */
27847
+ onStatusChanged: { data: object({
27848
+ deviceId: number(),
27849
+ status: NetworkLinkStatusSchema
27850
+ }) } },
27851
+ status: {
27852
+ schema: NetworkLinkStatusSchema,
27853
+ kind: "push",
27854
+ empty: {
27855
+ type: "unknown",
27856
+ signalPercent: null,
27857
+ lastUpdated: 0
27858
+ }
27859
+ },
27860
+ /**
27861
+ * Runtime-state slice — every provider stores the same shape under
27862
+ * `device.runtimeState['network-link']`, read once by the badge and the
27863
+ * Home Assistant projector regardless of the driver.
27864
+ */
27865
+ runtimeState: NetworkLinkStatusSchema,
27866
+ /**
27867
+ * Runtime-state durability: **restored** — a link reading is slow to
27868
+ * change and a sleeping battery camera may not report for hours; the
27869
+ * restored slice is what the badge shows until the next read.
27870
+ *
27871
+ * See `RuntimeStateDurability`. Enforced by
27872
+ * `scripts/check-runtime-state-durability.ts`.
27873
+ */
27874
+ durability: "restored",
27875
+ /** Clock fields: written, but excluded from the compare that decides
27876
+ * whether persisting is worth a SQLite commit. */
27877
+ volatileStateFields: ["lastUpdated"]
27878
+ };
27879
+ /**
27476
27880
  * network-quality — system-scoped singleton capability tracking RTT,
27477
27881
  * jitter, and observed/peak bandwidth per device + per client.
27478
27882
  *
@@ -29053,287 +29457,6 @@ var ptzAutotrackCapability = {
29053
29457
  */
29054
29458
  durability: "session"
29055
29459
  };
29056
- /**
29057
- * `navigation` — a device-scoped capability that natively expresses the FULL
29058
- * navigation / action surface of a robot that DRIVES ITSELF and carries an
29059
- * on-board camera (the Dreame robot-vacuum camera is the first provider).
29060
- *
29061
- * Why a NEW cap rather than overloading `ptz`:
29062
- * - `ptz` moves a *gimbal* on a fixed camera (pan/tilt/zoom of the lens). A
29063
- * robot vacuum has no gimbal — the whole chassis drives, turns and spins.
29064
- * The two are different physical models: PTZ is absolute-position + presets,
29065
- * navigation is momentary drive nudges + discrete robot ACTIONS
29066
- * (dock / spot-clean / follow-pet / go-to-point / …).
29067
- * - This cap is the SOURCE OF TRUTH. Two consumers adapt from it rather than
29068
- * the reverse:
29069
- * 1. a native CamStack navigation panel (data-driven from `listActions`
29070
- * / `getOptions`), and
29071
- * 2. the PTZ surface — a thin adapter mimics `ptz` from `navigation` so a
29072
- * robot camera shows up in the existing PTZ control path without every
29073
- * PTZ provider learning about robots. The mapping lives in the adapter,
29074
- * not here (see the addon design note):
29075
- * ptz.continuousMove({pan,tilt}) → navigation.move({pan,tilt})
29076
- * ptz.stop() → navigation.stop()
29077
- * ptz.goHome() → navigation.runAction('goHome')
29078
- * ptz.getPresets() → navigation.listActions() (id→preset)
29079
- * ptz.goToPreset(id) → navigation.runAction(id)
29080
- *
29081
- * ## Continuous drive
29082
- *
29083
- * `move` is MOMENTARY. Fluid navigation comes from the UI (or the PTZ adapter)
29084
- * sending `move({pan,tilt})` REPEATEDLY at ~1 Hz while a direction is held, and
29085
- * one `stop()` on release — exactly like the robot app's remote-drive joystick.
29086
- * The provider forwards EACH `move` to one drive write; it must NOT debounce or
29087
- * coalesce them. The UI owns the cadence.
29088
- *
29089
- * ## The action dictionary
29090
- *
29091
- * The discrete controls (dock / locate / spot-clean / follow / flash / sounds)
29092
- * are a DATA-DRIVEN dictionary the cap exposes via `listActions()`. Each entry
29093
- * carries `{ id, kind, label, icon }` (plus `soundId` for sound entries) so the
29094
- * native panel AND the PTZ mimic render buttons WITHOUT hardcoding a
29095
- * vendor-specific list. `kind: 'action'` entries are triggered with
29096
- * `runAction({ actionId })`; `kind: 'sound'` entries with `playSound({ soundId })`
29097
- * (the entry carries the `soundId` to pass). The general primitives — `move`,
29098
- * `stop`, `goToPoint` — stay as first-class methods, not dictionary entries.
29099
- *
29100
- * NOTE (provider wiring): the first provider (Dreame) drives this with the RAW
29101
- * `callAction(siid,aiid,in)` / `setProperty({siid,piid,value})` MIoT primitives
29102
- * that the currently-published `@apocaliss92/nodedreame` already exposes on
29103
- * every device handle. A future nodedreame publish adds a typed
29104
- * `DreameCameraController` (drive / playPetSound / spotClean / findPet / …); the
29105
- * provider can then swap the raw calls for the typed methods with no change to
29106
- * THIS contract.
29107
- */
29108
- /**
29109
- * A momentary drive nudge. The robot MOVES (no gimbal) for as long as the caller
29110
- * keeps sending nudges (~1 Hz); an explicit `stop` (or letting the nudges lapse)
29111
- * halts it.
29112
- *
29113
- * - `pan` — turn: negative = left, positive = right, 0 = straight.
29114
- * - `tilt` — throttle: positive = forward, negative = spin / turn-around.
29115
- * - `speed` — optional intensity hint [0, 1]; the provider may scale the drive
29116
- * vector by it (drivers without proportional drive ignore it).
29117
- *
29118
- * `pan` / `tilt` are normalized [-1, 1]. Both optional so a caller can nudge one
29119
- * axis alone; an all-undefined nudge is a no-op.
29120
- */
29121
- var NavigationMoveCommandSchema = object({
29122
- pan: number().min(-1).max(1).optional(),
29123
- tilt: number().min(-1).max(1).optional(),
29124
- speed: number().min(0).max(1).optional()
29125
- });
29126
- /**
29127
- * The enumerated discrete actions a navigation-capable robot can perform via
29128
- * `runAction`. This is the CLOSED vocabulary; a given device advertises the
29129
- * subset it supports through `listActions`. Sounds are NOT here — they go through
29130
- * `playSound` (see the `sound` dictionary entries).
29131
- */
29132
- var NavigationActionIdSchema = _enum([
29133
- "goHome",
29134
- "locate",
29135
- "spotClean",
29136
- "findPet",
29137
- "personFollow",
29138
- "stop",
29139
- "startClean",
29140
- "pauseClean",
29141
- "dockWash",
29142
- "autoEmpty",
29143
- "flashOn",
29144
- "flashOff"
29145
- ]);
29146
- /** Whether a dictionary entry is a `runAction` action or a `playSound` sound. */
29147
- var NavigationEntryKindSchema = _enum(["action", "sound"]);
29148
- /**
29149
- * One entry in the navigation action dictionary — the DATA-DRIVEN unit both the
29150
- * native panel and the PTZ mimic render as a button.
29151
- *
29152
- * - `id` — stable id. For `kind:'action'` it is a {@link NavigationActionId}
29153
- * (pass to `runAction`); for `kind:'sound'` it is a namespaced id
29154
- * (`sound:meow`) whose `soundId` is passed to `playSound`.
29155
- * - `icon` — icon HINT (lucide-style name; the UI maps it to its own set).
29156
- * - `label` — operator-facing English label.
29157
- * - `soundId` — wire sound id, present only on `kind:'sound'` entries.
29158
- * - `enabled` — per-device FEATURE FLAG. `listActions` reports it so the UI /
29159
- * PTZ render ONLY enabled entries. Data-driven: the provider
29160
- * flips it from config, never by editing code.
29161
- */
29162
- var NavigationActionEntrySchema = object({
29163
- id: string(),
29164
- kind: NavigationEntryKindSchema,
29165
- label: string(),
29166
- icon: string(),
29167
- /** Present only on `kind:'sound'` entries — the id to pass to `playSound`. */
29168
- soundId: number().int().optional(),
29169
- /** Per-device feature flag — render this entry only when true. */
29170
- enabled: boolean()
29171
- });
29172
- /** Coordinates for `goToPoint` — a point on the robot's live map. */
29173
- var NavigationPointSchema = object({
29174
- x: number(),
29175
- y: number()
29176
- });
29177
- /**
29178
- * Per-device FEATURE-FLAG report for the general (non-dictionary) primitives.
29179
- * The cap reports which are enabled so the UI / PTZ render only the controls
29180
- * that are turned on for THIS device. Data-driven: the provider derives these
29181
- * from config + probe, never hardcoded in the UI. The per-DICTIONARY-entry flags
29182
- * live on {@link NavigationActionEntrySchema.enabled}; these gate the primitives
29183
- * that are not dictionary entries.
29184
- *
29185
- * - `move` / `stop` — the momentary drive joystick.
29186
- * - `goToPoint` — send-to-map-coordinate. Ships OFF on Dreame until the
29187
- * map-coordinate plumbing is wired.
29188
- * - `runAction` — the discrete action buttons (dictionary `kind:'action'`).
29189
- * - `playSound` — the sound buttons (dictionary `kind:'sound'`).
29190
- * - `light` — the on/off fill-light toggle (works anytime).
29191
- * - `lightMode` — the auto/manual selector + manual level slider (a
29192
- * camera-service control; needs an active stream).
29193
- */
29194
- var NavigationFeaturesSchema = object({
29195
- move: boolean(),
29196
- stop: boolean(),
29197
- goToPoint: boolean(),
29198
- runAction: boolean(),
29199
- playSound: boolean(),
29200
- light: boolean(),
29201
- lightMode: boolean()
29202
- });
29203
- /** Light mode: `auto` lets the camera choose brightness; `manual` uses `level`. */
29204
- var NavigationLightModeSchema = _enum(["auto", "manual"]);
29205
- /**
29206
- * Live navigation state so the UI can reflect what the robot is doing:
29207
- * - `mode` — coarse activity (idle / cleaning / following / …).
29208
- * - `following` — person/pet follow is currently armed.
29209
- * - `flash` — the on-camera fill light is on.
29210
- * - `lightMode` — auto vs manual fill-light mode.
29211
- * - `lightLevel` — manual fill-light level (40..100); meaningful when
29212
- * `lightMode === 'manual'`.
29213
- */
29214
- var NavigationStatusSchema = object({
29215
- mode: _enum([
29216
- "idle",
29217
- "cleaning",
29218
- "spot",
29219
- "following",
29220
- "goto",
29221
- "returning",
29222
- "paused",
29223
- "unknown"
29224
- ]),
29225
- following: boolean(),
29226
- flash: boolean(),
29227
- lightMode: NavigationLightModeSchema,
29228
- lightLevel: number().min(40).max(100),
29229
- /** Ms epoch when the slice was last updated. */
29230
- lastChangedAt: number()
29231
- });
29232
- /**
29233
- * Runtime-state slice owned by this cap (kernel-managed: validated, mirrored,
29234
- * observable). Adds `lastFetchedAt` on top of the status shape per the
29235
- * convention.
29236
- */
29237
- var NavigationRuntimeStateSchema = NavigationStatusSchema.extend({ lastFetchedAt: number() });
29238
- var navigationCapability = {
29239
- name: "navigation",
29240
- scope: "device",
29241
- deviceNative: true,
29242
- mode: "singleton",
29243
- deviceTypes: [DeviceType.Camera],
29244
- deviceConfig: { ui: {
29245
- kind: "widget",
29246
- widgetId: "host/navigation-panel",
29247
- tab: "navigation",
29248
- topTab: true,
29249
- label: "Navigation",
29250
- order: 0
29251
- } },
29252
- methods: {
29253
- /**
29254
- * Momentary drive nudge (the robot moves). `protected` — mirrors
29255
- * `ptz.continuousMove` so the Viewer navigation panel (and the PTZ-mimic
29256
- * path) works for any authenticated user, not admin-only. The UI sends
29257
- * these at ~1 Hz while a control is held; the provider forwards each one to
29258
- * a single drive write WITHOUT debouncing.
29259
- */
29260
- move: method(NavigationMoveCommandSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }),
29261
- /** Halt all motion immediately (zero drive vector). */
29262
- stop: method(object({ deviceId: number() }), _void(), { kind: "mutation" }),
29263
- /** Send the robot to a point on its live map. */
29264
- goToPoint: method(NavigationPointSchema.extend({ deviceId: number() }), _void(), { kind: "mutation" }),
29265
- /**
29266
- * Enumerate the discrete controls THIS device supports (data-driven UI +
29267
- * PTZ mimic). Camera-probed subset of {@link NAVIGATION_ACTION_CATALOG}.
29268
- */
29269
- listActions: method(object({ deviceId: number() }), array(NavigationActionEntrySchema)),
29270
- /**
29271
- * Run one discrete action (a `kind:'action'` dictionary entry). Invalid /
29272
- * unsupported action ids are rejected by the provider.
29273
- */
29274
- runAction: method(object({
29275
- deviceId: number(),
29276
- actionId: NavigationActionIdSchema
29277
- }), _void(), { kind: "mutation" }),
29278
- /** Play a sound by its wire id (the `soundId` of a `kind:'sound'` entry). */
29279
- playSound: method(object({
29280
- deviceId: number(),
29281
- soundId: number().int()
29282
- }), _void(), { kind: "mutation" }),
29283
- /**
29284
- * Turn the on-camera fill light on / off (the `OpenFullLight` control —
29285
- * works anytime, no active stream required).
29286
- */
29287
- setLightOn: method(object({
29288
- deviceId: number(),
29289
- on: boolean()
29290
- }), _void(), { kind: "mutation" }),
29291
- /**
29292
- * Set the fill-light mode (auto vs manual). `manual` optionally carries the
29293
- * initial `level`. The auto/manual + level control is a CAMERA-service
29294
- * action that generally needs an active camera stream/monitor session — the
29295
- * UI shows the manual level slider ONLY when `mode === 'manual'`.
29296
- */
29297
- setLightMode: method(object({
29298
- deviceId: number(),
29299
- mode: NavigationLightModeSchema,
29300
- level: number().min(40).max(100).optional()
29301
- }), _void(), { kind: "mutation" }),
29302
- /** Set the MANUAL fill-light level (40..100). Implies `manual` mode. */
29303
- setLightLevel: method(object({
29304
- deviceId: number(),
29305
- level: number().min(40).max(100)
29306
- }), _void(), { kind: "mutation" }),
29307
- /**
29308
- * Per-device FEATURE-FLAG report for the general primitives — drives which
29309
- * controls the UI shows (the per-entry flags for the dictionary come back on
29310
- * `listActions`).
29311
- */
29312
- getFeatures: method(object({ deviceId: number() }), NavigationFeaturesSchema)
29313
- },
29314
- events: { onStatusChanged: { data: object({
29315
- deviceId: number(),
29316
- status: NavigationStatusSchema
29317
- }) } },
29318
- status: {
29319
- schema: NavigationStatusSchema,
29320
- kind: "push"
29321
- },
29322
- /**
29323
- * Runtime-state slice mirrored by the kernel. The navigation panel watches it
29324
- * for live mode / follow / flash changes.
29325
- */
29326
- runtimeState: NavigationRuntimeStateSchema,
29327
- /**
29328
- * Runtime-state durability: **session** — like `vacuum-control`, a restored
29329
- * `mode: cleaning` / `following: true` is a robot that is not actually doing
29330
- * that. The live handle re-publishes on connect.
29331
- *
29332
- * See `RuntimeStateDurability`. Enforced by
29333
- * `scripts/check-runtime-state-durability.ts`.
29334
- */
29335
- durability: "session"
29336
- };
29337
29460
  DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceId: number().int().nonnegative() }), object({ success: literal(true) }), {
29338
29461
  kind: "mutation",
29339
29462
  auth: "admin"
@@ -38796,6 +38919,12 @@ Object.freeze({
38796
38919
  addonId: null,
38797
38920
  access: "view"
38798
38921
  },
38922
+ "storage.listDrainProgress": {
38923
+ capName: "storage",
38924
+ capScope: "system",
38925
+ addonId: null,
38926
+ access: "view"
38927
+ },
38799
38928
  "storage.listLocationDeclarations": {
38800
38929
  capName: "storage",
38801
38930
  capScope: "system",
@@ -38940,6 +39069,12 @@ Object.freeze({
38940
39069
  addonId: null,
38941
39070
  access: "view"
38942
39071
  },
39072
+ "storageOccupancy.getOccupancy": {
39073
+ capName: "storage-occupancy",
39074
+ capScope: "system",
39075
+ addonId: null,
39076
+ access: "view"
39077
+ },
38943
39078
  "storageProvider.abortUpload": {
38944
39079
  capName: "storage-provider",
38945
39080
  capScope: "system",