Skip to content

chore: version packages - #108

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: version packages#108
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@teslemetry/node-red-contrib-teslemetry@0.6.0

Minor Changes

  • 3a03573: 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.
  • e82e608: 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.

Patch Changes

  • 77b0db2: 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.
  • 4191f24: 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.
  • 023be46: 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").
  • 7f873a8: 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.

homebridge-teslemetry@1.2.2

Patch Changes

  • a87e573: 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.
  • 27cd774: 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.
  • aeeaf5f: 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.
  • 6a555ae: 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.
  • 89412c1: 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.

@teslemetry/n8n-nodes-teslemetry@0.4.1

Patch Changes

  • b61aef4: 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.
  • 76ebb96: 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.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 15 times, most recently from 3c1038f to 1ee1ad6 Compare August 14, 2026 00:01
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1ee1ad6 to 1b4d8dc Compare August 14, 2026 01:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants