@enyo-energy/energy-app-sdk 1.24.0 → 1.25.0

package/README.md

@@ -184,7 +184,7 @@ The SDK exposes several layered building blocks. Pick the one that matches the k
 | List known WiFi SSIDs in range | [`useWifi()`](#usewifi-energyappwifi) |
 | Query historical timeseries (PV, battery, meter, …) | [`useTimeseries()`](#usetimeseries-energyapptimeseries) |
 | Read site location (zip or coordinates) | [`useLocation()`](#uselocation-energyapplocation) |
-| Read grid connection point (fuse, phases, max power) | [`useGridConnectionPoint()`](#usegridconnectionpoint-energyappgridconnectionpoint) |
+| Read grid connection point (fuse, phases, max power, charger limit) | [`useGridConnectionPoint()`](#usegridconnectionpoint-energyappgridconnectionpoint) |
 | Retrieve secrets from the developer org secret store | [`useSecretManager()`](#usesecretmanager-energyappsecretmanager) |
 | Submit energy-manager diagnostics | [`useDiagnostics()`](#usediagnostics-energyappdiagnostics) |
 | Register a weather / PV / dynamic-price forecast provider | [`useWeatherForecasting()`](#useweatherforecasting-energyappweatherforecasting) / [`usePvForecasting()`](#usepvforecasting-energyapppvforecasting) / [`useDynamicPriceForecast()`](#usedynamicpriceforecast-energyappdynamicpriceforecast) |
@@ -1592,13 +1592,18 @@ if (full) console.log(`lat=${full.latitude} lon=${full.longitude}`);
 
 #### `useGridConnectionPoint(): EnergyAppGridConnectionPoint`
 
-Read the site's grid connection details — main fuse rating, number of phases, and the maximum allowed grid power. Use this to size dispatch envelopes and avoid violating the contractual cap.
+Read the site's grid connection details — main fuse rating, number of phases, the maximum allowed grid power, and the total power that load balancing may allocate to EV chargers. Use this to size dispatch envelopes and avoid violating the contractual cap.
+
+`chargerLimitW` is optional: when it is not configured, load balancing falls back to `DEFAULT_CHARGER_LIMIT_W` (11 kW).
 
 ```typescript
+import {DEFAULT_CHARGER_LIMIT_W} from "@enyo-energy/energy-app-sdk";
+
 const gcp = energyApp.useGridConnectionPoint();
 const point = await gcp.getGridConnectionPoint();
 if (point) {
     console.log(`Fuse ${point.fuseAmpere}A across ${point.numberOfPhases} phases`);
+    console.log(`Charger limit ${point.chargerLimitW ?? DEFAULT_CHARGER_LIMIT_W} W`);
 }
 ```
 
@@ -1725,6 +1730,14 @@ await tariffs.publishPrices(EnyoTariffDirectionEnum.Consumption, {
 });
 ```
 
+An entry may carry an optional `gridFeeGrossPerKwh`: the gross grid fee **contained in**
+`pricePerKwh`, in currency units per kWh. It is a breakdown only — `pricePerKwh` is always the
+total, so never compute `pricePerKwh + gridFeeGrossPerKwh`.
+
+```typescript
+entries.push({ timestampIso: '2026-05-23T10:00:00Z', pricePerKwh: 0.31, gridFeeGrossPerKwh: 0.09 });
+```
+
 **Calling `setTariff` is the activation signal.** Return `AuthenticationRequired` or
 `OnboardingRequired` from the handler to have the host send the user somewhere, and carry the
 `authenticationUrl` / `onboardingGuideId` that makes it actionable; when that flow later completes,

package/dist/cjs/implementations/onboarding-v2/define-onboarding-guide-v2.cjs

@@ -306,7 +306,11 @@ exports.onboardingV2Block = {
      * Filter it. `deviceTypes` is what turns this from "here are the six EEBUS
      * devices in the house" into "here is your heat pump", and with one match it
      * skips the screen entirely instead of asking a question with one possible
-     * answer.
+     * answer. `vendors` narrows it further, by the `brand` a peer announces —
+     * use it where the device type cannot separate the candidates (two EEBUS
+     * heat pumps in one house), or where the guide is written for one
+     * manufacturer and must not offer a competitor's device. The two filters are
+     * conjunctive: a peer must satisfy both to be offered.
      *
      * The picker is drawn from what mDNS discovery found, so the guide must have
      * scanned — keep {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its
@@ -327,8 +331,9 @@ exports.onboardingV2Block = {
      * paired peer into appliances.
      *
      * @param id - Stable block id, unique within the guide.
-     * @param options - Screen wording, optional `deviceTypes` filter, skip
-     *   behaviour, and the `paired` / `not-found` / `failure` routing handles.
+     * @param options - Screen wording, optional `deviceTypes` and `vendors`
+     *   filters, skip behaviour, and the `paired` / `not-found` / `failure`
+     *   routing handles.
      * @returns The EEBUS device-select block.
      *
      * @example
@@ -336,6 +341,7 @@ exports.onboardingV2Block = {
      * onboardingV2Block.eebusDeviceSelect('pair', {
      *     headline: t('Wärmepumpe auswählen', 'Select the heat pump'),
      *     deviceTypes: [EnyoEebusDeviceTypeEnum.HeatPumpAppliance],
+     *     vendors: ['Vaillant'],
      *     outcomes: [
      *         {id: 'ok',    value: EnyoOnboardingV2EebusPairOutcome.Paired,   label: t('Gekoppelt', 'Paired')},
      *         {id: 'none',  value: EnyoOnboardingV2EebusPairOutcome.NotFound, label: t('Nichts gefunden', 'Nothing found')},

package/dist/cjs/implementations/onboarding-v2/define-onboarding-guide-v2.d.cts

@@ -254,7 +254,11 @@ export declare const onboardingV2Block: {
      * Filter it. `deviceTypes` is what turns this from "here are the six EEBUS
      * devices in the house" into "here is your heat pump", and with one match it
      * skips the screen entirely instead of asking a question with one possible
-     * answer.
+     * answer. `vendors` narrows it further, by the `brand` a peer announces —
+     * use it where the device type cannot separate the candidates (two EEBUS
+     * heat pumps in one house), or where the guide is written for one
+     * manufacturer and must not offer a competitor's device. The two filters are
+     * conjunctive: a peer must satisfy both to be offered.
      *
      * The picker is drawn from what mDNS discovery found, so the guide must have
      * scanned — keep {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its
@@ -275,8 +279,9 @@ export declare const onboardingV2Block: {
      * paired peer into appliances.
      *
      * @param id - Stable block id, unique within the guide.
-     * @param options - Screen wording, optional `deviceTypes` filter, skip
-     *   behaviour, and the `paired` / `not-found` / `failure` routing handles.
+     * @param options - Screen wording, optional `deviceTypes` and `vendors`
+     *   filters, skip behaviour, and the `paired` / `not-found` / `failure`
+     *   routing handles.
      * @returns The EEBUS device-select block.
      *
      * @example
@@ -284,6 +289,7 @@ export declare const onboardingV2Block: {
      * onboardingV2Block.eebusDeviceSelect('pair', {
      *     headline: t('Wärmepumpe auswählen', 'Select the heat pump'),
      *     deviceTypes: [EnyoEebusDeviceTypeEnum.HeatPumpAppliance],
+     *     vendors: ['Vaillant'],
      *     outcomes: [
      *         {id: 'ok',    value: EnyoOnboardingV2EebusPairOutcome.Paired,   label: t('Gekoppelt', 'Paired')},
      *         {id: 'none',  value: EnyoOnboardingV2EebusPairOutcome.NotFound, label: t('Nichts gefunden', 'Nothing found')},

package/dist/cjs/implementations/onboarding-v2/onboarding-v2-validators.cjs

@@ -614,9 +614,9 @@ function isPickerBlock(block) {
  *   it would either be skipped along with it or offer a way past the pick. Both
  *   are errors rather than warnings, because there is no reading of the step
  *   that behaves sensibly.
- * - **An empty filter is not a filter.** `detectedAt: []` / `deviceTypes: []`
- *   match nothing, so the picker can only ever reach its `not-found` branch.
- *   Omitting the property is how "no filter" is expressed.
+ * - **An empty filter is not a filter.** `detectedAt: []` / `deviceTypes: []` /
+ *   `vendors: []` match nothing, so the picker can only ever reach its
+ *   `not-found` branch. Omitting the property is how "no filter" is expressed.
  * - **A picker that renders should say something.** With neither a headline of
  *   its own nor a step title, the installer gets a bare list — a warning, since
  *   the host has a default caption.
@@ -655,6 +655,10 @@ function validatePickerBlocks(step, at, errors, warnings) {
                 errors.push(`${at}: ${label(block)} has an empty \`deviceTypes\` filter, which matches no peer — ` +
                     'omit the property to offer every discovered peer.');
             }
+            if (block.vendors && block.vendors.length === 0) {
+                errors.push(`${at}: ${label(block)} has an empty \`vendors\` filter, which matches no peer — ` +
+                    'omit the property to offer peers of every vendor.');
+            }
         }
         if (!block.headline?.length && !step.title?.length) {
             warnings.push(`${at}: ${label(block)} has no headline and sits on a step with no title — ` +

package/dist/cjs/packages/energy-app-grid-connection-point.d.cts

@@ -4,7 +4,8 @@ import { EnyoGridConnectionPoint } from "../types/enyo-grid-connection-point.cjs
  *
  * The grid connection point describes the physical interface between the
  * local electrical installation and the public grid, including the main
- * fuse rating, the number of phases, and the maximum allowed grid power.
+ * fuse rating, the number of phases, the maximum allowed grid power, and the
+ * total power that load balancing may allocate to EV chargers.
  * Energy apps consume this information to size grid-import/export budgets,
  * enforce per-phase current limits, and respect contractual or regulatory
  * power caps.
@@ -21,12 +22,16 @@ export interface EnergyAppGridConnectionPoint {
      *
      * @example
      * ```typescript
+     * import {DEFAULT_CHARGER_LIMIT_W} from "@enyo-energy/energy-app-sdk";
+     *
      * const gridConnectionPoint = energyApp.useGridConnectionPoint();
      * const details = await gridConnectionPoint.getGridConnectionPoint();
      * if (details) {
      *     console.log(`Fuse: ${details.fuseAmpere} A`);
      *     console.log(`Phases: ${details.numberOfPhases}`);
      *     console.log(`Power limit: ${details.powerLimitW} W`);
+     *     const chargerLimitW = details.chargerLimitW ?? DEFAULT_CHARGER_LIMIT_W;
+     *     console.log(`Charger limit: ${chargerLimitW} W`);
      * }
      * ```
      */

package/dist/cjs/types/enyo-charger-appliance.cjs

@@ -69,4 +69,10 @@ var EnyoChargerApplianceAvailableFeaturesEnum;
     EnyoChargerApplianceAvailableFeaturesEnum["PvSurplusMode"] = "PvSurplusMode";
     /** If the charger supports switching between three-phase and one-phase charging */
     EnyoChargerApplianceAvailableFeaturesEnum["ThreeToOnePhaseSwitch"] = "ThreeToOnePhaseSwitch";
+    /**
+     * If the charger requires the vehicle to be disconnected before a new charge can be started.
+     * Once the charger is in {@link EnyoChargerApplianceStatusEnum.Finishing}, no new charge can be
+     * started remotely; the customer has to unplug the vehicle and plug it in again.
+     */
+    EnyoChargerApplianceAvailableFeaturesEnum["DisconnectToRestartCharge"] = "DisconnectToRestartCharge";
 })(EnyoChargerApplianceAvailableFeaturesEnum || (exports.EnyoChargerApplianceAvailableFeaturesEnum = EnyoChargerApplianceAvailableFeaturesEnum = {}));

package/dist/cjs/types/enyo-charger-appliance.d.cts

@@ -82,7 +82,13 @@ export declare enum EnyoChargerApplianceAvailableFeaturesEnum {
     /** If the Charger supprots a pv surplus mode */
     PvSurplusMode = "PvSurplusMode",
     /** If the charger supports switching between three-phase and one-phase charging */
-    ThreeToOnePhaseSwitch = "ThreeToOnePhaseSwitch"
+    ThreeToOnePhaseSwitch = "ThreeToOnePhaseSwitch",
+    /**
+     * If the charger requires the vehicle to be disconnected before a new charge can be started.
+     * Once the charger is in {@link EnyoChargerApplianceStatusEnum.Finishing}, no new charge can be
+     * started remotely; the customer has to unplug the vehicle and plug it in again.
+     */
+    DisconnectToRestartCharge = "DisconnectToRestartCharge"
 }
 /**
  * Phase configurations a charger can operate in.

package/dist/cjs/types/enyo-eebus.d.cts

@@ -80,6 +80,19 @@ export interface EebusDiscoveredDevice {
     ski: string;
     /** Human-readable device name advertised during discovery */
     deviceName?: string;
+    /**
+     * The vendor the peer announced in its SHIP record (the `brand` TXT key),
+     * verbatim and untranslated — e.g. `Vaillant`, `KEBA`, `Viessmann`.
+     *
+     * The peer's own claim, made before anything is paired, which is what makes
+     * it usable as a discovery filter next to {@link deviceType}: see
+     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.vendors}. Spelling and case
+     * are whatever the firmware ships, so compare case-insensitively rather
+     * than with `===`.
+     *
+     * Absent when the peer advertises no `brand`.
+     */
+    brand?: string;
     /** IP address or hostname of the device */
     host: string;
     /** Port number for the SHIP connection */

package/dist/cjs/types/enyo-electricity-tariff.d.cts

@@ -180,6 +180,15 @@ export interface EnyoTariffPriceEntry {
     timestampIso: string;
     /** Price per kWh for this interval, in the tariff's currency. */
     pricePerKwh: number;
+    /**
+     * Optional gross grid fee per kWh contained in {@link pricePerKwh}, in the
+     * tariff's currency (not cent).
+     *
+     * Informational only: it breaks down the price, it is **never added** to it.
+     * {@link pricePerKwh} is always the total price. Only meaningful when the
+     * series declares {@link EnyoPriceComponentEnum.GridFee} in its `includes`.
+     */
+    gridFeeGrossPerKwh?: number;
 }
 /**
  * Prices for one direction over a requested range.

package/dist/cjs/types/enyo-grid-connection-point.cjs

@@ -1,2 +1,10 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.DEFAULT_CHARGER_LIMIT_W = void 0;
+/**
+ * Default total charger power limit, in watts (W), applied by load balancing
+ * when {@link EnyoGridConnectionPoint.chargerLimitW} is not configured.
+ *
+ * 11 kW corresponds to the common three-phase 16 A wallbox rating.
+ */
+exports.DEFAULT_CHARGER_LIMIT_W = 11000;

package/dist/cjs/types/enyo-grid-connection-point.d.cts

@@ -52,4 +52,25 @@ export interface EnyoGridConnectionPoint {
      * `powerLimitW` applies.
      */
     desiredKwLimit?: number;
+    /**
+     * Maximum active power, in watts (W), that the load balancing may allocate
+     * to EV chargers in total at this grid connection point.
+     *
+     * This caps the charging power distributed across all connected wallboxes,
+     * independently of what the grid connection as a whole could deliver: it
+     * lets an installer keep headroom for the rest of the household, or honour
+     * a charger-specific limit agreed with the grid operator (e.g. §14a EnWG
+     * style restrictions).
+     *
+     * Optional. When `undefined`, load balancing assumes the default of
+     * {@link DEFAULT_CHARGER_LIMIT_W} (11 kW).
+     */
+    chargerLimitW?: number;
 }
+/**
+ * Default total charger power limit, in watts (W), applied by load balancing
+ * when {@link EnyoGridConnectionPoint.chargerLimitW} is not configured.
+ *
+ * 11 kW corresponds to the common three-phase 16 A wallbox rating.
+ */
+export declare const DEFAULT_CHARGER_LIMIT_W = 11000;

package/dist/cjs/types/enyo-onboarding-v2-eebus-device-select.d.cts

@@ -47,6 +47,17 @@ export interface EnyoOnboardingV2EebusPeer {
     deviceName?: string;
     /** Brand or model the peer advertised, if any. */
     deviceModel?: string;
+    /**
+     * The vendor the peer announced during discovery (the SHIP `brand` TXT
+     * key), verbatim and untranslated, if any.
+     *
+     * The same claim {@link EnyoOnboardingV2EebusDeviceSelectBlock.vendors}
+     * filters the picker by, passed on so a handler that serves several
+     * manufacturers can pick the right appliance shape without re-reading
+     * discovery. Case and spelling are the firmware's — compare
+     * case-insensitively. Absent means the peer announced no vendor.
+     */
+    brand?: string;
     /**
      * The device type the peer announced, when it announced one this SDK knows.
      *
@@ -118,7 +129,8 @@ export interface EnyoOnboardingV2EebusDeviceSelectRequest {
     /**
      * `true` when the host paired on the installer's behalf because exactly one
      * peer matched the block's
-     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.deviceTypes} filter and
+     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.deviceTypes} and
+     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.vendors} filters and
      * {@link EnyoOnboardingV2PickerBlockBase.autoSelectSingleMatch} was left on —
      * the screen was never rendered.
      *

package/dist/cjs/types/enyo-onboarding-v2.d.cts

@@ -679,6 +679,31 @@ export interface EnyoOnboardingV2EebusDeviceSelectBlock extends EnyoOnboardingV2
      * is a validation error.
      */
     deviceTypes?: EnyoEebusDeviceTypeEnum[];
+    /**
+     * Offer only peers announcing one of these vendors; everything else is left
+     * out of the list and does not count towards
+     * {@link EnyoOnboardingV2PickerBlockBase.autoSelectSingleMatch}.
+     *
+     * The companion of {@link deviceTypes} for the case that filter cannot
+     * separate: a house with two EEBUS heat pumps, or a guide that is written
+     * for one manufacturer's device and would otherwise offer a competitor's as
+     * a candidate for its own pairing flow. Both filters are **conjunctive** —
+     * a peer must satisfy every filter present to be offered.
+     *
+     * Matched against the vendor the peer announced
+     * ({@link EebusDiscoveredDevice.brand}, the SHIP `brand` TXT key),
+     * **case-insensitively and ignoring surrounding whitespace**, since the
+     * spelling is whatever the firmware ships. It is otherwise an exact match,
+     * not a substring one: `KEBA` does not match `KEBA AG`, so list the
+     * spellings a vendor is known to announce rather than hoping for one.
+     *
+     * A peer that announces no vendor is treated the same way an unknown device
+     * type is: it survives an omitted filter and is excluded by any filter
+     * present, so a guide can never pair something it did not ask for. Omit the
+     * property to offer peers of every vendor; an **empty array** filters
+     * everything out and is a validation error.
+     */
+    vendors?: string[];
 }
 /**
  * A fixed URL the installer opens or copies — a vendor portal, a manual, a

package/dist/cjs/version.cjs

@@ -9,7 +9,7 @@ exports.getSdkVersion = getSdkVersion;
 /**
  * Current version of the enyo Energy App SDK.
  */
-exports.SDK_VERSION = '1.24.0';
+exports.SDK_VERSION = '1.25.0';
 /**
  * Gets the current SDK version.
  * @returns The semantic version string of the SDK

package/dist/cjs/version.d.cts

@@ -5,7 +5,7 @@
 /**
  * Current version of the enyo Energy App SDK.
  */
-export declare const SDK_VERSION = "1.24.0";
+export declare const SDK_VERSION = "1.25.0";
 /**
  * Gets the current SDK version.
  * @returns The semantic version string of the SDK

package/dist/implementations/onboarding-v2/define-onboarding-guide-v2.d.ts

@@ -254,7 +254,11 @@ export declare const onboardingV2Block: {
      * Filter it. `deviceTypes` is what turns this from "here are the six EEBUS
      * devices in the house" into "here is your heat pump", and with one match it
      * skips the screen entirely instead of asking a question with one possible
-     * answer.
+     * answer. `vendors` narrows it further, by the `brand` a peer announces —
+     * use it where the device type cannot separate the candidates (two EEBUS
+     * heat pumps in one house), or where the guide is written for one
+     * manufacturer and must not offer a competitor's device. The two filters are
+     * conjunctive: a peer must satisfy both to be offered.
      *
      * The picker is drawn from what mDNS discovery found, so the guide must have
      * scanned — keep {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its
@@ -275,8 +279,9 @@ export declare const onboardingV2Block: {
      * paired peer into appliances.
      *
      * @param id - Stable block id, unique within the guide.
-     * @param options - Screen wording, optional `deviceTypes` filter, skip
-     *   behaviour, and the `paired` / `not-found` / `failure` routing handles.
+     * @param options - Screen wording, optional `deviceTypes` and `vendors`
+     *   filters, skip behaviour, and the `paired` / `not-found` / `failure`
+     *   routing handles.
      * @returns The EEBUS device-select block.
      *
      * @example
@@ -284,6 +289,7 @@ export declare const onboardingV2Block: {
      * onboardingV2Block.eebusDeviceSelect('pair', {
      *     headline: t('Wärmepumpe auswählen', 'Select the heat pump'),
      *     deviceTypes: [EnyoEebusDeviceTypeEnum.HeatPumpAppliance],
+     *     vendors: ['Vaillant'],
      *     outcomes: [
      *         {id: 'ok',    value: EnyoOnboardingV2EebusPairOutcome.Paired,   label: t('Gekoppelt', 'Paired')},
      *         {id: 'none',  value: EnyoOnboardingV2EebusPairOutcome.NotFound, label: t('Nichts gefunden', 'Nothing found')},

package/dist/implementations/onboarding-v2/define-onboarding-guide-v2.js

@@ -298,7 +298,11 @@ export const onboardingV2Block = {
      * Filter it. `deviceTypes` is what turns this from "here are the six EEBUS
      * devices in the house" into "here is your heat pump", and with one match it
      * skips the screen entirely instead of asking a question with one possible
-     * answer.
+     * answer. `vendors` narrows it further, by the `brand` a peer announces —
+     * use it where the device type cannot separate the candidates (two EEBUS
+     * heat pumps in one house), or where the guide is written for one
+     * manufacturer and must not offer a competitor's device. The two filters are
+     * conjunctive: a peer must satisfy both to be offered.
      *
      * The picker is drawn from what mDNS discovery found, so the guide must have
      * scanned — keep {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its
@@ -319,8 +323,9 @@ export const onboardingV2Block = {
      * paired peer into appliances.
      *
      * @param id - Stable block id, unique within the guide.
-     * @param options - Screen wording, optional `deviceTypes` filter, skip
-     *   behaviour, and the `paired` / `not-found` / `failure` routing handles.
+     * @param options - Screen wording, optional `deviceTypes` and `vendors`
+     *   filters, skip behaviour, and the `paired` / `not-found` / `failure`
+     *   routing handles.
      * @returns The EEBUS device-select block.
      *
      * @example
@@ -328,6 +333,7 @@ export const onboardingV2Block = {
      * onboardingV2Block.eebusDeviceSelect('pair', {
      *     headline: t('Wärmepumpe auswählen', 'Select the heat pump'),
      *     deviceTypes: [EnyoEebusDeviceTypeEnum.HeatPumpAppliance],
+     *     vendors: ['Vaillant'],
      *     outcomes: [
      *         {id: 'ok',    value: EnyoOnboardingV2EebusPairOutcome.Paired,   label: t('Gekoppelt', 'Paired')},
      *         {id: 'none',  value: EnyoOnboardingV2EebusPairOutcome.NotFound, label: t('Nichts gefunden', 'Nothing found')},

package/dist/implementations/onboarding-v2/onboarding-v2-validators.js

@@ -608,9 +608,9 @@ function isPickerBlock(block) {
  *   it would either be skipped along with it or offer a way past the pick. Both
  *   are errors rather than warnings, because there is no reading of the step
  *   that behaves sensibly.
- * - **An empty filter is not a filter.** `detectedAt: []` / `deviceTypes: []`
- *   match nothing, so the picker can only ever reach its `not-found` branch.
- *   Omitting the property is how "no filter" is expressed.
+ * - **An empty filter is not a filter.** `detectedAt: []` / `deviceTypes: []` /
+ *   `vendors: []` match nothing, so the picker can only ever reach its
+ *   `not-found` branch. Omitting the property is how "no filter" is expressed.
  * - **A picker that renders should say something.** With neither a headline of
  *   its own nor a step title, the installer gets a bare list — a warning, since
  *   the host has a default caption.
@@ -649,6 +649,10 @@ function validatePickerBlocks(step, at, errors, warnings) {
                 errors.push(`${at}: ${label(block)} has an empty \`deviceTypes\` filter, which matches no peer — ` +
                     'omit the property to offer every discovered peer.');
             }
+            if (block.vendors && block.vendors.length === 0) {
+                errors.push(`${at}: ${label(block)} has an empty \`vendors\` filter, which matches no peer — ` +
+                    'omit the property to offer peers of every vendor.');
+            }
         }
         if (!block.headline?.length && !step.title?.length) {
             warnings.push(`${at}: ${label(block)} has no headline and sits on a step with no title — ` +

package/dist/packages/energy-app-grid-connection-point.d.ts

@@ -4,7 +4,8 @@ import { EnyoGridConnectionPoint } from "../types/enyo-grid-connection-point.js"
  *
  * The grid connection point describes the physical interface between the
  * local electrical installation and the public grid, including the main
- * fuse rating, the number of phases, and the maximum allowed grid power.
+ * fuse rating, the number of phases, the maximum allowed grid power, and the
+ * total power that load balancing may allocate to EV chargers.
  * Energy apps consume this information to size grid-import/export budgets,
  * enforce per-phase current limits, and respect contractual or regulatory
  * power caps.
@@ -21,12 +22,16 @@ export interface EnergyAppGridConnectionPoint {
      *
      * @example
      * ```typescript
+     * import {DEFAULT_CHARGER_LIMIT_W} from "@enyo-energy/energy-app-sdk";
+     *
      * const gridConnectionPoint = energyApp.useGridConnectionPoint();
      * const details = await gridConnectionPoint.getGridConnectionPoint();
      * if (details) {
      *     console.log(`Fuse: ${details.fuseAmpere} A`);
      *     console.log(`Phases: ${details.numberOfPhases}`);
      *     console.log(`Power limit: ${details.powerLimitW} W`);
+     *     const chargerLimitW = details.chargerLimitW ?? DEFAULT_CHARGER_LIMIT_W;
+     *     console.log(`Charger limit: ${chargerLimitW} W`);
      * }
      * ```
      */

package/dist/types/enyo-charger-appliance.d.ts

@@ -82,7 +82,13 @@ export declare enum EnyoChargerApplianceAvailableFeaturesEnum {
     /** If the Charger supprots a pv surplus mode */
     PvSurplusMode = "PvSurplusMode",
     /** If the charger supports switching between three-phase and one-phase charging */
-    ThreeToOnePhaseSwitch = "ThreeToOnePhaseSwitch"
+    ThreeToOnePhaseSwitch = "ThreeToOnePhaseSwitch",
+    /**
+     * If the charger requires the vehicle to be disconnected before a new charge can be started.
+     * Once the charger is in {@link EnyoChargerApplianceStatusEnum.Finishing}, no new charge can be
+     * started remotely; the customer has to unplug the vehicle and plug it in again.
+     */
+    DisconnectToRestartCharge = "DisconnectToRestartCharge"
 }
 /**
  * Phase configurations a charger can operate in.

package/dist/types/enyo-charger-appliance.js

@@ -66,4 +66,10 @@ export var EnyoChargerApplianceAvailableFeaturesEnum;
     EnyoChargerApplianceAvailableFeaturesEnum["PvSurplusMode"] = "PvSurplusMode";
     /** If the charger supports switching between three-phase and one-phase charging */
     EnyoChargerApplianceAvailableFeaturesEnum["ThreeToOnePhaseSwitch"] = "ThreeToOnePhaseSwitch";
+    /**
+     * If the charger requires the vehicle to be disconnected before a new charge can be started.
+     * Once the charger is in {@link EnyoChargerApplianceStatusEnum.Finishing}, no new charge can be
+     * started remotely; the customer has to unplug the vehicle and plug it in again.
+     */
+    EnyoChargerApplianceAvailableFeaturesEnum["DisconnectToRestartCharge"] = "DisconnectToRestartCharge";
 })(EnyoChargerApplianceAvailableFeaturesEnum || (EnyoChargerApplianceAvailableFeaturesEnum = {}));

package/dist/types/enyo-eebus.d.ts

@@ -80,6 +80,19 @@ export interface EebusDiscoveredDevice {
     ski: string;
     /** Human-readable device name advertised during discovery */
     deviceName?: string;
+    /**
+     * The vendor the peer announced in its SHIP record (the `brand` TXT key),
+     * verbatim and untranslated — e.g. `Vaillant`, `KEBA`, `Viessmann`.
+     *
+     * The peer's own claim, made before anything is paired, which is what makes
+     * it usable as a discovery filter next to {@link deviceType}: see
+     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.vendors}. Spelling and case
+     * are whatever the firmware ships, so compare case-insensitively rather
+     * than with `===`.
+     *
+     * Absent when the peer advertises no `brand`.
+     */
+    brand?: string;
     /** IP address or hostname of the device */
     host: string;
     /** Port number for the SHIP connection */

package/dist/types/enyo-electricity-tariff.d.ts

@@ -180,6 +180,15 @@ export interface EnyoTariffPriceEntry {
     timestampIso: string;
     /** Price per kWh for this interval, in the tariff's currency. */
     pricePerKwh: number;
+    /**
+     * Optional gross grid fee per kWh contained in {@link pricePerKwh}, in the
+     * tariff's currency (not cent).
+     *
+     * Informational only: it breaks down the price, it is **never added** to it.
+     * {@link pricePerKwh} is always the total price. Only meaningful when the
+     * series declares {@link EnyoPriceComponentEnum.GridFee} in its `includes`.
+     */
+    gridFeeGrossPerKwh?: number;
 }
 /**
  * Prices for one direction over a requested range.

package/dist/types/enyo-grid-connection-point.d.ts

@@ -52,4 +52,25 @@ export interface EnyoGridConnectionPoint {
      * `powerLimitW` applies.
      */
     desiredKwLimit?: number;
+    /**
+     * Maximum active power, in watts (W), that the load balancing may allocate
+     * to EV chargers in total at this grid connection point.
+     *
+     * This caps the charging power distributed across all connected wallboxes,
+     * independently of what the grid connection as a whole could deliver: it
+     * lets an installer keep headroom for the rest of the household, or honour
+     * a charger-specific limit agreed with the grid operator (e.g. §14a EnWG
+     * style restrictions).
+     *
+     * Optional. When `undefined`, load balancing assumes the default of
+     * {@link DEFAULT_CHARGER_LIMIT_W} (11 kW).
+     */
+    chargerLimitW?: number;
 }
+/**
+ * Default total charger power limit, in watts (W), applied by load balancing
+ * when {@link EnyoGridConnectionPoint.chargerLimitW} is not configured.
+ *
+ * 11 kW corresponds to the common three-phase 16 A wallbox rating.
+ */
+export declare const DEFAULT_CHARGER_LIMIT_W = 11000;

package/dist/types/enyo-grid-connection-point.js

@@ -1 +1,7 @@
-export {};
+/**
+ * Default total charger power limit, in watts (W), applied by load balancing
+ * when {@link EnyoGridConnectionPoint.chargerLimitW} is not configured.
+ *
+ * 11 kW corresponds to the common three-phase 16 A wallbox rating.
+ */
+export const DEFAULT_CHARGER_LIMIT_W = 11000;

package/dist/types/enyo-onboarding-v2-eebus-device-select.d.ts

@@ -47,6 +47,17 @@ export interface EnyoOnboardingV2EebusPeer {
     deviceName?: string;
     /** Brand or model the peer advertised, if any. */
     deviceModel?: string;
+    /**
+     * The vendor the peer announced during discovery (the SHIP `brand` TXT
+     * key), verbatim and untranslated, if any.
+     *
+     * The same claim {@link EnyoOnboardingV2EebusDeviceSelectBlock.vendors}
+     * filters the picker by, passed on so a handler that serves several
+     * manufacturers can pick the right appliance shape without re-reading
+     * discovery. Case and spelling are the firmware's — compare
+     * case-insensitively. Absent means the peer announced no vendor.
+     */
+    brand?: string;
     /**
      * The device type the peer announced, when it announced one this SDK knows.
      *
@@ -118,7 +129,8 @@ export interface EnyoOnboardingV2EebusDeviceSelectRequest {
     /**
      * `true` when the host paired on the installer's behalf because exactly one
      * peer matched the block's
-     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.deviceTypes} filter and
+     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.deviceTypes} and
+     * {@link EnyoOnboardingV2EebusDeviceSelectBlock.vendors} filters and
      * {@link EnyoOnboardingV2PickerBlockBase.autoSelectSingleMatch} was left on —
      * the screen was never rendered.
      *

package/dist/types/enyo-onboarding-v2.d.ts

@@ -679,6 +679,31 @@ export interface EnyoOnboardingV2EebusDeviceSelectBlock extends EnyoOnboardingV2
      * is a validation error.
      */
     deviceTypes?: EnyoEebusDeviceTypeEnum[];
+    /**
+     * Offer only peers announcing one of these vendors; everything else is left
+     * out of the list and does not count towards
+     * {@link EnyoOnboardingV2PickerBlockBase.autoSelectSingleMatch}.
+     *
+     * The companion of {@link deviceTypes} for the case that filter cannot
+     * separate: a house with two EEBUS heat pumps, or a guide that is written
+     * for one manufacturer's device and would otherwise offer a competitor's as
+     * a candidate for its own pairing flow. Both filters are **conjunctive** —
+     * a peer must satisfy every filter present to be offered.
+     *
+     * Matched against the vendor the peer announced
+     * ({@link EebusDiscoveredDevice.brand}, the SHIP `brand` TXT key),
+     * **case-insensitively and ignoring surrounding whitespace**, since the
+     * spelling is whatever the firmware ships. It is otherwise an exact match,
+     * not a substring one: `KEBA` does not match `KEBA AG`, so list the
+     * spellings a vendor is known to announce rather than hoping for one.
+     *
+     * A peer that announces no vendor is treated the same way an unknown device
+     * type is: it survives an omitted filter and is excluded by any filter
+     * present, so a guide can never pair something it did not ask for. Omit the
+     * property to offer peers of every vendor; an **empty array** filters
+     * everything out and is a validation error.
+     */
+    vendors?: string[];
 }
 /**
  * A fixed URL the installer opens or copies — a vendor portal, a manual, a

package/dist/version.d.ts

@@ -5,7 +5,7 @@
 /**
  * Current version of the enyo Energy App SDK.
  */
-export declare const SDK_VERSION = "1.24.0";
+export declare const SDK_VERSION = "1.25.0";
 /**
  * Gets the current SDK version.
  * @returns The semantic version string of the SDK

package/dist/version.js

@@ -5,7 +5,7 @@
 /**
  * Current version of the enyo Energy App SDK.
  */
-export const SDK_VERSION = '1.24.0';
+export const SDK_VERSION = '1.25.0';
 /**
  * Gets the current SDK version.
  * @returns The semantic version string of the SDK

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@enyo-energy/energy-app-sdk",
-  "version": "1.24.0",
+  "version": "1.25.0",
   "description": "enyo Energy App SDK",
   "type": "module",
   "main": "dist/index.js",