@camstack/addon-provider-homeassistant 1.2.65 → 1.2.66

package/dist/ha-export/ha-export.addon.js

@@ -20,17 +20,54 @@ let node_crypto = require("node:crypto");
 */
 /** Root of every topic. Namespaces the export inside HA's event bus. */
 var TOPIC_ROOT = "camstack";
-/** Prefix that turns a device's `stableId` into its HA `device_id`. */
+/** Prefix that turns a device's numeric id into its HA `device_id`. */
 var DEVICE_KEY_PREFIX = "camstack-";
 /**
-* The HA `device_id` for a camstack device.
-*
-* Derived from `stableId`, never from the numeric id: numeric ids are
-* reallocated by a re-sync, and an operator who re-adopts a camera would
-* get a second HA device with every automation pointing at the orphan.
+* The HA `device_id` for a camstack device. **THIS FILE OWNS THE RULE.**
+*
+* Derived from the NUMERIC device id, which is what the other three
+* ecosystem exports already key on: Alexa's `endpointId` is
+* `String(deviceId)`, HomeKit's accessory uuid is
+* `camstack:camera:<deviceId>` and Google's `id` is `String(deviceId)`.
+* Home Assistant was the only export keying on `stableId`, and `stableId`
+* is provider-internal — `(addonId, stableId)` is the addon-facing
+* identity in `device-meta-actions.ts`, not an identity meant to leave the
+* hub. This was the one place it leaked.
+*
+* The rationale that used to sit here — "numeric ids are reallocated by a
+* re-sync, so a captured number would address whichever camera inherited
+* it" — was FALSE and is deleted rather than softened.
+* `allocateNextDeviceId` (`@camstack/system`,
+* `device-meta-store.ts`) is a monotonic counter: it reads
+* `nextDeviceId ?? 1` and writes `current + 1`. A freed id is never
+* re-issued. The worst case after a re-adoption is an ORPHANED entity —
+* never a mis-addressed one — which is exactly what a changed `stableId`
+* produced too.
+*
+* The component MIRRORS this rule in `CamStackDevice.device_key`
+* (`custom_components/camstack/coordinator.py`), because the camera entity
+* is built from the export membership rather than pushed. Everywhere the
+* component receives a key it takes it verbatim (`dev.ids[0]` /
+* `entity_change.device_id`) instead of composing one. The two
+* compositions are pinned to the same literal by
+* `__tests__/entity-catalog.spec.ts` ("the cross-side identity contract")
+* and `tests/test_entities.py::test_the_device_key_matches_the_hub_rule`.
+*/
+function deviceKeyFor(deviceId) {
+	return `${DEVICE_KEY_PREFIX}${deviceId}`;
+}
+/**
+* The HA `device_id` for a SYNTHETIC device.
+*
+* Synthetic devices are built by the exporter and have no camstack device
+* behind them — `HaDevicePlan.deviceId` is `null` for one — so there is no
+* numeric id to key on and their own `synthetic-…` id IS their identity.
+* A separate builder rather than an overload: a caller that has a real
+* device must not be able to reach the string-keyed path by accident,
+* which is how a second HA device appears beside the first.
 */
