homebridge-http-advanced-platform 2.0.0-alpha.6 → 2.0.0-alpha.7

package/README.md

@@ -1,6 +1,8 @@
 # Homebridge HTTP Advanced Platform
 
-A platform conversion of [staromeste's homebridge-http-advanced-accessory](https://github.com/staromeste/homebridge-http-advanced-accessory), connecting HTTP-controlled devices and web services to Apple Home through Homebridge. The project retains the original Apache-2.0 license, Git history and contributor credit, including the earlier [tasict/homebridge-http-accessory](https://github.com/tasict/homebridge-http-accessory) lineage.
+Connect HTTP/HTTPS-controlled devices and REST APIs to Apple Home (HomeKit) through Homebridge. Read sensor values, control switches and other supported HomeKit services, and map JSON or XML responses with JSONPath or XPath. Shared polling and caching keep reads responsive while HTTP refreshes run in the background.
+
+This is a platform conversion of [staromeste's homebridge-http-advanced-accessory](https://github.com/staromeste/homebridge-http-advanced-accessory). The project retains the original Apache-2.0 license, Git history and contributor credit, including the earlier [tasict/homebridge-http-accessory](https://github.com/tasict/homebridge-http-accessory) lineage.
 
 **Use platform devices, retain existing accessory configurations, or migrate manually at your own pace.** Keep your `HttpAdvancedAccessory` entries, encoded command URLs, request bodies, hand-written mappings and other settings. The improvements apply to existing accessories without converting them to a platform or upgrading their web server.
 
@@ -8,7 +10,7 @@ A platform conversion of [staromeste's homebridge-http-advanced-accessory](https
 - **More resilient HTTP handling:** bounded requests, background recovery and quieter logs accommodate slow or temporarily unavailable servers, including older systems you cannot change.
 - **Migration at your pace:** maintain existing accessories through JSON Config, and add platform devices alongside them when useful. The plugin also keeps a requested switch state visible while the server catches up, avoiding a brief reversal caused by stale reads.
 
-**Release channel: `2.0.0-alpha.6` is an opt-in Alpha based on preserved Alpha.5.** It changes public package identity and branding while retaining Alpha.5 device behavior. Source checks, isolated installations and Homebridge UI replacement/rollback acceptance have passed; paired Apple Home and live-device soak remain pending. Compatibility applies on the supported runtimes below. Refresh timing changes, and voluntarily converting a device to the platform creates a new HomeKit identity. [Compatibility details](docs/modernization.md#what-non-breaking-means-here) explain those boundaries.
+**Release channel: `2.0.0-alpha.7` is an Alpha based on preserved Alpha.5.** Alpha.6 introduced the new public package identity and branding. Alpha.7 updates search metadata and corrects npm installation guidance; device behavior is unchanged. Source checks, isolated installations and Homebridge UI replacement/rollback acceptance have passed; paired Apple Home and live-device soak remain pending. Compatibility applies on the supported runtimes below. Refresh timing changes, and voluntarily converting a device to the platform creates a new HomeKit identity. [Compatibility details](docs/modernization.md#what-non-breaking-means-here) explain those boundaries.
 
 [User guide](#user-guide) · [Modernization details](#modernization-details) · [Developer reference](docs/modernization.md#development-and-release-policy)
 
@@ -27,23 +29,25 @@ Older environments need a runtime upgrade before testing this Alpha. Plugin 1.3.
 
 Back up Homebridge first, including configuration, cached accessories and pairing data. This is a separate npm package, not an automatic update to the original accessory package. Follow the [replacement and rollback guide](docs/migration.md) before changing an existing installation.
 
-Check the [npm version list](https://www.npmjs.com/package/homebridge-http-advanced-platform?activeTab=versions) and matching [GitHub prerelease](https://github.com/shanemcw/homebridge-http-advanced-platform/releases) before installing. The registry instructions below apply once the Alpha is published; a local candidate archive alone does not establish public availability.
+Check the [npm version list](https://www.npmjs.com/package/homebridge-http-advanced-platform?activeTab=versions) and matching [GitHub prerelease](https://github.com/shanemcw/homebridge-http-advanced-platform/releases) before installing. Choose a published Alpha; a local candidate archive alone does not establish public availability.
 
-In **Homebridge UI 5.29.0**, open **Plugins** and search for `homebridge-http-advanced-platform`. Choose its install icon, then select **alpha / v2.0.0-alpha.6** in the version chooser. After installation, use **Manage Version** to select a later Alpha deliberately. Descriptive searches such as **HTTP Advanced** or **HTTP accessory** depend on npm indexing; searching the exact original package name still finds the original accessory package. The exact new-package card may show an empty default-version label while this package has only an `alpha` tag; select the tagged version in the chooser.
+In **Homebridge UI 5.29.0**, open **Plugins** and search for `homebridge-http-advanced-platform`. Choose its install icon, then select the **alpha** row in the version chooser, or the reviewed **v2.0.0-alpha.7** version. After installation, use **Manage Version** to select a later Alpha deliberately. Descriptive searches such as **HTTP Advanced**, **HTTP accessory**, **REST API** or **HTTP JSON** depend on npm indexing and ranking; searching the exact original package name still finds the original accessory package.
 
 For command-line installation, use `homebridge-http-advanced-platform@alpha`, or pin the reviewed version as shown below. Use the same plugin location and account your Homebridge installation already uses; `/var/lib/homebridge` is an example prefix:
 
 ```sh
-npm install --prefix /var/lib/homebridge --omit=dev --ignore-scripts homebridge-http-advanced-platform@2.0.0-alpha.6
+npm install --prefix /var/lib/homebridge --omit=dev --ignore-scripts homebridge-http-advanced-platform@2.0.0-alpha.7
 ```
 
-Before publication, install the locally reviewed archive instead:
+To install a reviewed archive directly:
 
 ```sh
-npm install --prefix /var/lib/homebridge --omit=dev --ignore-scripts /path/to/homebridge-http-advanced-platform-2.0.0-alpha.6.tgz
+npm install --prefix /var/lib/homebridge --omit=dev --ignore-scripts /path/to/homebridge-http-advanced-platform-2.0.0-alpha.7.tgz
 ```
 
-This package has no stable release or `latest` tag yet. An install without an explicit tag/version is not the Alpha installation path. Its release tags are separate from the original accessory package's tags. Public registry indexing and the complete UI-to-registry install flow will be checked at launch; the Alpha-only version selection was rehearsed with isolated registry data and Homebridge UI 5.29.0's actual service and version-chooser logic.
+**This package has no stable release.** npm requires a `latest` tag; for this package, it can point to an Alpha and does not indicate stability. An unqualified install can therefore install an Alpha. The `alpha` and `latest` tags can point to different Alpha versions; choose the explicit `@alpha` tag or reviewed exact version to select the intended release. These tags affect only the new platform package; the original accessory package is separate and does not update automatically to it.
+
+Alpha.7 includes this correction in its packaged README. The earlier published Alpha.6 archive remains unchanged.
 
 Preserve Homebridge storage and bridge identity. Remove the old plugin package as part of the backed-up replacement before starting Homebridge with the new package; loading both would make their shared configuration aliases ambiguous. See the migration guide for package-qualified entries and plugin allowlists. Restart Homebridge and its UI, then verify devices, state updates, controls and existing automations. Installed UI and managed-child-bridge acceptance passed in an isolated Node 24/Homebridge 2 fixture with HAP disabled; paired Apple Home identity and live controls still need acceptance.
 

package/docs/alpha-release-notes.md

@@ -1,4 +1,4 @@
-# Homebridge HTTP Advanced Platform 2.0.0-alpha.6
+# Homebridge HTTP Advanced Platform 2.0.0-alpha.7
 
 Opt-in Alpha based on preserved `2.0.0-alpha.5`. Confirm availability in the
 matching [GitHub prerelease](https://github.com/shanemcw/homebridge-http-advanced-platform/releases)
@@ -6,7 +6,11 @@ and [npm version list](https://www.npmjs.com/package/homebridge-http-advanced-pl
 
 This is a platform conversion of [staromeste/homebridge-http-advanced-accessory](https://github.com/staromeste/homebridge-http-advanced-accessory). It retains the original Apache-2.0 license, contributor credit and Git history.
 
-The release changes the public package to `homebridge-http-advanced-platform`, updates branding and search metadata, and retains Alpha.5 device behavior: shared cached reads, bounded background HTTP requests, recovery, write confirmation, legacy accessories and optional platform devices. No parent issue/PR fixes or dependency updates are included in this packaging milestone.
+Alpha.6 introduced the public `homebridge-http-advanced-platform` package. Alpha.7 updates its description, keywords and README to explain HTTP/HTTPS devices, REST APIs, JSON/XML response mapping, JSONPath, XPath, polling, shared caching, switches and sensors. It also packages the corrected explanation of npm's required `latest` tag. Search metadata helps matching but does not guarantee public indexing or ranking.
+
+Distributable runtime, custom UI, schema, configuration aliases, UUID namespace and dependency declarations are unchanged from Alpha.6. This retains Alpha.5 device behavior: shared cached reads, bounded background HTTP requests, recovery, write confirmation, legacy accessories and optional platform devices. No parent issue/PR fixes or dependency updates are included.
+
+A repository-only timing assertion now checks scheduled execution spacing rather than server receive timestamps, which include connection delays. Its configured delay and timeout checks are retained. Tests and maintenance reports are not shipped in the npm archive.
 
 Configuration aliases remain `HttpAdvancedAccessory` and `HttpAdvanced`. The platform UUID namespace remains the Alpha.5 namespace. Package-qualified configuration and plugin lists must use the new package name; do not load both old and new packages. Follow the [replacement and rollback guide](migration.md), preserving configuration, storage and bridge identity.
 
@@ -14,6 +18,8 @@ Moving a legacy accessory into a platform remains an explicit manual conversion
 
 Requirements remain Node `^22.13.0 || ^24.0.0` and Homebridge `^1.11.4 || ^2.4.0`. Source checks and installed loader/adapters/custom UI IPC passed across Node 22/24 and Homebridge 1/2. Rendered Homebridge UI 5.29.0, native editing, managed child bridges and backed-up replacement/rollback passed in an isolated Node 24/Homebridge 2 fixture. HAP was disabled in that fixture; paired Apple Home, physical controls, rooms/scenes/automations and live soak remain separate acceptance.
 
-The publication channel is the explicit `alpha` npm tag with a matching GitHub prerelease; this package has no stable release or `latest` tag. Once published, select **alpha / v2.0.0-alpha.6** in Homebridge UI 5.29.0's install version chooser, or install `homebridge-http-advanced-platform@alpha` (exact version: `@2.0.0-alpha.6`). The Alpha-only chooser and metadata matching were rehearsed using isolated registry responses and actual UI logic; public indexing and registry installation still require launch checks. Its tags do not modify the original accessory package's tags. Homebridge verification will be pursued separately after publication; this Alpha is not verified.
+The publication channel is the explicit `alpha` npm tag with a matching GitHub prerelease; this package has no stable release. npm also requires a `latest` tag, which can point to an Alpha and does not indicate stability. The `alpha` and `latest` tags can point to different Alpha versions, so choose the **alpha** row or reviewed **v2.0.0-alpha.7** in Homebridge UI 5.29.0's install version chooser, or install `homebridge-http-advanced-platform@alpha` (exact version: `@2.0.0-alpha.7`). Its tags do not modify the original accessory package's tags. Homebridge verification will be pursued separately after publication; this Alpha is not verified.
+
+Alpha.7 includes the npm tag correction in its packaged README. The published Alpha.6 archive and its release tag remain unchanged.
 
 Report versions and sanitized diagnostics. Do not include credentials, pairing PINs or unredacted configuration.

package/docs/migration.md

@@ -7,7 +7,7 @@ This is a separate package with the existing Alpha behavior. It does not automat
 1. Keep the Homebridge storage, bridge username, accessory names, service definitions, platform names, device IDs and `_bridge` settings unchanged.
 2. Stop Homebridge before the package swap, and remove only the installed `homebridge-http-advanced-accessory` package through the installation's existing package-management workflow. Preserve configuration and Homebridge storage. Do not load both packages: both register `HttpAdvancedAccessory` and `HttpAdvanced`.
 3. Unqualified `accessory: "HttpAdvancedAccessory"` and `platform: "HttpAdvanced"` remain valid. In explicitly qualified entries, replace only the package prefix with `homebridge-http-advanced-platform`, keeping the alias after the dot unchanged. Likewise update the package name in any `plugins` allowlist or `disabledPlugins` list. Runtime does not rewrite these settings.
-4. Install the reviewed platform Alpha package through the installation's existing package-management workflow, explicitly selecting `@alpha`, `@2.0.0-alpha.6` or the reviewed local archive. See the [installation instructions](../README.md#install-or-upgrade), then restart Homebridge and its UI.
+4. Install the reviewed platform Alpha package through the installation's existing package-management workflow, explicitly selecting `@alpha`, `@2.0.0-alpha.7` or the reviewed local archive. See the [installation instructions](../README.md#install-or-upgrade), then restart Homebridge and its UI.
 5. Verify native JSON Config, Plugin Config, legacy devices, cached platform devices, child bridges, rooms, scenes and automations before leaving the candidate unattended.
 
 Platform UUIDs retain the immutable Alpha.5 namespace `homebridge-http-advanced-accessory`, independent of the new registration name. Homebridge 1/2 can reassociate cached platform accessories through the unchanged `HttpAdvanced` alias when the old package is absent. Regression tests exercise that fallback with serialized cache and identifier assignments. Isolated installed-UI, managed-child-bridge and package replacement/rollback checks also passed with HAP disabled. Paired Apple Home identity, rooms, scenes, automations and actual device controls remain live acceptance checks.

package/docs/modernization.md

@@ -1,6 +1,6 @@
 # Modernization details and developer reference
 
-This reference describes the behavior of **2.0.0-alpha.6**. Start with the [README](../README.md) for the compatibility summary, installation and everyday configuration.
+This reference describes the behavior of **2.0.0-alpha.7**, unchanged from Alpha.6. Start with the [README](../README.md) for the compatibility summary, installation and everyday configuration.
 
 ## What non-breaking means here
 
@@ -206,6 +206,6 @@ npm pack --dry-run
 
 CI exercises Node 22/24 and real Homebridge v1/v2 HAP implementations. Unit/integration tests use only loopback fake servers. `legacy-plugin` is a test-only alias of published 1.3.0; its obsolete dependencies are excluded from production installation and the tarball. `npm audit --omit=dev` audits the maintained runtime separately.
 
-Any future public prerelease must use an explicit tag matching its version channel (`alpha` or `beta`) and be marked as a GitHub prerelease. The guard rejects stable versions, channel mismatches and `latest`. `publishConfig.tag` remains `alpha` for this Alpha candidate; update it deliberately when preparing Beta. No automatic publishing workflow is enabled. Stable requires broader device, restart and real-installation evidence, not merely one working household fixture.
+Any future public prerelease must use an explicit tag matching its version channel (`alpha` or `beta`) and be marked as a GitHub prerelease. The guard rejects stable versions, channel mismatches and manual publication to `latest`. npm requires a `latest` dist-tag and assigned it to the first public Alpha; retaining that registry-required tag does not make the package stable. The `alpha` and `latest` tags can point to different prerelease versions. `publishConfig.tag` remains `alpha` for this Alpha candidate; update it deliberately when preparing Beta. No automatic publishing workflow is enabled. Stable requires broader device, restart and real-installation evidence, not merely one working household fixture.
 
 The existing Apache-2.0 LICENSE remains unchanged. Package metadata is reconciled to that file, which has existed since the initial commit; historical authorship is retained and the current maintainer is credited.

package/package.json

@@ -1,19 +1,29 @@
 {
   "displayName": "Homebridge HTTP Advanced Platform",
   "name": "homebridge-http-advanced-platform",
-  "version": "2.0.0-alpha.6",
-  "description": "A platform conversion of staromeste's homebridge-http-advanced-accessory, with shared cached HTTP reads and support for existing accessory configurations.",
+  "version": "2.0.0-alpha.7",
+  "description": "Connect HTTP/HTTPS devices and REST APIs to HomeKit with JSON/XML mapping, polling and shared cached reads. A platform conversion of staromeste's homebridge-http-advanced-accessory with support for existing accessory configurations.",
   "license": "Apache-2.0",
   "keywords": [
     "homebridge-plugin",
     "supports-hap",
+    "homebridge",
     "http",
     "https",
+    "rest",
+    "api",
+    "json",
+    "xml",
+    "jsonpath",
+    "xpath",
+    "polling",
     "advanced",
     "platform",
     "accessory",
     "homekit",
     "cache",
+    "switch",
+    "sensor",
     "homebridge-http-advanced-accessory"
   ],
   "engines": {