In beta and available on request. The additions in this overview require the matching integration or controller update and are not confirmed as part of the standard customer release. Request them through your existing Eniris support conversation. The status applies to these additions, not to every existing function of the devices listed elsewhere on this page.
| Model / system | Beta addition | Validation and conditions |
|---|---|---|
| Custom control logic | Grid power per phase (block "Grid power per phase") | In beta and available on request. Requires phase readings from the grid meter. Validated on one installation: the block values matched the grid meter per phase, and a per-phase export protection logic kept every phase in import during a monitored test with solar production. |
| Custom control logic | Calendar-month peak demand | In beta and available on request. Software tests passed; commissioning and physical validation remain required. Seed from verified meter history when starting mid-month. |
| Custom control logic | Actual peak-shaving reserve energy | In beta and available on request. Reads the scheduler's reserved partition instead of assuming it is full from total battery SOC. Software-tested; physical validation pending. |
| Peak Shaving Plus with custom logic | Dynamic primary peak thresholds | In beta and available on request. Preserves the secondary self-consumption targets and configured reserve fraction. Software-tested; physical validation pending. |
| Custom control logic | Reserve-based forecast peak limit | In beta and available on request. Software tests passed; physical validation remains required. Requires all 96 forecast quarters and genuinely available battery energy and discharge power. |
See integration details for connection requirements and operating limitations.
The measurement block Grid power per phase exposes the measured grid active power on L1, L2 and L3 to custom control logic (positive is import, negative is export). It requires a grid meter that provides the relevant phase readings and a controller build containing the extension. A phase that the meter does not measure gives no value; missing measurements must not be interpreted as zero consumption, so use a "Replace missing value" block where the flow needs a fallback.
Typical use is protection against export on a single phase while the site as a whole stays in import. Because batteries and solar inverters usually act symmetrically on all three phases, the total import needed to keep the weakest phase above a margin can be calculated from the meter: grid power minus three times the weakest phase power plus three times the margin. A peak shaving block with battery thresholds can then hold the grid import at that level while the weakest phase is low. Avoid feeding a battery setpoint back from the battery's own measured power: short gaps in battery readings can make such a loop settle at zero. Grid limits and battery protections of the settings keep applying.
These beta blocks require a matching controller build and are not yet confirmed in the standard customer release. Request them through your existing Eniris support conversation.
Monthly peak demand records the highest completed, aligned 15-minute grid import average in the installation's calendar month. It retains state across restarts and resets at local month start. When commissioning during a month, Eniris must first seed the current peak from verified local meter history. Partial starting quarters and intervals with missing readings are not extrapolated. This sampled estimate does not replace the billing meter.
The reserve-based block estimates a conservative import threshold over the next 24 hours from the grid forecast, the battery energy actually available for peak shaving and its available discharge power. It assumes no future recharge and adds a configurable safety margin. A missing input or forecast quarter produces no limit, so the flow must retain an explicit fallback. Combine the forecast limit with the current monthly peak using the higher value.
The blocks only calculate values. They do not automatically reserve battery capacity, enable grid charging, replace battery protections or alter grid limits. Those settings, the charging limit, fallback behaviour and the complete flow require site-specific commissioning. Forecast uncertainty remains; a lower bill or a guaranteed peak cannot be promised. Physical operation has not yet been validated for these additions.
The peak-shaving reserve source exposes the execution state's actual reserved energy and capacity. Missing partition information or stale battery measurements yields no value. It does not estimate reserve fullness from the battery's total state of charge.
With Peak Shaving Plus active, dynamic thresholds apply to the primary peak-shaving partition. The secondary self-consumption targets and reserved capacity fraction remain separate. A matching controller build is required for this beta correction; it must be verified on the installation before reporting working control.