@camstack/addon-provider-homeassistant 1.2.52 → 1.2.54

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 CHANGED
@@ -1,5 +1,5 @@
1
1
  Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
2
- const require_dist = require("./dist-nBclHVR_.js");
2
+ const require_dist = require("./dist-D24orV6m.js");
3
3
  let node_crypto = require("node:crypto");
4
4
  let node_zlib = require("node:zlib");
5
5
  //#region src/ha-device-source.ts
package/dist/addon.mjs CHANGED
@@ -1,4 +1,4 @@
1
- import { $ as presenceCapability, A as controlCapability, At as EventCategory, B as humiditySensorCapability, C as buildAddonRouteProvider, Ct as number, D as colorCapability, Dt as union, E as climateControlCapability, Et as string, F as eventEmitterCapability, G as motionCapability, H as lawnMowerControlCapability, I as fanControlCapability, J as notifierCapability, K as normalizeUnit, L as floodCapability, M as deviceAdoptionCapability, O as connectivityCapability, Ot as unknown, P as enumSensorCapability, Q as prepareNotification, R as gasCapability, S as brokerCapability, St as literal, T as carbonMonoxideCapability, Tt as record, U as lockControlCapability, V as imageCapability, W as mediaPlayerCapability, Y as numericSensorCapability, Z as powerMeterCapability, _ as automationControlCapability, _t as createEvent, at as temperatureSensorCapability, b as binaryCapability, bt as array, ct as valveCapability, d as TargetSchema, dt as weatherCapability, et as pressureSensorCapability, f as accessoriesCapability, ft as errMsg, g as ambientLightSensorCapability, gt as DeviceType, h as alarmPanelCapability, ht as DeviceRole, it as tamperCapability, j as coverCapability, k as contactCapability, kt as url, lt as vibrationCapability, m as airQualitySensorCapability, mt as DeviceFeature, n as BaseDevice, nt as smokeCapability, ot as updateCapability, p as addonRoutesCapability, q as notificationOutputCapability, r as BaseDeviceProvider, rt as switchCapability, s as EnumSensorDateTimeFormatSchema, st as vacuumControlCapability, tt as scriptRunnerCapability, ut as waterHeaterCapability, v as batteryCapability, w as buttonCapability, wt as object, x as brightnessCapability, xt as discriminatedUnion, y as bestLocationMatch, yt as _enum, z as humidifierCapability } from "./dist-Dm7hAzfd.mjs";
1
+ import { $ as presenceCapability, A as controlCapability, At as EventCategory, B as humiditySensorCapability, C as buildAddonRouteProvider, Ct as number, D as colorCapability, Dt as union, E as climateControlCapability, Et as string, F as eventEmitterCapability, G as motionCapability, H as lawnMowerControlCapability, I as fanControlCapability, J as notifierCapability, K as normalizeUnit, L as floodCapability, M as deviceAdoptionCapability, O as connectivityCapability, Ot as unknown, P as enumSensorCapability, Q as prepareNotification, R as gasCapability, S as brokerCapability, St as literal, T as carbonMonoxideCapability, Tt as record, U as lockControlCapability, V as imageCapability, W as mediaPlayerCapability, Y as numericSensorCapability, Z as powerMeterCapability, _ as automationControlCapability, _t as createEvent, at as temperatureSensorCapability, b as binaryCapability, bt as array, ct as valveCapability, d as TargetSchema, dt as weatherCapability, et as pressureSensorCapability, f as accessoriesCapability, ft as errMsg, g as ambientLightSensorCapability, gt as DeviceType, h as alarmPanelCapability, ht as DeviceRole, it as tamperCapability, j as coverCapability, k as contactCapability, kt as url, lt as vibrationCapability, m as airQualitySensorCapability, mt as DeviceFeature, n as BaseDevice, nt as smokeCapability, ot as updateCapability, p as addonRoutesCapability, q as notificationOutputCapability, r as BaseDeviceProvider, rt as switchCapability, s as EnumSensorDateTimeFormatSchema, st as vacuumControlCapability, tt as scriptRunnerCapability, ut as waterHeaterCapability, v as batteryCapability, w as buttonCapability, wt as object, x as brightnessCapability, xt as discriminatedUnion, y as bestLocationMatch, yt as _enum, z as humidifierCapability } from "./dist-BfdeH6US.mjs";
2
2
  import { randomUUID } from "node:crypto";
