Skip to content

Provider AEMO VPP

bolagnaise edited this page Oct 15, 2026 · 1 revision

AEMO VPP and spike detection

Select AEMO VPP for an Australian plan using generic AEMO spike detection without a dedicated account tariff model. GloBird has its own provider reference; AGL pricing has its own reference. A retailer's VPP enrollment and PowerSync's local spike control are separate.

Choose the correct NEM region and account Spike threshold. The normal Australian fallback is $3,000/MWh, but use the terms and displayed units for your plan. Enable spike detection only when it is intended for the account. Configure the normal import/export tariff as well; spike detection is not a replacement for everyday TOU prices.

Battery discharge requires a supported writable connection and the relevant control permissions. Monitoring-only routes can report decisions without sending battery commands. Turning off spike detection stops new PowerSync spike dispatch and can trigger restoration of state already owned by PowerSync. It does not disable an external VPP, the battery's native tariff behaviour or a user-started force action.

Check the current NEM region/market value, feature status and decisions at the same time as any event. Use device readback and measured power to establish dispatch, rather than treating a forecast spike or scheduled action as physical export.

AEMO spike detection and recovery

When spike response is enabled on a control-capable route, PowerSync requests discharge using the configured threshold (default $3,000/MWh) and attempts recovery of its owned action afterward. The active path depends on the optimization mode. Monitoring, ownership, connection permissions and failures can prevent dispatch or restoration; an enabled setting is not physical proof.

Tesla Powerwall

The applicable native/generic path can save the current tariff/mode and upload a spike tariff, then attempt to restore its saved state. A Smart Optimization path has separate planning/execution ownership. Verify the running path and device readback rather than assuming every mode uses one manager.

Other supported writable routes

Supported adapters can request discharge and later restoration through their available controls. A monitoring-only route or an upstream integration exposing only telemetry cannot acquire dispatch merely because AEMO settings are visible. Start/end notifications and event status are not measured export.

Turning spike detection off

From v2.12.1380, saving Spike Detection → off blocks new AEMO spike discharge commands immediately. Saving the enable switch, NEM region, or spike threshold also reloads PowerSync automatically so the running handler uses the saved settings. In the mobile app, tap Save Changes after editing the switch.

If PowerSync already started a spike event, disabling the feature restores the tariff and operation mode it saved before that event. Tesla recovery also runs after a restart when spike detection is off. Failed restoration stays pending and is retried; PowerSync does not return Tesla to autonomous mode while its spike tariff still needs restoration. If the saved tariff is missing or invalid, check the warning log and restore the correct tariff in the Tesla app.

Monitoring Mode blocks new hardware commands and preserves pending recovery until control is permitted again. AEMO spike detection is separate from Amber Spike Protection and Price Spike Alerts. Turning it off does not stop ordinary Tesla tariff behaviour, Smart Optimization, or a user-started discharge.


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.

AEMO spike detection — initial setup

Field Meaning / input Fallback / limits
Enable spike detection Required for Globird and AEMO VPP plans that include spike export payments. Disable if your plan does not pay for spike exports. Saved/detected value or the form’s shown fallback
NEM region Your NEM region determines which AEMO price feed is monitored. Check your electricity bill if unsure. Saved/detected value or the form’s shown fallback
Spike threshold Battery exports when the AEMO wholesale price exceeds this value. Default 3,000 in the selected market price unit matches most Globird and VPP plans. Only change if your plan specifies a different threshold. Fallback 3000.0; 0–20000; step 100

Clone this wiki locally