chore: version packages

packages/api/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @teslemetry/api
 
+## 0.12.0
+
+### Minor Changes
+
+- e15de8e: Updated to match upstream schema
+
 ## 0.11.3
 
 ### Patch Changes

packages/api/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@teslemetry/api",
-  "version": "0.11.3",
+  "version": "0.12.0",
   "description": "API client for Teslemetry",
   "main": "dist/index.cjs",
   "module": "dist/index.mjs",

packages/homebridge-teslemetry/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @teslemetry/homebridge-teslemetry
 
+## 1.2.2
+
+### Patch Changes
+
+- 4f09d2f: Set the Brightness characteristic's min/max/step on the charge-limit control to 50-100 (step 1), matching the telemetry clamp already applied to `ChargeLimitSoc` readings, so HomeKit itself rejects a client write outside the vehicle's supported charge-limit range instead of forwarding it to the API.
+- 2faedf7: Retry a transient `createProducts()` failure during startup discovery with capped exponential backoff instead of failing discovery outright, and evict any cached accessory for a product no longer returned by the account or newly added to the ignore list, destroying its services (and their SSE listeners) before unregistering it.
+- 6e7431f: Close two gaps left by the terminal stream health fault propagation: PresenceService's occupancy sensors now fault on a terminal stream failure and clear again once their signal reports a fresh value, and WallConnectorService's per-DIN sensors restored from Homebridge's accessory cache (before any `live_status` has arrived this run) are now hydrated and fault-checked immediately instead of being invisible to `setStreamFault()` until their first reading.
+- 52abef2: Remove the unearned "verified-by-homebridge" badge from the README (the plugin is not yet on the official verified-plugins list) and correct the energy site description: `live_status` (power flow, etc.) is delivered via real-time SSE streaming, not periodic polling — only `site_info` (backup reserve, operation mode, etc.) is polled.
+- 6056af9: Handle `stream_error` and terminal `auth_failure` from the account stream: a stream disconnect no longer logs a blanket "will attempt to reconnect" (it may be terminal), and two consecutive auth failures now mark every contact sensor that supports a HomeKit fault state (doors, TPMS, grid outage, storm watch active) as faulted instead of leaving them on their last cached value forever. A later reconnect clears the fault. See the README's Streaming Connection Issues section for recovery steps.
+- Updated dependencies [e15de8e]
+  - @teslemetry/api@0.12.0
+
 ## 1.2.1
 
 ### Patch Changes

packages/homebridge-teslemetry/package.json

@@ -1,7 +1,7 @@
 {
   "name": "homebridge-teslemetry",
   "displayName": "Homebridge Teslemetry",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "Teslemetry integration for Homebridge with real-time streaming support",
   "author": "Teslemetry",
   "license": "Apache-2.0",

packages/n8n-nodes-teslemetry/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @teslemetry/n8n-nodes-teslemetry
 
+## 0.4.1
+
+### Patch Changes
+
+- bd225a7: Add regression coverage for the Vehicle and Energy nodes' operation dispatch (endpoint and argument shape for every switch-case), Continue On Fail behavior, and the Trigger node's VIN/site filtering and signal-field validation. No product code changes.
+- 36afaac: Surface a terminal Teslemetry stream auth failure on the Trigger node as a workflow-visible error instead of leaving the trigger apparently active but silently producing no more items. Stream health handlers are now registered before the stream connects, and `closeFunction` cleanup is idempotent.
+
 ## 0.4.0
 
 ### Minor Changes
@@ -34,9 +41,11 @@
 - e0978a1: Uplift n8n integration to feature-complete status, ready for publishing
 
   **New Features:**
+
   - Added "errors" event type to Teslemetry Trigger node for monitoring vehicle error events
 
   **Improvements:**
+
   - Enhanced package.json with better metadata, author info, and keywords (including n8n-community-node-package)
   - Added node engine requirement (>=18.0.0)
   - Comprehensive README update with:
@@ -46,6 +55,7 @@
     - Links to resources and support
 
   **Status:**
+
   - Feature parity with Node-RED integration achieved
   - All vehicle operations (22/22) implemented
   - All energy operations (7/7) implemented

packages/n8n-nodes-teslemetry/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@teslemetry/n8n-nodes-teslemetry",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "n8n nodes for controlling Tesla vehicles and energy sites via Teslemetry API",
   "main": "dist/index.cjs",
   "engines": {

packages/node-red-contrib-teslemetry/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @teslemetry/node-red-contrib-teslemetry
 
+## 0.6.0
+
+### Minor Changes
+
+- bfb5058: Add a "Test credentials" button to the config node's editor, backed by a new `POST /teslemetry/test-credentials` admin route, so a token can be validated before saving instead of only failing after deploy. The route distinguishes an invalid/expired token (401/403) from any other error.
+- 63925cf: Add a `teslemetry-wall-connector` node that splits an Energy Site's `wall_connectors[]` array (e.g. from `teslemetry-energy-event`'s `live_status` payload) into one message per connector, keyed by DIN, with an optional DIN filter to isolate a single connector.
+- e15de8e: navigationSuperchargerRequest now takes a numeric Supercharger location id and a 0-3 trip order, matching the public spec
+
+### Patch Changes
+
+- 7988098: Retry the config node's initial vehicle/energy-site fetch on failure instead of caching that error for the node's whole lifetime - a transient API/network blip now clears on its own, and a corrected token recovers cleanly on the next redeploy instead of leaving stale state behind.
+- 5859d52: Fix vehicle-command, energy-command, and energy-history nodes staying permanently inert when constructed while the config node's initial products fetch is still failing - they now re-check that error per message instead of once at construction, so a node built during that window becomes functional as soon as the fetch recovers, with no redeploy needed.
+- 20e5ec7: Reject an invalid `msg.daysOfWeek` on `addChargeSchedule`/`addPreconditionSchedule` before calling the API, instead of only checking that it's a non-empty string. Accepts `"All"`, `"Weekdays"`, or a comma separated list of day names (e.g. `"Monday,Wednesday"`).
+- 3f5ff20: Document that `setTimeOfUseSettings` replaces the site's entire time-of-use schedule rather than merging with it, in the node's help text, command dropdown, and README.
+
 ## 0.5.0
 
 ### Minor Changes

packages/node-red-contrib-teslemetry/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@teslemetry/node-red-contrib-teslemetry",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "Node-RED nodes for controlling Tesla vehicles and energy sites via Teslemetry API",
   "main": "dist/index.cjs",
   "engines": {