-function deviceKeyFor(stableId) {
-	return `${DEVICE_KEY_PREFIX}${stableId}`;
+function syntheticDeviceKeyFor(syntheticId) {
+	return `${DEVICE_KEY_PREFIX}${syntheticId}`;
 }
 function stateTopic(deviceKey, entity) {
 	return `${TOPIC_ROOT}/${deviceKey}/${entity}`;
@@ -121,7 +158,7 @@ function toSlug(value) {
 * behind two url gates: a refusal for a credential in the authority and a
 * refusal for a loopback host. On 2026-08-14 the live registry was read:
 * `platform: camstack` held **165 entities and exactly two `camera` ones**
-* — one per exported camera, `unique_id` `camstack_<stableId>_camera`.
+* — one per exported camera, `unique_id` `camstack_<deviceId>_camera`.
 * None of the twelve announced stream components existed.
 *
 * They never could. `custom_components/camstack/camera.py` builds its
@@ -146,8 +183,9 @@ function toSlug(value) {
 *
 * The component's membership entity IS the adaptive stream: it negotiates
 * no target, it is the device's primary camera (`_attr_name = None`), and
-* it has carried `camstack_<stableId>_camera` since the integration
-* shipped. Announcing a component for it would claim the same
+* it carries `camstack_<deviceId>_camera` — the component builds that one
+* itself, from the export membership, mirroring `deviceKeyFor`'s numeric
+* rule. Announcing a component for it would claim the same
 * `unique_id` — Home Assistant keys its registry on
 * `(platform, integration, unique_id)` — and one of the two would lose the
 * race and be dropped with a "does not generate unique IDs" error. So the
@@ -909,7 +947,7 @@ function buildNativeComponent(input) {
 	return {
 		component: {
 			platform: native.platform,
-			unique_id: `${input.stableId}_${derivedEntityId(input.capName)}`,
+			unique_id: `${input.deviceId}_${derivedEntityId(input.capName)}`,
 			name: input.label,
 			...primary.control,
 			...native.deviceClass !== void 0 ? { device_class: native.deviceClass } : {},
@@ -1136,10 +1174,10 @@ var MIRED_RANGE = {
 	step: 1
 };
 function buildComponent(device, spec) {
-	const deviceKey = deviceKeyFor(device.stableId);
+	const deviceKey = deviceKeyFor(device.id);
 	return {
 		platform: spec.platform,
-		unique_id: `${device.stableId}_${spec.uniqueSuffix ?? spec.entity}`,
+		unique_id: `${device.id}_${spec.uniqueSuffix ?? spec.entity}`,
 		name: spec.label,
 		...STATELESS_PLATFORMS.has(spec.platform) ? {} : { state_topic: stateTopic(deviceKey, spec.entity) },
 		...spec.writable === true && COMMANDABLE_PLATFORMS.has(spec.platform) ? { command_topic: commandTopic(deviceKey, spec.entity) } : {},
@@ -1164,7 +1202,7 @@ function buildComponent(device, spec) {
 }
 function deviceBlock(device) {
 	return {
-		ids: [deviceKeyFor(device.stableId)],
+		ids: [deviceKeyFor(device.id)],
 		name: device.name,
 		mf: device.manufacturer ?? "CamStack",
 		mdl: device.model ?? device.type
@@ -1542,7 +1580,7 @@ function assemble(device, specs) {
 	const cmps = {};
 	for (const spec of specs) cmps[toComponentKey(spec.platform, spec.entity)] = buildComponent(device, spec);
 	return {
-		deviceKey: deviceKeyFor(device.stableId),
+		deviceKey: deviceKeyFor(device.id),
 		deviceId: device.id,
 		dev: deviceBlock(device),
 		cmps
@@ -2916,8 +2954,8 @@ function buildDerivedPlan(device, options = UNNEGOTIATED_PLAN_OPTIONS) {
 		const mapping = CAP_ENTITY_MAP[cap];
 		const platform = nativePlatformFor(cap);
 		const plan = mapping === void 0 || platform === null || !options.platforms.has(platform) ? null : buildNativeComponent({
-			deviceKey: deviceKeyFor(device.stableId),
-			stableId: device.stableId,
+			deviceKey: deviceKeyFor(device.id),
+			deviceId: device.id,
 			capName: cap,
 			label: humanise(cap),
 			slice: device.capSlices?.[cap],
@@ -5127,9 +5165,13 @@ function cameraStatusToken(input) {
 * restart.
 *
 * The identity rules are the same wire format as every other device
-* (`../CLAUDE.md`): `device_id` is `camstack-<stableId>` and `unique_id` is
-* `<stableId>_<entity>`. The stable ids here are prefixed `synthetic-` so they
-* can never collide with a real device's, whatever a provider mints.
+* (`../CLAUDE.md`), with the one difference the category forces: a real device
+* is keyed on its NUMERIC id (`device_id` `camstack-<deviceId>`, `unique_id`
+* `<deviceId>_<entity>`) and these have no numeric id at all, so their own
+* `synthetic-…` id is their identity — `device_id` is `camstack-<syntheticId>`
+* and `unique_id` is `<syntheticId>_<entity>`, built through
+* {@link syntheticDeviceKeyFor}. The ids are prefixed `synthetic-` so they can
+* never collide with a numeric key, whatever the counter reaches.
 */
 /** The stable id of the notification-centre device. A WIRE FORMAT. */
 var NOTIFICATION_CENTER_STABLE_ID = "synthetic-notification-center";
@@ -5138,7 +5180,7 @@ var SERVER_STABLE_ID = "synthetic-server";
 var SYNTHETIC_STABLE_IDS = [NOTIFICATION_CENTER_STABLE_ID, SERVER_STABLE_ID];
 /** Is this device key one of ours? Used by the command route. */
 function isSyntheticDeviceKey(deviceKey) {
-	return SYNTHETIC_STABLE_IDS.some((id) => deviceKeyFor(id) === deviceKey);
+	return SYNTHETIC_STABLE_IDS.some((id) => syntheticDeviceKeyFor(id) === deviceKey);
 }
 /**
 * Pure derivation of the three alert entities (Task D1) — the conditions
@@ -5168,12 +5210,12 @@ function deriveAlertSummary(alerts) {
 * a rule they want to reach. Shipping them disabled would repeat the bug that
 * exported a thermometer's temperature switched off.
 */
-function buildComponents(stableId, specs) {
-	const deviceKey = deviceKeyFor(stableId);
+function buildComponents(syntheticId, specs) {
+	const deviceKey = syntheticDeviceKeyFor(syntheticId);
 	const cmps = {};
 	for (const spec of specs) cmps[toComponentKey(spec.platform, spec.entity)] = {
 		platform: spec.platform,
-		unique_id: `${stableId}_${spec.entity}`,
+		unique_id: `${syntheticId}_${spec.entity}`,
 		name: spec.label,
 		...spec.platform === "button" ? {} : { state_topic: stateTopic(deviceKey, spec.entity) },
 		...spec.writable === true ? { command_topic: commandTopic(deviceKey, spec.entity) } : {},
@@ -5189,17 +5231,17 @@ function buildComponents(stableId, specs) {
 	};
 	return cmps;
 }
-function plan(stableId, name, specs) {
+function plan(syntheticId, name, specs) {
 	return {
-		deviceKey: deviceKeyFor(stableId),
+		deviceKey: syntheticDeviceKeyFor(syntheticId),
 		deviceId: null,
 		dev: {
-			ids: [deviceKeyFor(stableId)],
+			ids: [syntheticDeviceKeyFor(syntheticId)],
 			name,
 			mf: "CamStack",
 			mdl: "Synthetic"
 		},
-		cmps: buildComponents(stableId, specs)
+		cmps: buildComponents(syntheticId, specs)
 	};
 }
 /**
@@ -5570,8 +5612,8 @@ function projectTriggerFacts(deviceKey, entityFor, t) {
 * whatever it was 300 seconds ago and read as a stalled machine.
 */
 function projectSynthetic(input, nowMs) {
-	const nc = deviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
-	const srv = deviceKeyFor(SERVER_STABLE_ID);
+	const nc = syntheticDeviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
+	const srv = syntheticDeviceKeyFor(SERVER_STABLE_ID);
 	const online = input.nodes.filter((node) => node.online);
 	const values = [
 		{
@@ -6537,7 +6579,7 @@ var HaExportAddon = class extends require_dist.BaseAddon {
 				* a camera's `snooze` select uses, over the SAME `snoozes` read this
 				* pass already made — one expression of the rule, not two.
 				*/
-				const ncKey = deviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
+				const ncKey = syntheticDeviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
 				await this.pushSynthetic([...projectSynthetic(synthetic, Date.now()), ...projectSnooze(ncKey, latestGlobalSnoozeWindow(snoozes))], [...enabled]);
 			}
 			this.ctx.logger.info("ha-export: reconciled", { meta: {
@@ -6929,7 +6971,6 @@ var HaExportAddon = class extends require_dist.BaseAddon {
 		const model = readString(device.metadata ?? {}, "model");
 		return {
 			id: device.id,
-			stableId: device.stableId,
 			name: device.name,
 			type: device.type,
 			...manufacturer !== null ? { manufacturer } : {},
@@ -7393,7 +7434,7 @@ var HaExportAddon = class extends require_dist.BaseAddon {
 			* `createSnooze`/`cancelSnooze` directly, `scope: 'all'`, never a
 			* store of its own.
 			*/
-			if (parsed.deviceKey === deviceKeyFor("synthetic-notification-center") && parsed.entity === "snooze") {
+			if (parsed.deviceKey === syntheticDeviceKeyFor("synthetic-notification-center") && parsed.entity === "snooze") {
 				if (!SNOOZE_OPTIONS.includes(value)) {
 					this.ctx.logger.warn("ha-export: dropping a global snooze command, unknown option", { meta: {
 						topic,
@@ -7679,7 +7720,7 @@ var HaExportAddon = class extends require_dist.BaseAddon {
 	async republishGlobalSnooze() {
 		try {
 			const { snoozes } = await this.ctx.api.notificationRules.listSnoozes.query({});
-			const ncKey = deviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
+			const ncKey = syntheticDeviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
 			await this.pushSynthetic(projectSnooze(ncKey, latestGlobalSnoozeWindow(snoozes)), this.enabledBrokerIds());
 		} catch (err) {
 			this.ctx.logger.warn("ha-export: could not republish the global snooze after a write from Home Assistant", { meta: { error: errMsg(err) } });

package/dist/ha-export/ha-export.addon.mjs

@@ -15,17 +15,54 @@ import { createHmac, timingSafeEqual } from "node:crypto";
 */
 /** Root of every topic. Namespaces the export inside HA's event bus. */
 var TOPIC_ROOT = "camstack";
-/** Prefix that turns a device's `stableId` into its HA `device_id`. */
+/** Prefix that turns a device's numeric id into its HA `device_id`. */
 var DEVICE_KEY_PREFIX = "camstack-";
 /**
-* The HA `device_id` for a camstack device.
-*
-* Derived from `stableId`, never from the numeric id: numeric ids are
-* reallocated by a re-sync, and an operator who re-adopts a camera would
-* get a second HA device with every automation pointing at the orphan.
+* The HA `device_id` for a camstack device. **THIS FILE OWNS THE RULE.**
+*
+* Derived from the NUMERIC device id, which is what the other three
+* ecosystem exports already key on: Alexa's `endpointId` is
+* `String(deviceId)`, HomeKit's accessory uuid is
+* `camstack:camera:<deviceId>` and Google's `id` is `String(deviceId)`.
+* Home Assistant was the only export keying on `stableId`, and `stableId`
+* is provider-internal — `(addonId, stableId)` is the addon-facing
+* identity in `device-meta-actions.ts`, not an identity meant to leave the
+* hub. This was the one place it leaked.
+*
+* The rationale that used to sit here — "numeric ids are reallocated by a
+* re-sync, so a captured number would address whichever camera inherited
+* it" — was FALSE and is deleted rather than softened.
+* `allocateNextDeviceId` (`@camstack/system`,
+* `device-meta-store.ts`) is a monotonic counter: it reads
+* `nextDeviceId ?? 1` and writes `current + 1`. A freed id is never
+* re-issued. The worst case after a re-adoption is an ORPHANED entity —
+* never a mis-addressed one — which is exactly what a changed `stableId`
+* produced too.
+*
+* The component MIRRORS this rule in `CamStackDevice.device_key`
+* (`custom_components/camstack/coordinator.py`), because the camera entity
+* is built from the export membership rather than pushed. Everywhere the
+* component receives a key it takes it verbatim (`dev.ids[0]` /
+* `entity_change.device_id`) instead of composing one. The two
+* compositions are pinned to the same literal by
+* `__tests__/entity-catalog.spec.ts` ("the cross-side identity contract")
+* and `tests/test_entities.py::test_the_device_key_matches_the_hub_rule`.
+*/
+function deviceKeyFor(deviceId) {
+	return `${DEVICE_KEY_PREFIX}${deviceId}`;
+}
+/**
+* The HA `device_id` for a SYNTHETIC device.
+*
+* Synthetic devices are built by the exporter and have no camstack device
+* behind them — `HaDevicePlan.deviceId` is `null` for one — so there is no
+* numeric id to key on and their own `synthetic-…` id IS their identity.
+* A separate builder rather than an overload: a caller that has a real
+* device must not be able to reach the string-keyed path by accident,
+* which is how a second HA device appears beside the first.
 */
-function deviceKeyFor(stableId) {
-	return `${DEVICE_KEY_PREFIX}${stableId}`;
+function syntheticDeviceKeyFor(syntheticId) {
+	return `${DEVICE_KEY_PREFIX}${syntheticId}`;
 }
 function stateTopic(deviceKey, entity) {
 	return `${TOPIC_ROOT}/${deviceKey}/${entity}`;
@@ -116,7 +153,7 @@ function toSlug(value) {
 * behind two url gates: a refusal for a credential in the authority and a
 * refusal for a loopback host. On 2026-08-14 the live registry was read:
 * `platform: camstack` held **165 entities and exactly two `camera` ones**
-* — one per exported camera, `unique_id` `camstack_<stableId>_camera`.
+* — one per exported camera, `unique_id` `camstack_<deviceId>_camera`.
 * None of the twelve announced stream components existed.
 *
 * They never could. `custom_components/camstack/camera.py` builds its
@@ -141,8 +178,9 @@ function toSlug(value) {
 *
 * The component's membership entity IS the adaptive stream: it negotiates
 * no target, it is the device's primary camera (`_attr_name = None`), and
-* it has carried `camstack_<stableId>_camera` since the integration
-* shipped. Announcing a component for it would claim the same
+* it carries `camstack_<deviceId>_camera` — the component builds that one
+* itself, from the export membership, mirroring `deviceKeyFor`'s numeric
+* rule. Announcing a component for it would claim the same
 * `unique_id` — Home Assistant keys its registry on
 * `(platform, integration, unique_id)` — and one of the two would lose the
 * race and be dropped with a "does not generate unique IDs" error. So the
@@ -904,7 +942,7 @@ function buildNativeComponent(input) {
 	return {
 		component: {
 			platform: native.platform,
-			unique_id: `${input.stableId}_${derivedEntityId(input.capName)}`,
+			unique_id: `${input.deviceId}_${derivedEntityId(input.capName)}`,
 			name: input.label,
 			...primary.control,
 			...native.deviceClass !== void 0 ? { device_class: native.deviceClass } : {},
@@ -1131,10 +1169,10 @@ var MIRED_RANGE = {
 	step: 1
 };
 function buildComponent(device, spec) {
-	const deviceKey = deviceKeyFor(device.stableId);
+	const deviceKey = deviceKeyFor(device.id);
 	return {
 		platform: spec.platform,
-		unique_id: `${device.stableId}_${spec.uniqueSuffix ?? spec.entity}`,
+		unique_id: `${device.id}_${spec.uniqueSuffix ?? spec.entity}`,
 		name: spec.label,
 		...STATELESS_PLATFORMS.has(spec.platform) ? {} : { state_topic: stateTopic(deviceKey, spec.entity) },
 		...spec.writable === true && COMMANDABLE_PLATFORMS.has(spec.platform) ? { command_topic: commandTopic(deviceKey, spec.entity) } : {},
@@ -1159,7 +1197,7 @@ function buildComponent(device, spec) {
 }
 function deviceBlock(device) {
 	return {
-		ids: [deviceKeyFor(device.stableId)],
+		ids: [deviceKeyFor(device.id)],
 		name: device.name,
 		mf: device.manufacturer ?? "CamStack",
 		mdl: device.model ?? device.type
@@ -1537,7 +1575,7 @@ function assemble(device, specs) {
 	const cmps = {};
 	for (const spec of specs) cmps[toComponentKey(spec.platform, spec.entity)] = buildComponent(device, spec);
 	return {
-		deviceKey: deviceKeyFor(device.stableId),
+		deviceKey: deviceKeyFor(device.id),
 		deviceId: device.id,
 		dev: deviceBlock(device),
 		cmps
@@ -2911,8 +2949,8 @@ function buildDerivedPlan(device, options = UNNEGOTIATED_PLAN_OPTIONS) {
 		const mapping = CAP_ENTITY_MAP[cap];
 		const platform = nativePlatformFor(cap);
 		const plan = mapping === void 0 || platform === null || !options.platforms.has(platform) ? null : buildNativeComponent({
-			deviceKey: deviceKeyFor(device.stableId),
-			stableId: device.stableId,
+			deviceKey: deviceKeyFor(device.id),
+			deviceId: device.id,
 			capName: cap,
 			label: humanise(cap),
 			slice: device.capSlices?.[cap],
@@ -5122,9 +5160,13 @@ function cameraStatusToken(input) {
 * restart.
 *
 * The identity rules are the same wire format as every other device
-* (`../CLAUDE.md`): `device_id` is `camstack-<stableId>` and `unique_id` is
-* `<stableId>_<entity>`. The stable ids here are prefixed `synthetic-` so they
-* can never collide with a real device's, whatever a provider mints.
+* (`../CLAUDE.md`), with the one difference the category forces: a real device
+* is keyed on its NUMERIC id (`device_id` `camstack-<deviceId>`, `unique_id`
+* `<deviceId>_<entity>`) and these have no numeric id at all, so their own
+* `synthetic-…` id is their identity — `device_id` is `camstack-<syntheticId>`
+* and `unique_id` is `<syntheticId>_<entity>`, built through
+* {@link syntheticDeviceKeyFor}. The ids are prefixed `synthetic-` so they can
+* never collide with a numeric key, whatever the counter reaches.
 */
 /** The stable id of the notification-centre device. A WIRE FORMAT. */
 var NOTIFICATION_CENTER_STABLE_ID = "synthetic-notification-center";
@@ -5133,7 +5175,7 @@ var SERVER_STABLE_ID = "synthetic-server";
 var SYNTHETIC_STABLE_IDS = [NOTIFICATION_CENTER_STABLE_ID, SERVER_STABLE_ID];
 /** Is this device key one of ours? Used by the command route. */
 function isSyntheticDeviceKey(deviceKey) {
-	return SYNTHETIC_STABLE_IDS.some((id) => deviceKeyFor(id) === deviceKey);
+	return SYNTHETIC_STABLE_IDS.some((id) => syntheticDeviceKeyFor(id) === deviceKey);
 }
 /**
 * Pure derivation of the three alert entities (Task D1) — the conditions
@@ -5163,12 +5205,12 @@ function deriveAlertSummary(alerts) {
 * a rule they want to reach. Shipping them disabled would repeat the bug that
 * exported a thermometer's temperature switched off.
 */
-function buildComponents(stableId, specs) {
-	const deviceKey = deviceKeyFor(stableId);
+function buildComponents(syntheticId, specs) {
+	const deviceKey = syntheticDeviceKeyFor(syntheticId);
 	const cmps = {};
 	for (const spec of specs) cmps[toComponentKey(spec.platform, spec.entity)] = {
 		platform: spec.platform,
-		unique_id: `${stableId}_${spec.entity}`,
+		unique_id: `${syntheticId}_${spec.entity}`,
 		name: spec.label,
 		...spec.platform === "button" ? {} : { state_topic: stateTopic(deviceKey, spec.entity) },
 		...spec.writable === true ? { command_topic: commandTopic(deviceKey, spec.entity) } : {},
@@ -5184,17 +5226,17 @@ function buildComponents(stableId, specs) {
 	};
 	return cmps;
 }
-function plan(stableId, name, specs) {
+function plan(syntheticId, name, specs) {
 	return {
-		deviceKey: deviceKeyFor(stableId),
+		deviceKey: syntheticDeviceKeyFor(syntheticId),
 		deviceId: null,
 		dev: {
-			ids: [deviceKeyFor(stableId)],
+			ids: [syntheticDeviceKeyFor(syntheticId)],
 			name,
 			mf: "CamStack",
 			mdl: "Synthetic"
 		},
-		cmps: buildComponents(stableId, specs)
+		cmps: buildComponents(syntheticId, specs)
 	};
 }
 /**
@@ -5565,8 +5607,8 @@ function projectTriggerFacts(deviceKey, entityFor, t) {
 * whatever it was 300 seconds ago and read as a stalled machine.
 */
 function projectSynthetic(input, nowMs) {
-	const nc = deviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
-	const srv = deviceKeyFor(SERVER_STABLE_ID);
+	const nc = syntheticDeviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
+	const srv = syntheticDeviceKeyFor(SERVER_STABLE_ID);
 	const online = input.nodes.filter((node) => node.online);
 	const values = [
 		{
@@ -6532,7 +6574,7 @@ var HaExportAddon = class extends BaseAddon {
 				* a camera's `snooze` select uses, over the SAME `snoozes` read this
 				* pass already made — one expression of the rule, not two.
 				*/
-				const ncKey = deviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
+				const ncKey = syntheticDeviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
 				await this.pushSynthetic([...projectSynthetic(synthetic, Date.now()), ...projectSnooze(ncKey, latestGlobalSnoozeWindow(snoozes))], [...enabled]);
 			}
 			this.ctx.logger.info("ha-export: reconciled", { meta: {
@@ -6924,7 +6966,6 @@ var HaExportAddon = class extends BaseAddon {
 		const model = readString(device.metadata ?? {}, "model");
 		return {
 			id: device.id,
-			stableId: device.stableId,
 			name: device.name,
 			type: device.type,
 			...manufacturer !== null ? { manufacturer } : {},
@@ -7388,7 +7429,7 @@ var HaExportAddon = class extends BaseAddon {
 			* `createSnooze`/`cancelSnooze` directly, `scope: 'all'`, never a
 			* store of its own.
 			*/
-			if (parsed.deviceKey === deviceKeyFor("synthetic-notification-center") && parsed.entity === "snooze") {
+			if (parsed.deviceKey === syntheticDeviceKeyFor("synthetic-notification-center") && parsed.entity === "snooze") {
 				if (!SNOOZE_OPTIONS.includes(value)) {
 					this.ctx.logger.warn("ha-export: dropping a global snooze command, unknown option", { meta: {
 						topic,
@@ -7674,7 +7715,7 @@ var HaExportAddon = class extends BaseAddon {
 	async republishGlobalSnooze() {
 		try {
 			const { snoozes } = await this.ctx.api.notificationRules.listSnoozes.query({});
-			const ncKey = deviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
+			const ncKey = syntheticDeviceKeyFor(NOTIFICATION_CENTER_STABLE_ID);
 			await this.pushSynthetic(projectSnooze(ncKey, latestGlobalSnoozeWindow(snoozes)), this.enabledBrokerIds());
 		} catch (err) {
 			this.ctx.logger.warn("ha-export: could not republish the global snooze after a write from Home Assistant", { meta: { error: errMsg(err) } });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-homeassistant",
-  "version": "1.2.65",
+  "version": "1.2.66",
   "description": "Home Assistant device provider addon for CamStack",
   "keywords": [
     "camstack",