@camstack/addon-provider-homeassistant 1.2.642 → 1.2.644
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/dist/addon.js +1 -1
- package/dist/addon.mjs +1 -1
- package/dist/{ha-broker-source-D9_yzN2c.mjs → ha-broker-source-DmHRCdW2.mjs} +1972 -1118
- package/dist/{ha-broker-source-B6xSmZ6H.js → ha-broker-source-tDtT7Zi-.js} +1971 -1117
- package/dist/ha-export/ha-export.addon.js +6 -2
- package/dist/ha-export/ha-export.addon.mjs +6 -2
- package/package.json +4 -1
|
@@ -24,7 +24,7 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
|
|
|
24
24
|
enumerable: true
|
|
25
25
|
}) : target, mod));
|
|
26
26
|
//#endregion
|
|
27
|
-
const require_ha_broker_source = require("../ha-broker-source-
|
|
27
|
+
const require_ha_broker_source = require("../ha-broker-source-tDtT7Zi-.js");
|
|
28
28
|
let node_crypto = require("node:crypto");
|
|
29
29
|
require("node:zlib");
|
|
30
30
|
let node_fs = require("node:fs");
|
|
@@ -261,7 +261,7 @@ var DEVICE_KEY_PREFIX = "camstack-";
|
|
|
261
261
|
* The rationale that used to sit here — "numeric ids are reallocated by a
|
|
262
262
|
* re-sync, so a captured number would address whichever camera inherited
|
|
263
263
|
* it" — was FALSE and is deleted rather than softened.
|
|
264
|
-
* `allocateNextDeviceId` (`@camstack/system`,
|
|
264
|
+
* `allocateNextDeviceId` (`@camstack/server/system`,
|
|
265
265
|
* `device-meta-store.ts`) is a monotonic counter: it reads
|
|
266
266
|
* `nextDeviceId ?? 1` and writes `current + 1`. A freed id is never
|
|
267
267
|
* re-issued. The worst case after a re-adoption is an ORPHANED entity —
|
|
@@ -3485,6 +3485,10 @@ function controlEntitySpecs(slice, quantity) {
|
|
|
3485
3485
|
}, kindExtra];
|
|
3486
3486
|
}
|
|
3487
3487
|
var CAPS_NOT_EXPORTED = [
|
|
3488
|
+
{
|
|
3489
|
+
cap: "power-source",
|
|
3490
|
+
reason: "A manual admin recovery action (cut the power of a device that hangs) on a switch that is already exported as itself; publishing a restart button beside it would hand an ecosystem the means to cut a device off by mistake."
|
|
3491
|
+
},
|
|
3488
3492
|
{
|
|
3489
3493
|
cap: "pet-fountain",
|
|
3490
3494
|
reason: "A fountain is BUILT here from the loose entities Home Assistant already holds (a pump switch, two number boxes, a button), so exporting it back would publish a second copy of entities that already exist there. A dedicated mapping can follow when an ecosystem asks for the built device."
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
import {
|
|
1
|
+
import { B as consumableKindOf, Et as sendToExportedTarget, K as deviceExportCapability, Kt as isReadingQuantity, Vt as baseUnitOf, Yt as array, _ as PLUG_APPLIANCE_TYPES, bt as runExportedAction, c as COCO_TO_MACRO, d as ConsumableItemSchema, en as object, f as ConsumableStatusSchema, g as MediaPlayerRepeatSchema, gt as pruneDeletedEntities, h as HvacModeSchema, i as AlarmArmModeSchema, in as unknown, j as buildAddonRouteProvider, l as CameraSwitchIdSchema, m as FanDirectionSchema, nn as string, qt as nodePin, r as listHomeAssistantBrokers, s as CAMERA_SWITCH_ORDER, u as ConsumableFormSchema, un as EventCategory, ut as oauthIntegrationCapability, x as addonRoutesCapability, z as consumableFormOf, zt as BaseAddon } from "../ha-broker-source-DmHRCdW2.mjs";
|
|
2
2
|
import { createHmac, timingSafeEqual } from "node:crypto";
|
|
3
3
|
import "node:zlib";
|
|
4
4
|
import "node:fs";
|
|
@@ -233,7 +233,7 @@ var DEVICE_KEY_PREFIX = "camstack-";
|
|
|
233
233
|
* The rationale that used to sit here — "numeric ids are reallocated by a
|
|
234
234
|
* re-sync, so a captured number would address whichever camera inherited
|
|
235
235
|
* it" — was FALSE and is deleted rather than softened.
|
|
236
|
-
* `allocateNextDeviceId` (`@camstack/system`,
|
|
236
|
+
* `allocateNextDeviceId` (`@camstack/server/system`,
|
|
237
237
|
* `device-meta-store.ts`) is a monotonic counter: it reads
|
|
238
238
|
* `nextDeviceId ?? 1` and writes `current + 1`. A freed id is never
|
|
239
239
|
* re-issued. The worst case after a re-adoption is an ORPHANED entity —
|
|
@@ -3450,6 +3450,10 @@ function controlEntitySpecs(slice, quantity) {
|
|
|
3450
3450
|
}, kindExtra];
|
|
3451
3451
|
}
|
|
3452
3452
|
var CAPS_NOT_EXPORTED = [
|
|
3453
|
+
{
|
|
3454
|
+
cap: "power-source",
|
|
3455
|
+
reason: "A manual admin recovery action (cut the power of a device that hangs) on a switch that is already exported as itself; publishing a restart button beside it would hand an ecosystem the means to cut a device off by mistake."
|
|
3456
|
+
},
|
|
3453
3457
|
{
|
|
3454
3458
|
cap: "pet-fountain",
|
|
3455
3459
|
reason: "A fountain is BUILT here from the loose entities Home Assistant already holds (a pump switch, two number boxes, a button), so exporting it back would publish a second copy of entities that already exist there. A dedicated mapping can follow when an ecosystem asks for the built device."
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@camstack/addon-provider-homeassistant",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.644",
|
|
4
4
|
"description": "Home Assistant device provider addon for CamStack",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|
|
@@ -125,6 +125,9 @@
|
|
|
125
125
|
"bundle": {
|
|
126
126
|
"displayName": "Home Assistant",
|
|
127
127
|
"description": "Device provider (import) + native entity export (push). Two addons, one bundle, separate processes."
|
|
128
|
+
},
|
|
129
|
+
"requires": {
|
|
130
|
+
"server": ">=1.2.719"
|
|
128
131
|
}
|
|
129
132
|
},
|
|
130
133
|
"files": [
|