HA Optimiser Access

HA optimiser access

Configuration index · Battery connections

HA optimiser access

The HA optimiser runs locally and uses PowerSync to verify a separate subscription: A$4/month directly, or a qualifying recurring GitHub sponsorship of at least US$3/month while active. Existing US$4/month and higher sponsors are included. Monitoring, dashboards and manual controls remain free; a PowerSync Cloud subscription does not include HA optimiser access.

Direct signup requires a card and provides one seven-day HA trial, then automatic A$4 monthly billing until cancelled. The trial starts at completed signup, independently of the existing-user transition. While Stripe verifies the first payment, a renewing trial can continue for up to two hours after its original end. Confirmed payment failure or cancellation removes that buffer; paid priority support starts after payment is confirmed. GitHub sponsorship starts paying immediately and has no HA trial. Paid HA subscriptions and qualifying sponsors include priority HA support without a response-time guarantee.

Open the integration options and choose HA optimiser access → Start pairing. Sign in on the HA account page, choose one payment option or link your sponsoring GitHub account, and approve your own temporary code. Return to HA and choose Finish pairing. After an access gap, refresh and explicitly Resume optimisation for the intended entry. Full setup and cancellation guide.

The HA dialog shows the free existing-user transition period and its deadline separately from the seven-day signup trial. It also shows whether this HA server is paired; linking GitHub or Discord on the website does not complete server pairing. Follow the next step shown in the dialog. If it says No Resume action is needed, you can close the window. Access availability does not turn on Smart Optimization or turn off Monitoring Mode.

Subscription enforcement begins on 23 October 2026 at 00:00 UTC (11:00 am AEDT). Sign up and pair your HA installation before then. This is a fixed deadline; reinstalling and pairing do not change it. Removing the integration or unlinking GitHub/Discord does not cancel payments. Use the billing portal or GitHub Sponsors to cancel.

Optimiser access and recovery

Use integration options → HA optimiser access → Refresh access to verify account status. Licence permission can last up to seven days offline, capped by its source deadline; failed verification cannot extend a trial or expired permission. The phone's Cloud login does not grant HA access.

If access ends, new optimiser actions pause and PowerSync attempts to restore only controls it owns. Failed restoration remains pending for retry, including after restart. Manual controls remain available. A newer manual or Boost EV session is preserved. If HA restarted and EV ownership is uncertain, stop the old optimiser session with the charger's normal manual controls. Do not remove a charger configuration while its recovery is pending.

Once recovery is complete and subscription access is verified, explicitly choose Resume optimisation for the intended entry. PowerSync clears the old plan and requests a fresh one. For pairing a replacement HA server, first disconnect the old installation on the HA account page; local Reset pairing does not release the hosted installation slot or reset trial history.

The authenticated status API is GET /api/power_sync/licensing?entry_id=<entry>. It exposes enforcement mode, access state, fixed validity times, pairing, recovery and Resume flags. Activation, refresh and Resume mutations require an HA administrator. Do not post .storage/power_sync.ha_licensing, pairing codes, account tokens or payment credentials in support tickets.

Link your Discord account in the HA account page to verify priority HA support. Unlinking queues role removal and does not cancel your subscription.

Field reference

The tables use the current form labels and help text. They list the conditional field union: a field can be hidden for a different battery, provider, route or available integration. The instructions above explain those conditions. Existing saved/discovered values take precedence over fresh fallbacks. Rate units follow the provider; check the displayed currency/energy unit.