@camstack/addon-provider-homeassistant 1.2.76 → 1.2.78

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

@@ -1538,13 +1538,31 @@ function cameraSpecs(device) {
 			icon: "mdi:counter",
 			enabledByDefault: false
 		});
-		if (LABELLED_MACROS.includes(macro)) specs.push({
-			entity: `${macro}_last_label`,
-			platform: "sensor",
-			label: `${label} last label`,
-			icon: "mdi:tag",
-			enabledByDefault: true
-		});
+		if (LABELLED_MACROS.includes(macro)) specs.push(
+			{
+				entity: `${macro}_last_label`,
+				platform: "sensor",
+				label: `${label} last label`,
+				icon: "mdi:tag",
+				enabledByDefault: true
+			},
+			/**
+			* The identification OCCURRENCE — moves on every recognition,
+			* including a repeat of the SAME name (an unchanged `last_label`
+			* is deduped by the push client, and an identical value is not a
+			* state change in HA). This is the entity an automation's trigger
+			* binds to; the label value arrives in the same batch, ordered
+			* first. Enabled for the same reason `<macro>_last_detection` is:
+			* it IS the automation hook, not a diagnostic.
+			*/
+			{
+				entity: `${macro}_last_label_at`,
+				platform: "sensor",
+				label: `${label} last label at`,
+				deviceClass: "timestamp",
+				enabledByDefault: true
+			}
+		);
 	}
 	/**
 	* The live picture — every stream the hub lists EXCEPT the adaptive one,
@@ -4886,10 +4904,29 @@ function projectTrackLifecycle(deviceKey, track, mediaUrl) {
 	* topic nothing is subscribed to.
 	*/
 	const label = track.plateText ?? track.label;
-	if (label !== void 0 && label.length > 0 && LABELLED_MACROS.includes(macro)) values.push({
-		topic: stateTopic(deviceKey, `${macro}_last_label`),
-		value: label
-	});
+	if (label !== void 0 && label.length > 0 && LABELLED_MACROS.includes(macro)) {
+		values.push({
+			topic: stateTopic(deviceKey, `${macro}_last_label`),
+			value: label
+		});
+		/**
+		* The occurrence STAMP. A second recognition of the same person is a
+		* real occurrence, but it is invisible on `_last_label`: the push
+		* client dedups per topic, and an identical value is not a state
+		* change in Home Assistant anyway — a state-trigger automation would
+		* never re-fire. The stamp is the value that always moves, so an
+		* automation binds its trigger HERE and reads `<macro>_last_label`
+		* for the name — which is ordered BEFORE the stamp in this array, so
+		* it is already applied when the trigger fires. HA's `event` platform
+		* would be the native home for this, but no released component builds
+		* it (`component-support.ts`): announcing one yields a warning in
+		* HA's log and NO entity — the exact D152 zero-entities failure.
+		*/
+		values.push({
+			topic: stateTopic(deviceKey, `${macro}_last_label_at`),
+			value: iso(track.lastSeen)
+		});
+	}
 	if (mediaUrl !== null) values.push({
 		topic: stateTopic(deviceKey, "last_image"),
 		value: mediaUrl

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

@@ -1533,13 +1533,31 @@ function cameraSpecs(device) {
 			icon: "mdi:counter",
 			enabledByDefault: false
 		});
-		if (LABELLED_MACROS.includes(macro)) specs.push({
-			entity: `${macro}_last_label`,
-			platform: "sensor",
-			label: `${label} last label`,
-			icon: "mdi:tag",
-			enabledByDefault: true
-		});
+		if (LABELLED_MACROS.includes(macro)) specs.push(
+			{
+				entity: `${macro}_last_label`,
+				platform: "sensor",
+				label: `${label} last label`,
+				icon: "mdi:tag",
+				enabledByDefault: true
+			},
+			/**
+			* The identification OCCURRENCE — moves on every recognition,
+			* including a repeat of the SAME name (an unchanged `last_label`
+			* is deduped by the push client, and an identical value is not a
+			* state change in HA). This is the entity an automation's trigger
+			* binds to; the label value arrives in the same batch, ordered
+			* first. Enabled for the same reason `<macro>_last_detection` is:
+			* it IS the automation hook, not a diagnostic.
+			*/
+			{
+				entity: `${macro}_last_label_at`,
+				platform: "sensor",
+				label: `${label} last label at`,
+				deviceClass: "timestamp",
+				enabledByDefault: true
+			}
+		);
 	}
 	/**
 	* The live picture — every stream the hub lists EXCEPT the adaptive one,
@@ -4881,10 +4899,29 @@ function projectTrackLifecycle(deviceKey, track, mediaUrl) {
 	* topic nothing is subscribed to.
 	*/
 	const label = track.plateText ?? track.label;
-	if (label !== void 0 && label.length > 0 && LABELLED_MACROS.includes(macro)) values.push({
-		topic: stateTopic(deviceKey, `${macro}_last_label`),
-		value: label
-	});
+	if (label !== void 0 && label.length > 0 && LABELLED_MACROS.includes(macro)) {
+		values.push({
+			topic: stateTopic(deviceKey, `${macro}_last_label`),
+			value: label
+		});
+		/**
+		* The occurrence STAMP. A second recognition of the same person is a
+		* real occurrence, but it is invisible on `_last_label`: the push
+		* client dedups per topic, and an identical value is not a state
+		* change in Home Assistant anyway — a state-trigger automation would
+		* never re-fire. The stamp is the value that always moves, so an
+		* automation binds its trigger HERE and reads `<macro>_last_label`
+		* for the name — which is ordered BEFORE the stamp in this array, so
+		* it is already applied when the trigger fires. HA's `event` platform
+		* would be the native home for this, but no released component builds
+		* it (`component-support.ts`): announcing one yields a warning in
+		* HA's log and NO entity — the exact D152 zero-entities failure.
+		*/
+		values.push({
+			topic: stateTopic(deviceKey, `${macro}_last_label_at`),
+			value: iso(track.lastSeen)
+		});
+	}
 	if (mediaUrl !== null) values.push({
 		topic: stateTopic(deviceKey, "last_image"),
 		value: mediaUrl

package/package.json

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