@camstack/addon-export-hap 1.2.132 → 1.2.134

package/dist/hap-export.addon.js

@@ -108386,22 +108386,43 @@ function syncStateToJson(map) {
 * capabilities bound to it — restricting coverage by type is precisely what
 * confined this exporter to cameras for its first three rounds.
 */
+/**
+* What an entry with no stored settings is read as — and what a camera
+* exported TODAY is built from. Exported so a spec can assert the one thing
+* that matters about it: it must resolve to NOT recording, or "off by default"
+* is true only for cameras exposed before the flip.
+*/
 var DEFAULT_DEVICE_SETTINGS = {
 	streamPreference: "auto",
-	hksvRecording: true
+	hksvRecording: false
 };
 /**
-* ON unless explicitly switched off — operator decision 2026-08-08 (flipped
-* from the launch default of off). ABSENT must resolve to ON or the flip is a
-* lie for every entry persisted before the field existed, so every read goes
-* through this one resolver (`!== false`), never a scattered `=== true`. The
-* cost that made off-by-default look prudent is measured and small on the only
-* branch the recorder accepts (copy: 0.7 % of a core / ~30 MB RSS, D84), and a
-* camera the recorder cannot copy refuses recording with a logged reason
-* rather than paying for a transcode.
+* OFF unless explicitly switched on — operator decision 2026-09-21, reversing
+* the 2026-08-08 flip:
+*
+* > *"il recording deve essere off di default, non deve essere attivo quando
+* > si esporta una camera su HKSV"*
+*
+* What changed is not the cost the earlier record argued about — recording on
+* the copy branch really is 0.7 % of a core and ~30 MB (D84), and cheap it
+* remains. What changed is that on-by-default made the switch **say something
+* the system was not doing**. Measured on 2026-09-21: 592, 587, 618 and 640
+* all reported HomeKit recording ON while the advertisement was WITHHELD
+* (`no-enabled-stream` — no enabled RTSP profile), so HomeKit never recorded
+* them and the tee had nothing to keep. The operator was being told four
+* cameras were recording because nobody had turned them off.
+*
+* Exposing a camera to HomeKit is a decision about EXPOSURE. Recording is a
+* second decision and now has to be made.
+*
+* ABSENT resolves OFF — the load-bearing case, for the same reason it was
+* before and with the opposite answer: a camera whose settings predate the
+* field, or that was exposed before today, was never asked about. Every read
+* goes through this one resolver (`=== true`), never a scattered `!== false`,
+* because those two disagree about exactly that case.
 */
 function resolveHksvRecording(settings) {
-	return settings?.hksvRecording !== false;
+	return settings?.hksvRecording === true;
 }
 /**
 * Whether this camera offers Apple's NEW camera service alongside the classic
@@ -109534,6 +109555,7 @@ function errMsg(err) {
 }
 //#endregion
 exports.DEFAULT_CLIP_RETENTION_DAYS = DEFAULT_CLIP_RETENTION_DAYS;
+exports.DEFAULT_DEVICE_SETTINGS = DEFAULT_DEVICE_SETTINGS;
 exports.EXPORT_HAP_ADDON_ID = EXPORT_HAP_ADDON_ID;
 exports.ExportHapAddon = ExportHapAddon;
 exports.default = ExportHapAddon;

package/dist/hap-export.addon.mjs

@@ -108376,22 +108376,43 @@ function syncStateToJson(map) {
 * capabilities bound to it — restricting coverage by type is precisely what
 * confined this exporter to cameras for its first three rounds.
 */
+/**
+* What an entry with no stored settings is read as — and what a camera
+* exported TODAY is built from. Exported so a spec can assert the one thing
+* that matters about it: it must resolve to NOT recording, or "off by default"
+* is true only for cameras exposed before the flip.
+*/
 var DEFAULT_DEVICE_SETTINGS = {
 	streamPreference: "auto",
-	hksvRecording: true
+	hksvRecording: false
 };
 /**
-* ON unless explicitly switched off — operator decision 2026-08-08 (flipped
-* from the launch default of off). ABSENT must resolve to ON or the flip is a
-* lie for every entry persisted before the field existed, so every read goes
-* through this one resolver (`!== false`), never a scattered `=== true`. The
-* cost that made off-by-default look prudent is measured and small on the only
-* branch the recorder accepts (copy: 0.7 % of a core / ~30 MB RSS, D84), and a
-* camera the recorder cannot copy refuses recording with a logged reason
-* rather than paying for a transcode.
+* OFF unless explicitly switched on — operator decision 2026-09-21, reversing
+* the 2026-08-08 flip:
+*
+* > *"il recording deve essere off di default, non deve essere attivo quando
+* > si esporta una camera su HKSV"*
+*
+* What changed is not the cost the earlier record argued about — recording on
+* the copy branch really is 0.7 % of a core and ~30 MB (D84), and cheap it
+* remains. What changed is that on-by-default made the switch **say something
+* the system was not doing**. Measured on 2026-09-21: 592, 587, 618 and 640
+* all reported HomeKit recording ON while the advertisement was WITHHELD
+* (`no-enabled-stream` — no enabled RTSP profile), so HomeKit never recorded
+* them and the tee had nothing to keep. The operator was being told four
+* cameras were recording because nobody had turned them off.
+*
+* Exposing a camera to HomeKit is a decision about EXPOSURE. Recording is a
+* second decision and now has to be made.
+*
+* ABSENT resolves OFF — the load-bearing case, for the same reason it was
+* before and with the opposite answer: a camera whose settings predate the
+* field, or that was exposed before today, was never asked about. Every read
+* goes through this one resolver (`=== true`), never a scattered `!== false`,
+* because those two disagree about exactly that case.
 */
 function resolveHksvRecording(settings) {
-	return settings?.hksvRecording !== false;
+	return settings?.hksvRecording === true;
 }
 /**
 * Whether this camera offers Apple's NEW camera service alongside the classic
@@ -109523,4 +109544,4 @@ function errMsg(err) {
 	return err instanceof Error ? err.message : String(err);
 }
 //#endregion
-export { DEFAULT_CLIP_RETENTION_DAYS, EXPORT_HAP_ADDON_ID, ExportHapAddon, ExportHapAddon as default, describeHksvCamera, unpublishAccessory as i, initHapStorage as n, publishStandalone as r, resolveClipRetentionDays, resolveHksvRecording, resolveKeepHomekitClips, resolveMultiTierService, deriveUsername as t };
+export { DEFAULT_CLIP_RETENTION_DAYS, DEFAULT_DEVICE_SETTINGS, EXPORT_HAP_ADDON_ID, ExportHapAddon, ExportHapAddon as default, describeHksvCamera, unpublishAccessory as i, initHapStorage as n, publishStandalone as r, resolveClipRetentionDays, resolveHksvRecording, resolveKeepHomekitClips, resolveMultiTierService, deriveUsername as t };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-export-hap",
-  "version": "1.2.132",
+  "version": "1.2.134",
   "description": "HomeKit (HAP) exporter for CamStack devices. Publishes each exposed device as its own HomeKit accessory: cameras and doorbells with SRTP streaming, HomeKit Secure Video, motion, two-way audio, PTZ and battery; switches, lights, locks and sensors through a capability→service table.",
   "keywords": [
     "camstack",