homebridge-mynest 1.0.0 → 2.0.0

package/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 All notable changes to this project are documented here. From the first release onward, [release-please](https://github.com/googleapis/release-please) owns this file — do not hand-edit version headings after `0.1.0` ships.
 
+## [2.0.0](https://github.com/tbaur/homebridge-mynest/compare/v1.1.0...v2.0.0) (2026-08-05)
+
+
+### ⚠ BREAKING CHANGES
+
+* Homebridge 1.x is no longer supported. Requires Homebridge 2.x and Node.js 22 or newer, which is what Homebridge 2 itself requires.
+
+### Features
+
+* harden for Homebridge 2 — breaking release to 2.0.0 ([#29](https://github.com/tbaur/homebridge-mynest/issues/29)) ([02a2b7d](https://github.com/tbaur/homebridge-mynest/commit/02a2b7de0da39db36a4884f010534ab9a095daa5))
+
+## [1.1.0](https://github.com/tbaur/homebridge-mynest/compare/v1.0.0...v1.1.0) (2026-08-01)
+
+
+### Features
+
+* allow diagnostics interval up to 24h as a number field ([#27](https://github.com/tbaur/homebridge-mynest/issues/27)) ([9f988f7](https://github.com/tbaur/homebridge-mynest/commit/9f988f7d2cc21c5e6e072ce1914b0d767aa0168e))
+
 ## [1.0.0](https://github.com/tbaur/homebridge-mynest/compare/v0.1.10...v1.0.0) (2026-07-31)
 
 
@@ -79,8 +97,6 @@ All notable changes to this project are documented here. From the first release
 
 * show Ignored Device IDs input in Homebridge UI ([#3](https://github.com/tbaur/homebridge-mynest/issues/3)) ([0e7d966](https://github.com/tbaur/homebridge-mynest/commit/0e7d9668ae1e9dc01da5fd5e04c8aceeae361fe6))
 
-## [Unreleased]
-
 ## 0.1.0
 
 Initial public release of **homebridge-mynest**.

package/README.md

@@ -3,8 +3,8 @@
 [![Tests](https://github.com/tbaur/homebridge-mynest/actions/workflows/test.yml/badge.svg)](https://github.com/tbaur/homebridge-mynest/actions/workflows/test.yml)
 [![npm version](https://img.shields.io/npm/v/homebridge-mynest?style=flat-square)](https://www.npmjs.com/package/homebridge-mynest)
 [![npm downloads](https://img.shields.io/npm/dt/homebridge-mynest?style=flat-square)](https://www.npmjs.com/package/homebridge-mynest)
-[![Node.js](https://img.shields.io/badge/node-%3E%3D20-green)](https://nodejs.org)
-[![Homebridge](https://img.shields.io/badge/homebridge-%3E%3D1.6.0%20%7C%7C%202.x-purple)](https://homebridge.io)
+[![Node.js](https://img.shields.io/badge/node-22%20%7C%7C%2024-green)](https://nodejs.org)
+[![Homebridge](https://img.shields.io/badge/homebridge-2.x-purple)](https://homebridge.io)
 [![License](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE)
 
 Expose Nest thermostats, Nest Protect smoke/CO alarms, and Nest Temperature Sensors in Apple HomeKit through Homebridge, using a **Nest Account** access token only.
@@ -33,10 +33,10 @@ Expose Nest thermostats, Nest Protect smoke/CO alarms, and Nest Temperature Sens
 ### Quality
 
 <!-- Canonical test count lives here only; keep other docs number-free to avoid multi-place updates. -->
-- **Homebridge 2 safe** — Live updates use stored getters + `updateValue(...)`, not removed `getValue()` or stale `.value` reads
-- **452 Tests** — Jest suite with an 80% coverage gate across statements, branches, functions, and lines
-- **Strict TypeScript** — `strict` mode with unused locals/params and no implicit returns
-- **Secret hygiene** — Access tokens are redacted from logs
+- **Built for Homebridge 2** — Live updates use stored getters + `updateValue(...)`, not the removed `getValue()` or stale `.value` reads
+- **576 tests** — Jest suite with a per-area coverage floor on every source directory (statements, branches, functions, and lines), and a CI step that fails if the suite leaks an open handle
+- **Strict TypeScript** — `strict` mode with unused locals/params and no implicit returns, plus type-aware linting (no floating promises)
+- **Secret hygiene** — Access tokens are redacted from logs, and untrusted Nest responses cannot reach `Object.prototype`
 - **No analytics** — Zero tracking or data collection
 
 ## Quick Start
@@ -53,7 +53,7 @@ npm install -g homebridge-mynest
 
 ### 2. Get a Nest Account token
 
-You need a Nest Account (not Google-only) access token from [home.nest.com/session](https://home.nest.com/session). Steps and threat model: [docs/AUTH.md](docs/AUTH.md).
+You need a Nest Account (not Google-only) access token from [home.nest.com/session](https://home.nest.com/session). Steps and threat model: [docs/AUTH.md](https://github.com/tbaur/homebridge-mynest/blob/main/docs/AUTH.md).
 
 Prefer treating that token like a password; Nest Account sessions are account-scoped credentials.
 
@@ -75,7 +75,7 @@ Use the Homebridge UI, or add the platform to `config.json`:
 
 ### 4. Restart Homebridge
 
-Thermostats, Protects, and temperature sensors appear in the Home app as Nest reports them. The log should show `Connected to Nest`, then device adds, then `Platform ready`.
+Thermostats, Protects, and temperature sensors appear in the Home app as Nest reports them. The log should show `Connected to Nest (REST up; Observe connecting)`, then device adds, then `Platform ready`.
 
 Thermostat control (mode, setpoints, Eco) stays off until you enable **Allow thermostat control**. Optionally enable **Expose global Eco switch** for a house-wide Nest Eco Mode tile.
 
@@ -87,7 +87,7 @@ Thermostat control (mode, setpoints, Eco) stays off until you enable **Allow the
 | Nest Protect | Smoke + CO (+ optional occupancy / temp) | Smoke/CO require REST `topaz`; occupancy is ~10-minute presence |
 | Temperature Sensor | Temperature Sensor | Battery + temperature |
 
-Cameras, doorbells, locks, and Home/Away structure switches are out of scope.
+Cameras, doorbells, Yale locks, Home/Away structure switches, and Google-account-only homes are out of scope.
 
 ## Configuration Options
 
@@ -96,14 +96,14 @@ Cameras, doorbells, locks, and Home/Away structure switches are out of scope.
 | Option | Default | Description |
 | --- | --- | --- |
 | `name` | `MyNest` | Required. Plugin instance name shown in Homebridge logs. |
-| `accessToken` | — | Required. Nest Account `access_token` from [docs/AUTH.md](docs/AUTH.md). |
+| `accessToken` | — | Required. Nest Account `access_token` from [docs/AUTH.md](https://github.com/tbaur/homebridge-mynest/blob/main/docs/AUTH.md). |
 | `allowThermostatControl` | `false` | Opt in to send mode/setpoint/Eco changes to Nest via BatchUpdateState. |
 | `exposeGlobalEcoSwitch` | `false` | Publish a Nest Eco Mode switch that sets Eco on every thermostat. Writes require `allowThermostatControl`. |
 | `exposeProtectOccupancy` | `true` | Occupancy from REST `auto_away` when Nest computes it on a mains-powered Protect. |
 | `exposeProtectTemperature` | `false` | Temperature/humidity measured by each Protect. |
 | `ignoredDeviceIds` | `[]` | Device IDs or serials to leave out of HomeKit. |
 | `fieldTest` | `false` | Use Nest field-test hosts. |
-| `diagnosticsInterval` | `0` | Seconds between health heartbeats in the log; `0` off, else `30`–`3600`. |
+| `diagnosticsInterval` | `0` | Seconds between health heartbeats in the log; `0` off, else `30`–`86400` (24h). |
 | `structuredLogs` | `false` | When diagnostics are enabled, also emit a machine-readable JSON line alongside each human summary. |
 | `debug` | `false` | Verbose logging; tokens are redacted. |
 
@@ -113,9 +113,9 @@ Nest does not expose a reliable Protect motion event stream to third-party clien
 
 ## Not Working?
 
-1. **Authentication error** — Token missing, truncated, Google JWT/`ya29.`, or revoked. Capture a fresh Nest Account token ([docs/AUTH.md](docs/AUTH.md)).
-2. **Thermostat missing** — Modern thermostats are Observe-only on some accounts. With default logging the plugin warns within about a minute if Observe produced no frames; set `debug: true` for stream detail, or run `npm run verify`.
-3. **Thermostat in Settings but no room tile** — Remove and re-add the My Nest child bridge in the Home app, then assign rooms again. Same-UUID republish does not clear Apple Home's stuck presentation.
+1. **Authentication error** — Token missing, truncated, Google JWT/`ya29.`, or revoked. Capture a fresh Nest Account token ([docs/AUTH.md](https://github.com/tbaur/homebridge-mynest/blob/main/docs/AUTH.md)).
+2. **Thermostat missing** — Modern thermostats are Observe-only on some accounts. With default logging the plugin warns within about a minute if Observe produced no frames, and again every five minutes if a connected stream goes quiet; set `debug: true` for stream detail. From a git checkout you can also run `npm run verify` against the live account — see [DEVELOPMENT.md](https://github.com/tbaur/homebridge-mynest/blob/main/DEVELOPMENT.md).
+3. **Thermostat in Settings but no room tile** — Remove and re-add the **MyNest** child bridge in the Home app (or whatever you set as **Name**), then assign rooms again. Same-UUID republish does not clear Apple Home's stuck presentation.
 4. **Eco / setpoint changes snap back** — Enable **Allow thermostat control**. With control off, HomeKit can still move the UI (required for tiles) but Nest ignores the write and the plugin reverts.
 5. **Protect without smoke/CO** — Likely Observe-only (missing from REST). The accessory still appears; alarm tiles wait for REST.
 6. **No occupancy** — Battery Protect, power unknown, Observe-only Protect, or `exposeProtectOccupancy` off.
@@ -124,24 +124,25 @@ Nest does not expose a reliable Protect motion event stream to third-party clien
 
 This plugin holds a Nest Account `access_token` in Homebridge's plaintext `config.json`. That token is account-scoped Nest credentials — anyone who can read the file can act as the Nest web app for the home. Secure the host, prefer rotating the token if it may have leaked, and never paste tokens into issues or logs.
 
-Details: [SECURITY.md](SECURITY.md) and [docs/AUTH.md](docs/AUTH.md).
+Details: [SECURITY.md](https://github.com/tbaur/homebridge-mynest/blob/main/SECURITY.md) and [docs/AUTH.md](https://github.com/tbaur/homebridge-mynest/blob/main/docs/AUTH.md).
 
 Nest publishes no consumer API and can change or revoke sessions without notice. This plugin uses Nest Account tokens only and rejects Google cookie / `ya29.` shapes on purpose.
 
 ## Requirements
 
-- Node.js 20 or newer
-- Homebridge 1.6 or newer, including Homebridge 2.x
+- **Homebridge 2.x** — Homebridge 1.x is not supported
+- **Node.js 22 or 24** — this mirrors Homebridge 2's own `engines` constraint, so newer Node versions are excluded until Homebridge supports them; CI tests both
 - A Nest Account (not Google-only) with an `access_token` from [home.nest.com/session](https://home.nest.com/session)
 
 ## More Info
 
-- [Authentication](docs/AUTH.md) — capturing the Nest Account token
-- [Protocol notes](docs/PROTOCOL.md) — reverse-engineered Nest behaviour
-- [Development](DEVELOPMENT.md) — architecture and local setup
-- [Contributing](CONTRIBUTING.md)
-- [Security policy](SECURITY.md)
-- [Changelog](CHANGELOG.md)
+- [Authentication](https://github.com/tbaur/homebridge-mynest/blob/main/docs/AUTH.md) — capturing the Nest Account token
+- [Protocol notes](https://github.com/tbaur/homebridge-mynest/blob/main/docs/PROTOCOL.md) — reverse-engineered Nest behaviour
+- [Development](https://github.com/tbaur/homebridge-mynest/blob/main/DEVELOPMENT.md) — architecture and local setup
+- [Contributing](https://github.com/tbaur/homebridge-mynest/blob/main/CONTRIBUTING.md)
+- [Code of conduct](https://github.com/tbaur/homebridge-mynest/blob/main/CODE_OF_CONDUCT.md)
+- [Security policy](https://github.com/tbaur/homebridge-mynest/blob/main/SECURITY.md)
+- [Changelog](https://github.com/tbaur/homebridge-mynest/blob/main/CHANGELOG.md)
 - [Report issues](https://github.com/tbaur/homebridge-mynest/issues)
 
 ## License

package/SECURITY.md

@@ -2,19 +2,21 @@
 
 ## Supported Versions
 
-| Version | Supported         |
+Only the latest published release is supported. Fixes are shipped forward rather than backported, so the answer to "is my version supported?" is always "upgrade to the newest release".
+
+| Version | Supported |
 | ------- | ----------------- |
-| 1.x.x   | ✅ Active support |
-| 0.1.x   | ❌ Unsupported (upgrade to 1.x) |
+| Latest release | ✅ Active support |
+| Anything older | ❌ Unsupported — upgrade |
 
-Only the latest 1.x release is supported. Fixes are shipped forward rather than backported.
+The next release requires **Homebridge 2.x and Node.js 22 or newer**; Homebridge 1.x is no longer supported.
 
 ## Reporting a Vulnerability
 
 If you discover a security vulnerability, please report it responsibly:
 
 1. **Do NOT open a public issue**
-2. Email the maintainer directly or use GitHub's [private vulnerability reporting](https://github.com/tbaur/homebridge-mynest/security/advisories/new)
+2. Use GitHub's [private vulnerability reporting](https://github.com/tbaur/homebridge-mynest/security/advisories/new)
 3. Include:
    - Description of the vulnerability
    - Steps to reproduce
@@ -47,4 +49,6 @@ This plugin implements:
 
 ## Scope limits
 
-Cameras, doorbells, Yale locks, and Google-account-only homes are out of scope. Life-safety alarm state for Protects is only published while Nest REST can refresh it; Observe-only units and Protects whose REST feed is down do not keep a frozen all-clear.
+Out-of-scope devices are listed in the [README](README.md#supported-devices): cameras, doorbells, Yale locks, Home/Away structure switches, and Google-account-only homes.
+
+Life-safety alarm state for Protects is only published while Nest REST can refresh it; Observe-only units and Protects whose REST feed is down do not keep a frozen all-clear.

package/config.schema.json

@@ -28,7 +28,7 @@
         "title": "Allow thermostat control",
         "type": "boolean",
         "default": false,
-        "description": "Opt in to let HomeKit change thermostat mode, setpoints, and Eco via Nest BatchUpdateState. Off by default so upgrades stay read-only until you enable control. Confirm setpoints with nest-probe probe 12 (--confirm) first; Eco Mode uses the same gateway but has no separate probe confirm yet."
+        "description": "Opt in to let HomeKit change thermostat mode, setpoints, and Eco via Nest BatchUpdateState. Off by default so upgrades stay read-only until you enable control. Nest publishes no supported write API, so leave this off unless you want HomeKit driving your HVAC."
       },
       "exposeGlobalEcoSwitch": {
         "title": "Expose global Eco switch",
@@ -51,6 +51,7 @@
       "ignoredDeviceIds": {
         "title": "Ignored device IDs",
         "type": "array",
+        "default": [],
         "required": false,
         "description": "Nest device IDs or serial numbers to leave out of HomeKit. IDs appear in the Homebridge log when devices are added.",
         "items": {
@@ -70,8 +71,11 @@
         "type": "integer",
         "default": 0,
         "minimum": 0,
-        "maximum": 3600,
-        "description": "Seconds between health heartbeats in the Homebridge log. 0 disables (default). Values 1–29 are raised to 30."
+        "maximum": 86400,
+        "x-schema-form": {
+          "type": "number"
+        },
+        "description": "Seconds between health heartbeats in the Homebridge log. 0 disables (default). Allowed range 0–86400 (24h); values 1–29 are raised to 30."
       },
       "structuredLogs": {
         "title": "Structured diagnostic logs",
@@ -116,7 +120,15 @@
       "title": "Advanced",
       "expandable": true,
       "expanded": false,
-      "items": ["fieldTest", "diagnosticsInterval", "structuredLogs", "debug"]
+      "items": [
+        "fieldTest",
+        {
+          "key": "diagnosticsInterval",
+          "type": "number"
+        },
+        "structuredLogs",
+        "debug"
+      ]
     }
   ]
 }

package/dist/accessories/base.d.ts

@@ -12,7 +12,7 @@
  * working on Homebridge 2 — see `utils/bound-characteristics.ts` for why the
  * obvious alternatives silently stop updating.
  */
-import type { PlatformAccessory, Service } from 'homebridge';
+import type { CharacteristicValue, PlatformAccessory, Service } from 'homebridge';
 import type { DeviceIdentity, DeviceKind, NestDevice } from '../types/device';
 import type { ResolvedConfig } from '../types/config';
 import type { Logger } from '../utils/logger';
@@ -78,5 +78,11 @@ export declare abstract class NestAccessory<TState> {
      * reporting whatever value it last held.
      */
     protected removeService(type: Parameters<PlatformAccessory['getService']>[0]): void;
+    /**
+     * Map a low-battery verdict onto HomeKit's enum.
+     *
+     * `undefined` when Nest has said nothing, so the binder leaves the last known
+     * value in place rather than publishing "normal" on no evidence.
+     */
+    protected toLowBatteryValue(isBatteryLow: boolean | undefined): CharacteristicValue | undefined;
 }
-//# sourceMappingURL=base.d.ts.map

package/dist/accessories/base.js

@@ -17,6 +17,14 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.NestAccessory = void 0;
 const settings_1 = require("../settings");
 const bound_characteristics_1 = require("../utils/bound-characteristics");
+/** Whether any field published as Accessory Information differs. */
+function hasIdentityChanged(previous, next) {
+    return previous.name !== next.name
+        || previous.model !== next.model
+        || previous.serialNumber !== next.serialNumber
+        || previous.firmwareVersion !== next.firmwareVersion
+        || previous.id !== next.id;
+}
 /** One HomeKit accessory backed by one Nest device. */
 class NestAccessory {
     platform;
@@ -35,7 +43,7 @@ class NestAccessory {
         this.config = platform.resolvedConfig;
         this.identity = device.identity;
         this.state = device.state;
-        this.binder = new bound_characteristics_1.CharacteristicBinder(log);
+        this.binder = new bound_characteristics_1.CharacteristicBinder(log, device.identity.name);
         this.#applyAccessoryInformation();
     }
     get deviceId() {
@@ -49,9 +57,15 @@ class NestAccessory {
      * unconditionally is cheaper than diffing here.
      */
     update(device) {
+        const previousIdentity = this.identity;
         this.identity = device.identity;
         this.state = device.state;
-        this.#applyAccessoryInformation();
+        // Only when it actually changed. These four values essentially never do, and
+        // re-applying them ran HAP's full value-validation path four times per
+        // device per refresh on the hot update path.
+        if (hasIdentityChanged(previousIdentity, device.identity)) {
+            this.#applyAccessoryInformation();
+        }
         this.onServicesMayChange();
         this.binder.refresh();
         this.#logSummary();
@@ -93,6 +107,21 @@ class NestAccessory {
         this.binder.unbindService(existing);
         this.accessory.removeService(existing);
     }
+    /**
+     * Map a low-battery verdict onto HomeKit's enum.
+     *
+     * `undefined` when Nest has said nothing, so the binder leaves the last known
+     * value in place rather than publishing "normal" on no evidence.
+     */
+    toLowBatteryValue(isBatteryLow) {
+        const { StatusLowBattery } = this.platform.Characteristic;
+        if (isBatteryLow === undefined) {
+            return undefined;
+        }
+        return isBatteryLow
+            ? StatusLowBattery.BATTERY_LEVEL_LOW
+            : StatusLowBattery.BATTERY_LEVEL_NORMAL;
+    }
     #applyAccessoryInformation() {
         const { Characteristic, Service: HapService } = this.platform;
         const service = this.accessory.getService(HapService.AccessoryInformation)
@@ -106,10 +135,18 @@ class NestAccessory {
             service.setCharacteristic(Characteristic.FirmwareRevision, this.identity.firmwareVersion);
         }
     }
-    /** Info on a change, debug otherwise, so the log follows the house. */
+    /**
+     * Info on a change, debug otherwise, so the log follows the house.
+     *
+     * The first summary is also info: it is the only default-visible confirmation
+     * that a newly published device is actually reporting data. The "Added …"
+     * line carries no readings, so folding the first summary into the debug
+     * branch left an operator unable to tell a live device from a silent one.
+     */
     #logSummary() {
         const summary = this.describeState();
-        if (this.#lastSummary === null || this.#lastSummary === summary) {
+        const isFirst = this.#lastSummary === null;
+        if (!isFirst && this.#lastSummary === summary) {
             this.log.debug(`${this.identity.name}: ${summary}`);
         }
         else {
@@ -119,4 +156,3 @@ class NestAccessory {
     }
 }
 exports.NestAccessory = NestAccessory;
-//# sourceMappingURL=base.js.map

package/dist/accessories/global-eco.d.ts

@@ -24,5 +24,12 @@ export declare class GlobalEcoAccessory {
      * matches within {@link PENDING_ECO_MAX_MS}, take Nest truth.
      */
     updateAllEco(allEco: boolean): void;
+    /**
+     * Release the pending-write backstop.
+     *
+     * Called when the switch is removed or the platform stops. The timer is
+     * `unref`'d so it cannot hold the process open, but without this it could
+     * still fire up to 45s later and refresh a torn-down accessory.
+     */
+    dispose(): void;
 }
-//# sourceMappingURL=global-eco.d.ts.map

package/dist/accessories/global-eco.js

@@ -15,7 +15,6 @@ exports.GlobalEcoAccessory = void 0;
 const settings_1 = require("../settings");
 const bound_characteristics_1 = require("../utils/bound-characteristics");
 const sanitizers_1 = require("../utils/sanitizers");
-const DISPLAY_NAME = 'Nest Eco Mode';
 /**
  * How long a successful HomeKit Eco write may ignore Nest aggregates that have
  * not yet matched. After this, Nest truth wins (Nest app / failed Observe).
@@ -35,11 +34,19 @@ class GlobalEcoAccessory {
      */
     #pendingAllEco = null;
     #pendingSinceMs = null;
+    /**
+     * Backstop for {@link PENDING_ECO_MAX_MS}.
+     *
+     * The age check in {@link updateAllEco} only runs when Nest sends another
+     * update. If Observe dies right after a successful write, nothing would ever
+     * clear the optimistic value and the switch would hold it indefinitely.
+     */
+    #pendingTimer = null;
     constructor(platform, accessory, log) {
         this.#platform = platform;
         this.#accessory = accessory;
         this.#log = log;
-        this.#binder = new bound_characteristics_1.CharacteristicBinder(log);
+        this.#binder = new bound_characteristics_1.CharacteristicBinder(log, settings_1.GLOBAL_ECO_DISPLAY_NAME);
         this.#applyAccessoryInformation();
         this.#bindSwitch();
         this.#binder.refresh();
@@ -58,8 +65,7 @@ class GlobalEcoAccessory {
             }
             else if (this.#pendingSinceMs !== null
                 && Date.now() - this.#pendingSinceMs >= PENDING_ECO_MAX_MS) {
-                this.#log.warn(`${DISPLAY_NAME}: Nest did not confirm Eco change within ${PENDING_ECO_MAX_MS / 1000}s — following Nest`);
-                this.#clearPending();
+                this.#expirePending();
             }
             else {
                 return;
@@ -68,15 +74,50 @@ class GlobalEcoAccessory {
         this.#allEco = allEco;
         this.#binder.refresh();
     }
+    /**
+     * Release the pending-write backstop.
+     *
+     * Called when the switch is removed or the platform stops. The timer is
+     * `unref`'d so it cannot hold the process open, but without this it could
+     * still fire up to 45s later and refresh a torn-down accessory.
+     */
+    dispose() {
+        this.#clearPending();
+    }
     #clearPending() {
         this.#pendingAllEco = null;
         this.#pendingSinceMs = null;
+        if (this.#pendingTimer) {
+            clearTimeout(this.#pendingTimer);
+            this.#pendingTimer = null;
+        }
+    }
+    /** Give up on an unconfirmed write and let Nest's own value stand. */
+    #expirePending() {
+        this.#log.warn(`${settings_1.GLOBAL_ECO_DISPLAY_NAME}: Nest did not confirm Eco change within ${PENDING_ECO_MAX_MS / 1000}s — following Nest`);
+        this.#clearPending();
+    }
+    /** Start the backstop that gives Nest the last word even if it goes quiet. */
+    #armPending(ecoOn) {
+        this.#clearPending();
+        this.#pendingAllEco = ecoOn;
+        this.#pendingSinceMs = Date.now();
+        this.#pendingTimer = setTimeout(() => {
+            this.#pendingTimer = null;
+            if (this.#pendingAllEco === null) {
+                return;
+            }
+            this.#expirePending();
+            this.#binder.refresh();
+        }, PENDING_ECO_MAX_MS);
+        // Homebridge owns the process lifetime; this must not hold Node open.
+        this.#pendingTimer.unref?.();
     }
     #bindSwitch() {
         const { Characteristic, Service: HapService } = this.#platform;
         const service = this.#accessory.getService(HapService.Switch)
-            ?? this.#accessory.addService(HapService.Switch, DISPLAY_NAME);
-        service.setCharacteristic(Characteristic.Name, DISPLAY_NAME);
+            ?? this.#accessory.addService(HapService.Switch, settings_1.GLOBAL_ECO_DISPLAY_NAME);
+        service.setCharacteristic(Characteristic.Name, settings_1.GLOBAL_ECO_DISPLAY_NAME);
         this.#accessory
             .setPrimaryService?.(service);
         this.#binder.bind(service, Characteristic.On, () => this.#allEco, {
@@ -91,22 +132,21 @@ class GlobalEcoAccessory {
             if (!sent) {
                 this.#clearPending();
                 if (!this.#platform.resolvedConfig.allowThermostatControl) {
-                    this.#log.warn(`${DISPLAY_NAME}: ignoring HomeKit change — enable Allow thermostat control in config.`);
+                    this.#log.warn(`${settings_1.GLOBAL_ECO_DISPLAY_NAME}: ignoring HomeKit change — enable Allow thermostat control in config.`);
                 }
                 // HAP assigns On after onSet; revert to Nest-derived `#allEco`.
                 setImmediate(() => this.#binder.refresh());
                 return;
             }
-            this.#log.info(`${DISPLAY_NAME}: ${ecoOn ? 'Updating all thermostats to Eco' : 'Clearing Eco on all thermostats'}`);
+            this.#log.info(`${settings_1.GLOBAL_ECO_DISPLAY_NAME}: ${ecoOn ? 'Updating all thermostats to Eco' : 'Clearing Eco on all thermostats'}`);
             // Optimistic until Nest's all-Eco aggregate matches; do not refresh here
             // or HAP's post-onSet value is overwritten by a stale read.
-            this.#pendingAllEco = ecoOn;
-            this.#pendingSinceMs = Date.now();
+            this.#armPending(ecoOn);
             this.#allEco = ecoOn;
         }
         catch (error) {
             this.#clearPending();
-            this.#log.warn(`${DISPLAY_NAME}: Eco update failed: ${(0, sanitizers_1.sanitizeError)(error)}`);
+            this.#log.warn(`${settings_1.GLOBAL_ECO_DISPLAY_NAME}: Eco update failed: ${(0, sanitizers_1.sanitizeError)(error)}`);
             setImmediate(() => this.#binder.refresh());
         }
     }
@@ -116,10 +156,9 @@ class GlobalEcoAccessory {
             ?? this.#accessory.addService(HapService.AccessoryInformation);
         service
             .setCharacteristic(Characteristic.Manufacturer, settings_1.MANUFACTURER)
-            .setCharacteristic(Characteristic.Name, DISPLAY_NAME)
+            .setCharacteristic(Characteristic.Name, settings_1.GLOBAL_ECO_DISPLAY_NAME)
             .setCharacteristic(Characteristic.Model, 'Eco Mode')
-            .setCharacteristic(Characteristic.SerialNumber, 'GLOBAL_ECO');
+            .setCharacteristic(Characteristic.SerialNumber, settings_1.GLOBAL_ECO_DEVICE_ID);
     }
 }
 exports.GlobalEcoAccessory = GlobalEcoAccessory;
-//# sourceMappingURL=global-eco.js.map

package/dist/accessories/protect.d.ts

@@ -42,4 +42,3 @@ export declare class ProtectAccessory extends NestAccessory<ProtectState> {
     protected onServicesMayChange(): void;
     protected describeState(): string;
 }
-//# sourceMappingURL=protect.d.ts.map

package/dist/accessories/protect.js

@@ -66,11 +66,18 @@ class ProtectAccessory extends base_1.NestAccessory {
      * Nest has said anything would show a working all-clear on no evidence.
      * Once created, services stay through REST outages (rooms/automations keep
      * their targets) and are marked inactive/faulted while the feed is stale.
+     *
+     * Each sensor is gated on *its own* reading. Nest returns different topaz
+     * subsets per firmware, and a bucket carrying `smoke_status` without
+     * `co_status` must not produce a CO tile: its reader would return undefined,
+     * the binder would skip it, and HomeKit would show a CO detector resting at
+     * HAP's default "levels normal" with nothing behind it.
      */
     #ensureAlarmServices() {
         const { Characteristic, Service: HapService } = this.platform;
-        const hasAlarms = this.state.smoke !== undefined || this.state.carbonMonoxide !== undefined;
-        if (!hasAlarms) {
+        const hasSmoke = this.state.smoke !== undefined;
+        const hasCarbonMonoxide = this.state.carbonMonoxide !== undefined;
+        if (!hasSmoke && !hasCarbonMonoxide) {
             this.removeService(HapService.SmokeSensor);
             this.removeService(HapService.CarbonMonoxideSensor);
             this.#smokeService = null;
@@ -92,25 +99,53 @@ class ProtectAccessory extends base_1.NestAccessory {
             this.#didLogAlarmFeedStale = false;
             this.log.info(`${this.identity.name}: REST alarm feed restored — Smoke/CO live again.`);
         }
-        this.#smokeService = this.resolveService(HapService.SmokeSensor);
-        this.#smokeService.setCharacteristic(Characteristic.Name, `${this.identity.name} Smoke`);
-        this.#coService = this.resolveService(HapService.CarbonMonoxideSensor);
-        this.#coService.setCharacteristic(Characteristic.Name, `${this.identity.name} CO`);
-        this.binder.bind(this.#smokeService, Characteristic.SmokeDetected, () => this.#toSmokeValue(this.state.smoke));
-        this.binder.bind(this.#coService, Characteristic.CarbonMonoxideDetected, () => this.#toCarbonMonoxideValue(this.state.carbonMonoxide));
-        // Both services carry the shared health characteristics so either tile in
-        // the Home app shows a flat battery, an offline device, or a stale REST feed.
+        if (hasSmoke) {
+            this.#smokeService = this.resolveService(HapService.SmokeSensor);
+            this.#smokeService.setCharacteristic(Characteristic.Name, `${this.identity.name} Smoke`);
+            this.binder.bind(this.#smokeService, Characteristic.SmokeDetected, () => this.#toSmokeValue(this.state.smoke));
+        }
+        else {
+            this.removeService(HapService.SmokeSensor);
+            this.#smokeService = null;
+        }
+        if (hasCarbonMonoxide) {
+            this.#coService = this.resolveService(HapService.CarbonMonoxideSensor);
+            this.#coService.setCharacteristic(Characteristic.Name, `${this.identity.name} CO`);
+            this.binder.bind(this.#coService, Characteristic.CarbonMonoxideDetected, () => this.#toCarbonMonoxideValue(this.state.carbonMonoxide));
+        }
+        else {
+            this.removeService(HapService.CarbonMonoxideSensor);
+            this.#coService = null;
+        }
+        // Whichever tiles exist carry the shared health characteristics, so the
+        // Home app shows a flat battery, an offline device, or a stale REST feed.
         for (const service of [this.#smokeService, this.#coService]) {
-            this.binder.bind(service, Characteristic.StatusLowBattery, () => this.#toLowBatteryValue());
-            this.binder.bind(service, Characteristic.StatusActive, () => this.#isAlarmReadingLive());
-            this.binder.bind(service, Characteristic.StatusFault, () => this.#isAlarmReadingLive()
-                ? Characteristic.StatusFault.NO_FAULT
-                : Characteristic.StatusFault.GENERAL_FAULT);
+            if (service) {
+                this.#bindHealth(service);
+            }
         }
         // Alarm tiles carry battery; the standalone Battery service is only for
         // Observe-only Protects that have no smoke/CO yet.
         this.removeService(HapService.Battery);
     }
+    /** Battery plus liveness, for the alarm tiles. */
+    #bindHealth(service) {
+        this.binder.bind(service, this.platform.Characteristic.StatusLowBattery, () => this.#toLowBatteryValue());
+        this.#bindLiveness(service);
+    }
+    /**
+     * Mark a service inactive and faulted whenever its reading is not live.
+     *
+     * Shared by the alarm tiles and the occupancy tile: all three are backed by
+     * the same REST feed, so they go stale together.
+     */
+    #bindLiveness(service) {
+        const { Characteristic } = this.platform;
+        this.binder.bind(service, Characteristic.StatusActive, () => this.#isAlarmReadingLive());
+        this.binder.bind(service, Characteristic.StatusFault, () => this.#isAlarmReadingLive()
+            ? Characteristic.StatusFault.NO_FAULT
+            : Characteristic.StatusFault.GENERAL_FAULT);
+    }
     /** Alarm readings are live only while online and the REST feed is fresh. */
     #isAlarmReadingLive() {
         return this.state.isOnline !== false && this.state.isAlarmFeedStale !== true;
@@ -184,10 +219,7 @@ class ProtectAccessory extends base_1.NestAccessory {
             : this.state.isOccupied
                 ? Characteristic.OccupancyDetected.OCCUPANCY_DETECTED
                 : Characteristic.OccupancyDetected.OCCUPANCY_NOT_DETECTED);
-        this.binder.bind(service, Characteristic.StatusActive, () => this.#isAlarmReadingLive());
-        this.binder.bind(service, Characteristic.StatusFault, () => this.#isAlarmReadingLive()
-            ? Characteristic.StatusFault.NO_FAULT
-            : Characteristic.StatusFault.GENERAL_FAULT);
+        this.#bindLiveness(service);
         if (!_a.#didLogOccupancyHint) {
             _a.#didLogOccupancyHint = true;
             this.log.info(`Protect occupancy is Nest ~${settings_1.PROTECT_OCCUPANCY_HOLD_OFF_SEC / 60}-min presence (auto_away), not motion.`);
@@ -251,13 +283,7 @@ class ProtectAccessory extends base_1.NestAccessory {
             : Characteristic.CarbonMonoxideDetected.CO_LEVELS_ABNORMAL;
     }
     #toLowBatteryValue() {
-        const { Characteristic } = this.platform;
-        if (this.state.isBatteryLow === undefined) {
-            return undefined;
-        }
-        return this.state.isBatteryLow
-            ? Characteristic.StatusLowBattery.BATTERY_LEVEL_LOW
-            : Characteristic.StatusLowBattery.BATTERY_LEVEL_NORMAL;
+        return this.toLowBatteryValue(this.state.isBatteryLow);
     }
     /**
      * HomeKit wants 0–100; Nest REST reports millivolts as `battery_level`.
@@ -293,4 +319,3 @@ class ProtectAccessory extends base_1.NestAccessory {
 }
 exports.ProtectAccessory = ProtectAccessory;
 _a = ProtectAccessory;
-//# sourceMappingURL=protect.js.map

package/dist/accessories/temperature-sensor.d.ts

@@ -25,4 +25,3 @@ export declare class TemperatureSensorAccessory extends NestAccessory<Temperatur
     protected bindCharacteristics(): void;
     protected describeState(): string;
 }
-//# sourceMappingURL=temperature-sensor.d.ts.map

package/dist/accessories/temperature-sensor.js

@@ -36,13 +36,7 @@ class TemperatureSensorAccessory extends base_1.NestAccessory {
         this.binder.bind(battery, Characteristic.StatusLowBattery, () => this.#toLowBatteryValue());
     }
     #toLowBatteryValue() {
-        const { Characteristic } = this.platform;
-        if (this.state.isBatteryLow === undefined) {
-            return undefined;
-        }
-        return this.state.isBatteryLow
-            ? Characteristic.StatusLowBattery.BATTERY_LEVEL_LOW
-            : Characteristic.StatusLowBattery.BATTERY_LEVEL_NORMAL;
+        return this.toLowBatteryValue(this.state.isBatteryLow);
     }
     describeState() {
         const parts = [];
@@ -59,4 +53,3 @@ class TemperatureSensorAccessory extends base_1.NestAccessory {
     }
 }
 exports.TemperatureSensorAccessory = TemperatureSensorAccessory;
-//# sourceMappingURL=temperature-sensor.js.map