3
3
  import { brotliCompressSync, deflateSync, gzipSync } from "node:zlib";
4
4
  //#region src/ha-device-source.ts
@@ -14240,6 +14240,50 @@ var NodeProcessSchema = object({
14240
14240
  /** Wall-clock uptime (seconds). Parsed from `ps etime`. */
14241
14241
  uptimeSec: number()
14242
14242
  });
14243
+ /**
14244
+ * One retained container-memory reading.
14245
+ *
14246
+ * `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
14247
+ * a second clock: that is what makes "processes sum to X, container says Y"
14248
+ * subtractable per point rather than an eyeballed comparison of two series
14249
+ * sampled at different instants.
14250
+ *
14251
+ * A reduced window keeps the sample with the LARGEST `currentBytes` in each
14252
+ * bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
14253
+ * never coexisted, and a mean would smear away the peak this exists to find.
14254
+ */
14255
+ var ContainerMemoryPointSchema = object({
14256
+ /** Which hierarchy answered, so a reading is never ambiguous. */
14257
+ source: _enum(["cgroup-v2", "cgroup-v1"]),
14258
+ /** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
14259
+ currentBytes: number(),
14260
+ /** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
14261
+ limitBytes: number().nullable(),
14262
+ /** Anonymous pages: the closest thing to "what the processes allocated". */
14263
+ anonBytes: number().nullable(),
14264
+ /** Page cache. Charged to the cgroup, owned by no process. */
14265
+ fileBytes: number().nullable(),
14266
+ /**
14267
+ * Shared memory — and the field that explained the largest single surprise.
14268
+ * The i915 driver backs GPU buffers with shmem, so an inference pool or a
14269
+ * hardware-decode session holding DRM objects is charged HERE and appears
14270
+ * nowhere in a `ps` scan.
14271
+ */
14272
+ shmemBytes: number().nullable(),
14273
+ /** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
14274
+ slabBytes: number().nullable(),
14275
+ /**
14276
+ * Shrinkable i915 GEM object bytes, from debugfs.
14277
+ *
14278
+ * **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
14279
+ * component of `currentBytes` and must not be subtracted from it; it says
14280
+ * what put the shmem there, where `shmemBytes` only says how much.
14281
+ *
14282
+ * `null` wherever debugfs is not mounted — which is inside every camstack
14283
+ * container today — and on any node with no Intel GPU.
14284
+ */
14285
+ gpuShmemBytes: number().nullable()
14286
+ }).extend({ atMs: number() });
14243
14287
  var DumpHeapSnapshotInputSchema = object({
14244
14288
  /** The addon whose runner should dump a heap snapshot. */
14245
14289
  addonId: string() });
