@camstack/addon-provider-gree 0.2.62 → 0.2.63
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/dist/addon.js +42 -0
- package/dist/addon.mjs +42 -0
- package/package.json +1 -1
package/dist/addon.js
CHANGED
|
@@ -12930,6 +12930,24 @@ var deviceProviderCapability = {
|
|
|
12930
12930
|
})
|
|
12931
12931
|
}
|
|
12932
12932
|
};
|
|
12933
|
+
/**
|
|
12934
|
+
* Device Manager capability — hub-side singleton that unifies device persistence,
|
|
12935
|
+
* live registry access, and all management operations into a single tRPC surface.
|
|
12936
|
+
*
|
|
12937
|
+
* Replaces:
|
|
12938
|
+
* - `device-persistence` capability (persistence methods absorbed here)
|
|
12939
|
+
* - `device-management.router.ts` (deleted in Phase 2)
|
|
12940
|
+
* - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
|
|
12941
|
+
*
|
|
12942
|
+
* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
|
|
12943
|
+
* fork into separate processes but never run on remote cluster agents. Therefore:
|
|
12944
|
+
* - No nodeId routing needed — this is a pure hub singleton.
|
|
12945
|
+
* - The hub's DeviceRegistry is the single source of truth for all live devices.
|
|
12946
|
+
* - No shadow registry or cross-node aggregation required.
|
|
12947
|
+
*
|
|
12948
|
+
* Forked workers register devices back to the hub via `ctx.devices`
|
|
12949
|
+
* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
|
|
12950
|
+
*/
|
|
12933
12951
|
/** One child-placement directive on a container's `childLayout`. Structurally
|
|
12934
12952
|
* identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
|
|
12935
12953
|
* shape for the same field. The child is identified by its re-sync-stable
|
|
@@ -18656,6 +18674,9 @@ var RetrainStatusSchema = _enum([
|
|
|
18656
18674
|
*
|
|
18657
18675
|
* `debug` does NOT pin; it is attention, not durability.
|
|
18658
18676
|
*
|
|
18677
|
+
* `debugNote` is the operator's own words about WHAT should be checked on this
|
|
18678
|
+
* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
|
|
18679
|
+
*
|
|
18659
18680
|
* `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
|
|
18660
18681
|
* A favourited track is skipped by retention the same way `staging` is, but
|
|
18661
18682
|
* it does not enter `none|staging|trained` and has no staging budget.
|
|
@@ -18666,6 +18687,21 @@ var TrackFlagFields = {
|
|
|
18666
18687
|
markForTrain: boolean().optional(),
|
|
18667
18688
|
/** Operator marked this track for diagnostic attention. */
|
|
18668
18689
|
debug: boolean().optional(),
|
|
18690
|
+
/**
|
|
18691
|
+
* What the operator wants CHECKED on this track, in their own words.
|
|
18692
|
+
*
|
|
18693
|
+
* The flag alone says "look at this" and nothing about what for; a debug set
|
|
18694
|
+
* reviewed hours later is a list of tracks with no question attached. Bound
|
|
18695
|
+
* to `debug` on the WRITE side — the body clears it when `debug` goes off,
|
|
18696
|
+
* and refuses it on a track whose debug is off — so a note can never outlive
|
|
18697
|
+
* the attention it belongs to.
|
|
18698
|
+
*
|
|
18699
|
+
* `''` is a real value ("marked, nothing to add"); the ABSENT key means
|
|
18700
|
+
* "leave whatever is stored alone", which is what lets a surface turn debug
|
|
18701
|
+
* on without a note (a cancelled prompt) and what lets it edit the note
|
|
18702
|
+
* without touching the flag.
|
|
18703
|
+
*/
|
|
18704
|
+
debugNote: string().max(500).optional(),
|
|
18669
18705
|
/** Operator favourited this track. Pins it against pruning. */
|
|
18670
18706
|
favourited: boolean().optional()
|
|
18671
18707
|
};
|
|
@@ -18692,6 +18728,12 @@ var TrackFlagsSchema = object({
|
|
|
18692
18728
|
trackId: string(),
|
|
18693
18729
|
markForTrain: boolean(),
|
|
18694
18730
|
debug: boolean(),
|
|
18731
|
+
/** The note as it STANDS after the write — never absent here (a track with no
|
|
18732
|
+
* note reports `''`), for the same reason the booleans are required: a
|
|
18733
|
+
* surface that has just written must be able to render the note it now owns
|
|
18734
|
+
* without a re-fetch, and an absent key would read as "unchanged" on a
|
|
18735
|
+
* screen that has no previous value to keep. */
|
|
18736
|
+
debugNote: string(),
|
|
18695
18737
|
favourited: boolean(),
|
|
18696
18738
|
/** The lifecycle state the boolean was derived from. Required here (unlike on
|
|
18697
18739
|
* a track row) because this shape is only ever produced by the write body,
|
package/dist/addon.mjs
CHANGED
|
@@ -12929,6 +12929,24 @@ var deviceProviderCapability = {
|
|
|
12929
12929
|
})
|
|
12930
12930
|
}
|
|
12931
12931
|
};
|
|
12932
|
+
/**
|
|
12933
|
+
* Device Manager capability — hub-side singleton that unifies device persistence,
|
|
12934
|
+
* live registry access, and all management operations into a single tRPC surface.
|
|
12935
|
+
*
|
|
12936
|
+
* Replaces:
|
|
12937
|
+
* - `device-persistence` capability (persistence methods absorbed here)
|
|
12938
|
+
* - `device-management.router.ts` (deleted in Phase 2)
|
|
12939
|
+
* - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
|
|
12940
|
+
*
|
|
12941
|
+
* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
|
|
12942
|
+
* fork into separate processes but never run on remote cluster agents. Therefore:
|
|
12943
|
+
* - No nodeId routing needed — this is a pure hub singleton.
|
|
12944
|
+
* - The hub's DeviceRegistry is the single source of truth for all live devices.
|
|
12945
|
+
* - No shadow registry or cross-node aggregation required.
|
|
12946
|
+
*
|
|
12947
|
+
* Forked workers register devices back to the hub via `ctx.devices`
|
|
12948
|
+
* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
|
|
12949
|
+
*/
|
|
12932
12950
|
/** One child-placement directive on a container's `childLayout`. Structurally
|
|
12933
12951
|
* identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
|
|
12934
12952
|
* shape for the same field. The child is identified by its re-sync-stable
|
|
@@ -18655,6 +18673,9 @@ var RetrainStatusSchema = _enum([
|
|
|
18655
18673
|
*
|
|
18656
18674
|
* `debug` does NOT pin; it is attention, not durability.
|
|
18657
18675
|
*
|
|
18676
|
+
* `debugNote` is the operator's own words about WHAT should be checked on this
|
|
18677
|
+
* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
|
|
18678
|
+
*
|
|
18658
18679
|
* `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
|
|
18659
18680
|
* A favourited track is skipped by retention the same way `staging` is, but
|
|
18660
18681
|
* it does not enter `none|staging|trained` and has no staging budget.
|
|
@@ -18665,6 +18686,21 @@ var TrackFlagFields = {
|
|
|
18665
18686
|
markForTrain: boolean().optional(),
|
|
18666
18687
|
/** Operator marked this track for diagnostic attention. */
|
|
18667
18688
|
debug: boolean().optional(),
|
|
18689
|
+
/**
|
|
18690
|
+
* What the operator wants CHECKED on this track, in their own words.
|
|
18691
|
+
*
|
|
18692
|
+
* The flag alone says "look at this" and nothing about what for; a debug set
|
|
18693
|
+
* reviewed hours later is a list of tracks with no question attached. Bound
|
|
18694
|
+
* to `debug` on the WRITE side — the body clears it when `debug` goes off,
|
|
18695
|
+
* and refuses it on a track whose debug is off — so a note can never outlive
|
|
18696
|
+
* the attention it belongs to.
|
|
18697
|
+
*
|
|
18698
|
+
* `''` is a real value ("marked, nothing to add"); the ABSENT key means
|
|
18699
|
+
* "leave whatever is stored alone", which is what lets a surface turn debug
|
|
18700
|
+
* on without a note (a cancelled prompt) and what lets it edit the note
|
|
18701
|
+
* without touching the flag.
|
|
18702
|
+
*/
|
|
18703
|
+
debugNote: string().max(500).optional(),
|
|
18668
18704
|
/** Operator favourited this track. Pins it against pruning. */
|
|
18669
18705
|
favourited: boolean().optional()
|
|
18670
18706
|
};
|
|
@@ -18691,6 +18727,12 @@ var TrackFlagsSchema = object({
|
|
|
18691
18727
|
trackId: string(),
|
|
18692
18728
|
markForTrain: boolean(),
|
|
18693
18729
|
debug: boolean(),
|
|
18730
|
+
/** The note as it STANDS after the write — never absent here (a track with no
|
|
18731
|
+
* note reports `''`), for the same reason the booleans are required: a
|
|
18732
|
+
* surface that has just written must be able to render the note it now owns
|
|
18733
|
+
* without a re-fetch, and an absent key would read as "unchanged" on a
|
|
18734
|
+
* screen that has no previous value to keep. */
|
|
18735
|
+
debugNote: string(),
|
|
18694
18736
|
favourited: boolean(),
|
|
18695
18737
|
/** The lifecycle state the boolean was derived from. Required here (unlike on
|
|
18696
18738
|
* a track row) because this shape is only ever produced by the write body,
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@camstack/addon-provider-gree",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.63",
|
|
4
4
|
"description": "Gree air-conditioner device-provider addon for CamStack — wraps the @apocaliss92/nodegree local-UDP client (LAN discovery + AES control), exposing climate-control and fan-control",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|