homebridge-nuheat2 1.2.4-beta.1 → 1.2.4

package/CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to this project should be documented in this file
 
 ## [Unreleased]
 
-## [1.2.4-beta.1] - 2026-04-11
+## [1.2.4] - 2026-04-11
 
 ### Added
 
@@ -14,18 +14,13 @@ All notable changes to this project should be documented in this file
 
 ### Changed
 
-- Simplify thermostat operating-mode handling to match the documented Nuheat Swagger model
-- Refresh thermostats when Nuheat sends schedule notifications
-
-## [1.2.4-beta.0] - 2026-04-11
-
-### Changed
-
 - Delay platform startup until Homebridge finishes restoring cached accessories
 - Allow overriding Nuheat OAuth client settings through config or environment variables
 - Improve SignalR reconnection handling and token refresh behavior
-- Add basic regression tests and modernize package metadata for Homebridge 1.8+ and 2.0 betas
-- Publish the maintained fork under the new npm package identity `homebridge-nuheat2`
+- Add regression tests and modernize package metadata for current Homebridge releases
+- Publish the maintained fork under the npm package identity `homebridge-nuheat2`
+- Simplify thermostat operating-mode handling to match the documented Nuheat Swagger model
+- Refresh thermostats when Nuheat sends schedule notifications
 
 ### Fixed
 

package/README.md

@@ -52,6 +52,7 @@ Most users should configure the plugin through Homebridge Config UI X, but the e
   "password": "password123",
   "devices": [{ "serialNumber": "1111111" }, { "serialNumber": "2222222" }],
   "autoPopulateAwayModeSwitches": true,
+  "exposeScheduleSwitches": false,
   "holdLength": 1440,
   "refresh": 60
 }
@@ -62,17 +63,18 @@ Most users should configure the plugin through Homebridge Config UI X, but the e
 - `platform`: Must be `NuHeat`
 - `name`: Display name used in Homebridge logs
 - `email`: MyNuheat account email address
+- `Email`: Legacy alias still accepted for backward compatibility, but `email` is the preferred documented field
 - `password`: MyNuheat account password
-- `devices`: Optional list of thermostats to expose
+- `devices`: Optional list of thermostats to expose. If omitted or empty, every thermostat on the account will be discovered automatically
 - `serialNumber`: Thermostat serial number from MyNuheat
-- `autoPopulateAwayModeSwitches`: Automatically expose switches for all groups on the account
+- `autoPopulateAwayModeSwitches`: Automatically expose away-mode switches for all groups on the account
 - `exposeScheduleSwitches`: Optionally expose a switch per thermostat that reflects whether the thermostat is following its schedule and can be turned on to resume the schedule
-- `groups`: Optional allow-list of groups to expose as away-mode switches
+- `groups`: Optional allow-list of groups to expose as away-mode switches. This only affects group/away-mode accessories
 - `groupName`: Group name as shown in MyNuheat
 - `holdLength`: Hold duration in minutes
 - `refresh`: Poll interval in seconds, default `60`
 - `debug`: Enables verbose logging
-- `clientId`: Optional advanced override for the Nuheat OAuth client ID
+- `clientId`: Optional advanced override for the Nuheat OAuth client ID. This is recommended once you have official Nuheat API credentials
 - `clientSecret`: Optional advanced override for the Nuheat OAuth client secret
 - `redirectUri`: Optional advanced override for the Nuheat OAuth redirect URI, default `http://localhost`
 
@@ -88,6 +90,8 @@ If `devices` is omitted or empty, the plugin will automatically expose every the
 
 If `groups` is omitted and `autoPopulateAwayModeSwitches` is enabled, the plugin will automatically expose away-mode switches for all groups on the account.
 
+If `exposeScheduleSwitches` is enabled, the plugin will also create one switch per thermostat that turns on when the thermostat is following its Nuheat schedule and can be used to resume that schedule from HomeKit.
+
 ## Nuheat API Access
 
 Nuheat's public OpenAPI documentation indicates that third-party developers should request their own API credentials:
@@ -95,7 +99,7 @@ Nuheat's public OpenAPI documentation indicates that third-party developers shou
 - [Nuheat OpenAPI docs](https://api.mynuheat.com/)
 - [Nuheat API access request page](https://www.nuheat.com/openapi)
 
-This fork still supports the legacy built-in OAuth client settings as a fallback, but using your own `clientId` and `clientSecret` is the recommended long-term path.
+This fork still supports the legacy built-in OAuth client settings as a fallback, but using your own `clientId` and `clientSecret` is the recommended long-term path once Nuheat issues them for your integration.
 
 ## What's New In This Fork
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "homebridge-nuheat2",
-  "version": "1.2.4-beta.1",
+  "version": "1.2.4",
   "description": "Homebridge Platform for NuHeat Signature Thermostats",
   "main": "index.js",
   "scripts": {