@@ -14303,6 +14347,21 @@ var NodeLoadSeriesSchema = object({
14303
14347
  /** One entry per function seen in the window, heaviest-first. */
14304
14348
  series: array(LoadFunctionSeriesSchema).readonly(),
14305
14349
  /**
14350
+ * The CONTAINER's memory over the same window, oldest-first.
14351
+ *
14352
+ * Sits next to `series` rather than in a method of its own because the whole
14353
+ * question is a subtraction: the per-process rows in `series` sum to one
14354
+ * number and this one is another, and an operator who has to issue two calls
14355
+ * to compare them will compare two different instants. Same reader, same
14356
+ * `sinceMs`, same `bucketMs`, same timestamps.
14357
+ *
14358
+ * **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
14359
+ * Mac, a bare-metal host, a container with the hierarchy hidden — reports no
14360
+ * points at all. A zero here would be indistinguishable from a healthy
14361
+ * container and is precisely the lie this field exists to avoid.
14362
+ */
14363
+ containerMemory: array(ContainerMemoryPointSchema).readonly(),
14364
+ /**
14306
14365
  * Width of one returned bucket, in ms. Equals the sampling cadence when no
14307
14366
  * reduction was needed — so a caller can always say what one point covers
14308
14367
  * without having to know whether it was reduced.
@@ -28117,10 +28176,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
28117
28176
  * recording config. NOTE on events (source of truth, R5/C3): this cap carries
28118
28177
  * NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
28119
28178
  * events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
28120
- * rows); the recorder's internal EventMap markers are ephemeral in-RAM
28121
- * annotations that are not exposed here and must not be treated as an event
28122
- * feed. Event<->footage joins are by time, padded with the shared `EVENT_PAD_MS`
28123
- * (`interfaces/recording-config.ts`).
28179
+ * rows) and are the ONLY event surface the recorder has none. The in-RAM
28180
+ * playback markers it used to build were deleted on 2026-08-29 because nothing
28181
+ * ever read them. Event<->footage joins are by time, padded with the shared
28182
+ * `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
28124
28183
  */
28125
28184
  var RecordingStatusSchema = object({
28126
28185
  deviceId: number(),
@@ -14240,6 +14240,50 @@ var NodeProcessSchema = object({
14240
14240
  /** Wall-clock uptime (seconds). Parsed from `ps etime`. */
14241
14241
  uptimeSec: number()
14242
14242
  });
14243
+ /**
14244
+ * One retained container-memory reading.
14245
+ *
14246
+ * `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
14247
+ * a second clock: that is what makes "processes sum to X, container says Y"
14248
+ * subtractable per point rather than an eyeballed comparison of two series
14249
+ * sampled at different instants.
14250
+ *
14251
+ * A reduced window keeps the sample with the LARGEST `currentBytes` in each
14252
+ * bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
14253
+ * never coexisted, and a mean would smear away the peak this exists to find.
14254
+ */
14255
+ var ContainerMemoryPointSchema = object({
14256
+ /** Which hierarchy answered, so a reading is never ambiguous. */
14257
+ source: _enum(["cgroup-v2", "cgroup-v1"]),
14258
+ /** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
14259
+ currentBytes: number(),
14260
+ /** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
14261
+ limitBytes: number().nullable(),
14262
+ /** Anonymous pages: the closest thing to "what the processes allocated". */
14263
+ anonBytes: number().nullable(),
14264
+ /** Page cache. Charged to the cgroup, owned by no process. */
14265
+ fileBytes: number().nullable(),
14266
+ /**
14267
+ * Shared memory — and the field that explained the largest single surprise.
14268
+ * The i915 driver backs GPU buffers with shmem, so an inference pool or a
14269
+ * hardware-decode session holding DRM objects is charged HERE and appears
14270
+ * nowhere in a `ps` scan.
14271
+ */
14272
+ shmemBytes: number().nullable(),
14273
+ /** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
14274
+ slabBytes: number().nullable(),
14275
+ /**
14276
+ * Shrinkable i915 GEM object bytes, from debugfs.
14277
+ *
14278
+ * **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
14279
+ * component of `currentBytes` and must not be subtracted from it; it says
14280
+ * what put the shmem there, where `shmemBytes` only says how much.
14281
+ *
14282
+ * `null` wherever debugfs is not mounted — which is inside every camstack
14283
+ * container today — and on any node with no Intel GPU.
14284
+ */
14285
+ gpuShmemBytes: number().nullable()
14286
+ }).extend({ atMs: number() });
14243
14287
  var DumpHeapSnapshotInputSchema = object({
14244
14288
  /** The addon whose runner should dump a heap snapshot. */
14245
14289
  addonId: string() });
@@ -14303,6 +14347,21 @@ var NodeLoadSeriesSchema = object({
14303
14347
  /** One entry per function seen in the window, heaviest-first. */
14304
14348
  series: array(LoadFunctionSeriesSchema).readonly(),
14305
14349
  /**
14350
+ * The CONTAINER's memory over the same window, oldest-first.
14351
+ *
14352
+ * Sits next to `series` rather than in a method of its own because the whole
14353
+ * question is a subtraction: the per-process rows in `series` sum to one
14354
+ * number and this one is another, and an operator who has to issue two calls
14355
+ * to compare them will compare two different instants. Same reader, same
14356
+ * `sinceMs`, same `bucketMs`, same timestamps.
14357
+ *
14358
+ * **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
14359
+ * Mac, a bare-metal host, a container with the hierarchy hidden — reports no
14360
+ * points at all. A zero here would be indistinguishable from a healthy
14361
+ * container and is precisely the lie this field exists to avoid.
14362
+ */
14363
+ containerMemory: array(ContainerMemoryPointSchema).readonly(),
14364
+ /**
14306
14365
  * Width of one returned bucket, in ms. Equals the sampling cadence when no
14307
14366
  * reduction was needed — so a caller can always say what one point covers
14308
14367
  * without having to know whether it was reduced.
@@ -28117,10 +28176,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
28117
28176
  * recording config. NOTE on events (source of truth, R5/C3): this cap carries
28118
28177
  * NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
28119
28178
  * events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
28120
- * rows); the recorder's internal EventMap markers are ephemeral in-RAM
28121
- * annotations that are not exposed here and must not be treated as an event
28122
- * feed. Event<->footage joins are by time, padded with the shared `EVENT_PAD_MS`
28123
- * (`interfaces/recording-config.ts`).
28179
+ * rows) and are the ONLY event surface the recorder has none. The in-RAM
28180
+ * playback markers it used to build were deleted on 2026-08-29 because nothing
28181
+ * ever read them. Event<->footage joins are by time, padded with the shared
28182
+ * `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
28124
28183
  */
28125
28184
  var RecordingStatusSchema = object({
28126
28185
  deviceId: number(),
@@ -3,7 +3,7 @@ Object.defineProperties(exports, {
3
3
  [Symbol.toStringTag]: { value: "Module" }
4
4
  });
5
5
  //#endregion
6
- const require_dist = require("../dist-nBclHVR_.js");
6
+ const require_dist = require("../dist-D24orV6m.js");
7
7
  let node_crypto = require("node:crypto");
8
8
  //#region src/ha-export/topics.ts
9
9
  /**
@@ -1,4 +1,4 @@
1
- import { At as EventCategory, C as buildAddonRouteProvider, Et as string, N as deviceExportCapability, X as oauthIntegrationCapability, a as COCO_TO_MACRO, c as FanDirectionSchema, i as CAMERA_SWITCH_ORDER, l as HvacModeSchema, o as CameraSwitchIdSchema, p as addonRoutesCapability, pt as BaseAddon, t as AlarmArmModeSchema, u as MediaPlayerRepeatSchema, vt as nodePin } from "../dist-Dm7hAzfd.mjs";
1
+ import { At as EventCategory, C as buildAddonRouteProvider, Et as string, N as deviceExportCapability, X as oauthIntegrationCapability, a as COCO_TO_MACRO, c as FanDirectionSchema, i as CAMERA_SWITCH_ORDER, l as HvacModeSchema, o as CameraSwitchIdSchema, p as addonRoutesCapability, pt as BaseAddon, t as AlarmArmModeSchema, u as MediaPlayerRepeatSchema, vt as nodePin } from "../dist-BfdeH6US.mjs";
2
2
  import { createHmac, timingSafeEqual } from "node:crypto";
3
3
  //#region src/ha-export/topics.ts
4
4
  /**
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-provider-homeassistant",
3
- "version": "1.2.52",
3
+ "version": "1.2.54",
4
4
  "description": "Home Assistant device provider addon for CamStack",
5
5
  "keywords": [
6
6
  "camstack",