Setup PV Forecaster
Setting up PV forecasted devices is straightforward!
Our basic pricing plan supports a single PV forecaster for small sites, and both PV and UCL forecasters for medium, large, and extra-large sites.
If the energy measurements of the PV asset are grouped under a single collector, integration is simple—just add the forecasted device to the site's device configuration:
{
"name": "LR34_001",
"collector": "main_collector",
"type": "forecasted_series_3phase",
"line_current": 32,
"should_be_aggregated": false
}
Forecasted 3-Phase Device
- 0-item-properties
- null
- 0-item-properties
- null
phase_permutations object
Specify the phase mapping between this asset (child) and its parent collector (parent). Leave unset when the wiring is unknown; phase-aware control (use_topology) requires every asset's mapping to be declared, so a single unset mapping makes the controller fall back to the worst case.
The name of the device itself. This value will be used as the asset ID in the rest of the API.
The name of the collector to which this device is connected.
ingress_validation object
Overrides the site-level ingress validation config for this asset. When set, controls how often measurements are expected during active and inactive transactions. When null, the site-level configuration is used.
forecasted_series_3phaseforecasted_series_3phaseThe line current in Ampere.
Defines the type of forecast to be used for this device.
falseHow the controller may curtail this device's production to respect the grid minimum. NONE never curtails; CONTINUOUS curtails to any level. Only relevant for PV devices.
noneFor more details, take a look at the site-configuration documentation.
We will detect these devices when a site is created or updated and will create the necessary forecasters. If you have created a site with a forecasted devices like the one above, it's a good idea to check the developer portal and verify that the forecasting task is visible.
If PV measurements are distributed across multiple collectors, we currently require you to aggregate these measurements into a virtual device and send us the aggregated data.