Priestley Place Charge HQ

15kW Fox ESS H3 · CQ6-L8 battery stack (47.92kWh nominal) · 44 panels / 20.9kW array
Monitoring only
 
Data sources

Inverter Connection

FoxESS Cloud
Only change this if you're routing through your own CORS proxy in front of FoxESS Cloud.
Sent as X-Proxy-Secret on both FoxESS and Solcast calls if this and the matching base URL below are set — one worker, one secret, both APIs.

Forecast Sources

BOM's own open-data feed has had outages during platform upgrades — if a BOM request fails, this automatically falls back to the blended model for that run.

Site & System

 
System losses (soiling, wiring, inverter) — typical 0.78–0.85
Usage history & accuracy

Usage History

For prediction
Log at least 3 days and the forecast below will predict tomorrow's usage from your own history (recency-weighted, split by weekday/weekend, and temperature-adjusted once you've logged a few hot/cold days) instead of the fallback figure. Logging actual solar made lets the Prediction Accuracy card below check the weather/Solcast/BOM forecasts against reality.
Tariffs

Time of Use

VPP event window (optional — leave blank if not on a VPP plan)
When set, the plan will weigh selling stored battery charge into the grid during this window against holding it for a later peak-avoidance saving, and recommend whichever is worth more — shown as a "VPP sell" item below, not yet sent to any device.

Flat Rate

Real Usage: TOU vs Flat

From your energy provider's interval export — uses the tariffs above
Provider Comparison
Save other providers' rates here to compare against your real usage — this doesn't affect the live plan above, which always uses the "Tariffs" section as your active plan. A provider's fields here are all optional; fill in only what you actually have a quote for.
Planning tool, not yet connected to the inverter. Solar output is estimated from Open-Meteo's shortwave radiation forecast at your site (kWp × GHI/1000 × performance ratio, with a simple temperature derate above 25°C) — treat it as an engineering estimate, not a guarantee. Load is your typical daily usage spread over a chosen shape, not a measured profile. The scheduler is a rule-based charge/discharge planner (solar-first, battery-before-grid, pre-charge from off-peak grid only when the forecast can't otherwise cover the next peak window) — it doesn't push anything to the H3. Once you're ready to connect (FoxESS Cloud API or local Modbus), this same logic can drive real setpoints.