@enyo-energy/energy-app-sdk 0.0.193 → 0.0.194

package/README.md

@@ -2054,6 +2054,16 @@ Drives an EV wallbox / charger. Has the richest command surface of all integrati
   - `publishChargingMeterValues(applianceId, data)` — periodic meter values during a session.
   - `publishMaxChargingPowerChanged(applianceId, maxChargingPowerKw)` — e.g. on thermal derating.
   - `publishChargerStatusChanged(applianceId, data)` — OCPP-style status changes.
+  - `publishEnergyManagementChargingState(applianceId, data)` — the app's own continuously
+    updated state for the energy manager. Facts only: `activePhases` (the phase count in
+    force), `phaseSwitching` (`supported` / `available` right now, `availableFromIso` when
+    it is barred until a known time, `inProgress`), `appliedCurrentLimitA` and the
+    `appliedPowerW` it implies, `lastLimitRequest` (`accepted` \| `clamped` \| `rejected`,
+    with what was requested), and `measuredAtIso` — when the reading was taken, as opposed
+    to when the message was sent. No recommended minimum power, no suggested setpoint,
+    nothing derived from the manager's own plan; static nameplate data stays in the
+    appliance metadata. Republish the **complete** payload on every change and periodically
+    as a heartbeat — an omitted field means "unknown", never "unchanged".
 
 ```typescript
 class MyWallbox extends WallboxIntegrationEnergyApp {

package/dist/cjs/energy-app-package-definition.d.cts

@@ -228,6 +228,18 @@ export interface EnergyAppPackageCompatibilityModel {
      * upgrade graph in {@link EnergyAppPackageDefinition.firmware} instead.
      */
     minimumFirmwareVersion?: string;
+    /**
+     * Optional device category of this concrete model (e.g. `Inverter`,
+     * `BatteryStorage`).
+     *
+     * Packages can support models of different kinds — a hybrid inverter plus a
+     * matching battery, for example — while
+     * {@link EnergyAppPackageDefinition.categories} only describes the package
+     * as a whole. Declaring the category per model lets the enyo Store and
+     * onboarding flows group and filter individual models correctly. Omit when
+     * the package-level categories are precise enough.
+     */
+    category?: EnergyAppPackageCategory;
     /** Optional internal note explaining model-specific caveats or limitations */
     internalComment?: string;
     /**

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

@@ -158,6 +158,37 @@ exports.onboardingV2Block = {
         label,
         outcomes,
     }),
+    /**
+     * An EEBUS-pair action block: the installer picks one of the discovered
+     * EEBUS peers and the host trusts its SKI.
+     *
+     * A convenience wrapper over {@link onboardingV2Block.action} that pins the
+     * action kind. The picker is drawn from what mDNS discovery found, so the
+     * guide must have scanned — keep
+     * {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its default or place
+     * a {@link EnyoOnboardingV2ActionKind.NetworkScan} block ahead of this one.
+     *
+     * Most EEBUS devices only announce themselves once pairing is enabled in
+     * their own menu or portal, and many ask for a confirmation there while the
+     * handshake runs, so put that instruction in a text/hint block on the
+     * preceding step — the app cannot do it for the installer.
+     *
+     * Outcome `value`s must be {@link EnyoOnboardingV2EebusPairOutcome} members;
+     * route `not-found` to troubleshooting and `failure` to a step describing
+     * the confirmation on the device. A retry must lead into a *second* pairing
+     * step: a back-edge onto the same step reads as a loop and ends the run.
+     *
+     * @param id - Stable block id, unique within the guide.
+     * @param label - Translated trigger button text (de/en).
+     * @param outcomes - The `paired` / `not-found` / `failure` results; each is a routing handle.
+     */
+    eebusPair: (id, label, outcomes) => ({
+        id,
+        type: enyo_onboarding_v2_js_1.EnyoOnboardingV2BlockType.Action,
+        action: enyo_onboarding_v2_js_1.EnyoOnboardingV2ActionKind.EebusPair,
+        label,
+        outcomes,
+    }),
     /**
      * An auth block: the installer signs into the energy app's own account
      * system (OAuth / vendor portal).

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

@@ -117,6 +117,31 @@ export declare const onboardingV2Block: {
      * @param outcomes - The `connected` / `timeout` results; each is a routing handle.
      */
     ocppConnect: (id: string, label: EnyoOnboardingTranslatedContent[], outcomes: EnyoOnboardingV2ActionOutcome[]) => EnyoOnboardingV2Block;
+    /**
+     * An EEBUS-pair action block: the installer picks one of the discovered
+     * EEBUS peers and the host trusts its SKI.
+     *
+     * A convenience wrapper over {@link onboardingV2Block.action} that pins the
+     * action kind. The picker is drawn from what mDNS discovery found, so the
+     * guide must have scanned — keep
+     * {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its default or place
+     * a {@link EnyoOnboardingV2ActionKind.NetworkScan} block ahead of this one.
+     *
+     * Most EEBUS devices only announce themselves once pairing is enabled in
+     * their own menu or portal, and many ask for a confirmation there while the
+     * handshake runs, so put that instruction in a text/hint block on the
+     * preceding step — the app cannot do it for the installer.
+     *
+     * Outcome `value`s must be {@link EnyoOnboardingV2EebusPairOutcome} members;
+     * route `not-found` to troubleshooting and `failure` to a step describing
+     * the confirmation on the device. A retry must lead into a *second* pairing
+     * step: a back-edge onto the same step reads as a loop and ends the run.
+     *
+     * @param id - Stable block id, unique within the guide.
+     * @param label - Translated trigger button text (de/en).
+     * @param outcomes - The `paired` / `not-found` / `failure` results; each is a routing handle.
+     */
+    eebusPair: (id: string, label: EnyoOnboardingTranslatedContent[], outcomes: EnyoOnboardingV2ActionOutcome[]) => EnyoOnboardingV2Block;
     /**
      * An auth block: the installer signs into the energy app's own account
      * system (OAuth / vendor portal).

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

@@ -178,6 +178,9 @@ function validateActionBlocks(step, at, errors, warnings) {
             if (block.action === enyo_onboarding_v2_js_1.EnyoOnboardingV2ActionKind.OcppConnect) {
                 validateOcppConnectOutcomes(block, at, errors);
             }
+            if (block.action === enyo_onboarding_v2_js_1.EnyoOnboardingV2ActionKind.EebusPair) {
+                validateEebusPairOutcomes(block, at, errors, warnings);
+            }
             continue;
         }
         const values = new Set();
@@ -233,8 +236,17 @@ function validateLinkBlocks(step, at, errors, warnings) {
 }
 /** Every valid {@link EnyoOnboardingV2InputValueType} value. */
 const INPUT_VALUE_TYPES = new Set(Object.values(enyo_onboarding_v2_js_1.EnyoOnboardingV2InputValueType));
-/** Outcome values the host treats as "the check succeeded". */
-const POSITIVE_INPUT_OUTCOMES = new Set(['reachable', 'success', 'found']);
+/**
+ * Outcome values the host treats as "the check succeeded" — mirrors the
+ * runtime's own positive-outcome set, `paired` included, so an eebus-pair
+ * result is not read as a failure.
+ */
+const POSITIVE_INPUT_OUTCOMES = new Set([
+    'reachable',
+    'success',
+    'found',
+    enyo_onboarding_v2_js_1.EnyoOnboardingV2EebusPairOutcome.Paired,
+]);
 /**
  * The {@link EnyoDeviceTestOutcomeEnum} verdicts that collapse onto a positive
  * input outcome; every other verdict collapses onto a negative one.
@@ -341,6 +353,42 @@ function validateOcppConnectOutcomes(block, at, errors) {
         }
     }
 }
+/** Every {@link EnyoOnboardingV2EebusPairOutcome} value. */
+const EEBUS_PAIR_OUTCOMES = new Set(Object.values(enyo_onboarding_v2_js_1.EnyoOnboardingV2EebusPairOutcome));
+/**
+ * Validates the outcomes of an {@link EnyoOnboardingV2ActionKind.EebusPair}
+ * block.
+ *
+ * The block reports one of three things — a peer was picked and the SHIP
+ * handshake came up, discovery found nothing, or the handshake failed — so its
+ * outcome `value`s are closed over {@link EnyoOnboardingV2EebusPairOutcome}.
+ * Anything else is an outcome that can never fire.
+ *
+ * The missing `paired` branch is a warning rather than an error: it strands
+ * every successful pairing, but an author staging a guide step by step may
+ * legitimately not have wired it yet.
+ *
+ * @param block - The eebus-pair action block being checked.
+ * @param at - Human-readable location prefix for messages.
+ * @param errors - Collector for blocking problems.
+ * @param warnings - Collector for advisory problems.
+ */
+function validateEebusPairOutcomes(block, at, errors, warnings) {
+    const values = new Set();
+    for (const outcome of block.outcomes ?? []) {
+        if (!EEBUS_PAIR_OUTCOMES.has(outcome.value)) {
+            errors.push(`${at}: eebus-pair block "${block.id}" has outcome value "${outcome.value}", which is not an EnyoOnboardingV2EebusPairOutcome member.`);
+        }
+        else if (values.has(outcome.value)) {
+            errors.push(`${at}: eebus-pair block "${block.id}" wires outcome value "${outcome.value}" more than once.`);
+        }
+        values.add(outcome.value);
+    }
+    if (!values.has(enyo_onboarding_v2_js_1.EnyoOnboardingV2EebusPairOutcome.Paired)) {
+        warnings.push(`${at}: eebus-pair block "${block.id}" has no "${enyo_onboarding_v2_js_1.EnyoOnboardingV2EebusPairOutcome.Paired}" outcome — ` +
+            'a successful pairing would have nowhere to go.');
+    }
+}
 /**
  * Validates the auth blocks of a step.
  *
@@ -410,6 +458,13 @@ function validateNetworkScanFlag(guide, warnings) {
             'nothing was scanned, so it has nothing to test. Use deviceSelection "current", or run a ' +
             'network-scan action inside the guide.');
     }
+    const pairsEebus = blocks.some((b) => b.type === enyo_onboarding_v2_js_1.EnyoOnboardingV2BlockType.Action &&
+        b.action === enyo_onboarding_v2_js_1.EnyoOnboardingV2ActionKind.EebusPair);
+    if (pairsEebus) {
+        warnings.push('requiresNetworkScan is false, but an eebus-pair block asks the installer to pick a ' +
+            'discovered EEBUS peer — nothing was scanned, so the picker would open on an empty ' +
+            'list. Run a network-scan action inside the guide ahead of it.');
+    }
 }
 /**
  * The set of routing-handle keys a step must wire exactly once: one per

package/dist/cjs/integrations/wallbox-integration-energy-app.cjs

@@ -117,6 +117,40 @@ class WallboxIntegrationEnergyApp extends integration_energy_app_js_1.Integratio
         };
         this.useDataBus().sendMessage([msg]);
     }
+    /**
+     * Publishes an `EnergyManagementChargingStateV1` message: the app's own
+     * state — the phase count in force, whether a phase switch is possible
+     * right now, the limit actually applied and the verdict on the last
+     * request — reported to the energy manager.
+     *
+     * This is a continuously updated state, not an event. Call it whenever
+     * anything in the payload changes (a phase switch starts or finishes, a
+     * cool-down expires, a new limit is applied) and periodically as a
+     * heartbeat, always passing the **complete** picture: an omitted field
+     * means "unknown", never "unchanged".
+     *
+     * Report facts, never advice: the phase count, the applied limit and the
+     * power it implies, the request verdict, the measurement timestamp — no
+     * recommended minimum power, no suggested setpoint, nothing derived from
+     * the energy manager's own plan.
+     *
+     * @param applianceId - The charger appliance the state describes.
+     * @param data - The full charging state; see
+     *   {@link EnyoDataBusEnergyManagementChargingStateV1}.
+     */
+    publishEnergyManagementChargingState(applianceId, data) {
+        const msg = {
+            id: this.generateMessageId(),
+            type: 'message',
+            message: enyo_data_bus_value_js_1.EnyoDataBusMessageEnum.EnergyManagementChargingStateV1,
+            source: this.source,
+            applianceId,
+            timestampIso: new Date().toISOString(),
+            resolution: 'dynamic',
+            data
+        };
+        this.useDataBus().sendMessage([msg]);
+    }
     /**
      * Publishes a `ChargerStatusChangedV1` message reporting the current OCPP
      * status (Available, Preparing, Charging, …).

package/dist/cjs/integrations/wallbox-integration-energy-app.d.cts

@@ -1,7 +1,7 @@
 import { IntegrationEnergyApp } from "./integration-energy-app.cjs";
 import { IntegrationCommandResponse, IntegrationEnergyAppOptions } from "./integration-types.cjs";
 import { EnyoApplianceTypeEnum } from "../types/enyo-appliance.cjs";
-import { EnyoDataBusChangeChargingPowerV1, EnyoDataBusChargerStatusChangedV1, EnyoDataBusChargingMeterValuesV1, EnyoDataBusChargingStartedV1, EnyoDataBusChargingStoppedV1, EnyoDataBusClearChargingProfilesV1, EnyoDataBusGridOperatorPowerLimitationV1, EnyoDataBusMessage, EnyoDataBusPauseChargingV1, EnyoDataBusRebootChargerV1, EnyoDataBusRequestChargerLogsV1, EnyoDataBusResetChargerV1, EnyoDataBusResumeChargingV1, EnyoDataBusSetChargerAvailablePowerV2, EnyoDataBusSetChargingScheduleV1, EnyoDataBusStartChargeV1, EnyoDataBusStopChargeV1 } from "../types/enyo-data-bus-value.cjs";
+import { EnyoDataBusChangeChargingPowerV1, EnyoDataBusChargerStatusChangedV1, EnyoDataBusChargingMeterValuesV1, EnyoDataBusChargingStartedV1, EnyoDataBusChargingStoppedV1, EnyoDataBusClearChargingProfilesV1, EnyoDataBusEnergyManagementChargingStateV1, EnyoDataBusGridOperatorPowerLimitationV1, EnyoDataBusMessage, EnyoDataBusPauseChargingV1, EnyoDataBusRebootChargerV1, EnyoDataBusRequestChargerLogsV1, EnyoDataBusResetChargerV1, EnyoDataBusResumeChargingV1, EnyoDataBusSetChargerAvailablePowerV2, EnyoDataBusSetChargingScheduleV1, EnyoDataBusStartChargeV1, EnyoDataBusStopChargeV1 } from "../types/enyo-data-bus-value.cjs";
 /**
  * Abstract base class for wallbox / charger integrations.
  *
@@ -122,6 +122,28 @@ export declare abstract class WallboxIntegrationEnergyApp extends IntegrationEne
      * charger's max charging power has changed (e.g. due to thermal derating).
      */
     publishMaxChargingPowerChanged(applianceId: string, maxChargingPowerKw: number): void;
+    /**
+     * Publishes an `EnergyManagementChargingStateV1` message: the app's own
+     * state — the phase count in force, whether a phase switch is possible
+     * right now, the limit actually applied and the verdict on the last
+     * request — reported to the energy manager.
+     *
+     * This is a continuously updated state, not an event. Call it whenever
+     * anything in the payload changes (a phase switch starts or finishes, a
+     * cool-down expires, a new limit is applied) and periodically as a
+     * heartbeat, always passing the **complete** picture: an omitted field
+     * means "unknown", never "unchanged".
+     *
+     * Report facts, never advice: the phase count, the applied limit and the
+     * power it implies, the request verdict, the measurement timestamp — no
+     * recommended minimum power, no suggested setpoint, nothing derived from
+     * the energy manager's own plan.
+     *
+     * @param applianceId - The charger appliance the state describes.
+     * @param data - The full charging state; see
+     *   {@link EnyoDataBusEnergyManagementChargingStateV1}.
+     */
+    publishEnergyManagementChargingState(applianceId: string, data: EnyoDataBusEnergyManagementChargingStateV1['data']): void;
     /**
      * Publishes a `ChargerStatusChangedV1` message reporting the current OCPP
      * status (Available, Preparing, Charging, …).

package/dist/cjs/types/enyo-data-bus-value.cjs

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.EnyoPowerSourceEnum = exports.EnyoHeatpumpControlPurposeEnum = exports.EnyoChargingProfileTypeEnum = exports.EnyoCommandAcknowledgeAnswerEnum = exports.EnyoStorageControlDirectionEnum = exports.EnyoStorageControlModeEnum = exports.EnyoStorageScheduleDirectionEnum = exports.EnyoStorageScheduleModeEnum = exports.EnyoDataBusMessageEnum = exports.EnyoChargeInitiatorEnum = exports.EnyoChargeModeEnum = exports.EnyoChargingStopReason = exports.EnyoChargingMeterValueContext = exports.EnyoStringStateEnum = exports.EnyoHeatingRodStateEnum = exports.EnyoInverterStateEnum = exports.EnyoBatteryStateEnum = exports.EnyoGridOperatorLimitTypeEnum = exports.EnyoDataBusCommandReasonCategoryEnum = exports.EnyoDataBusCommandReasonTypeEnum = void 0;
+exports.EnyoPowerSourceEnum = exports.EnyoHeatpumpControlPurposeEnum = exports.EnyoChargingProfileTypeEnum = exports.EnyoCommandAcknowledgeAnswerEnum = exports.EnyoStorageControlDirectionEnum = exports.EnyoStorageControlModeEnum = exports.EnyoStorageScheduleDirectionEnum = exports.EnyoStorageScheduleModeEnum = exports.EnyoChargingLimitRequestResultEnum = exports.EnyoDataBusMessageEnum = exports.EnyoChargeInitiatorEnum = exports.EnyoChargeModeEnum = exports.EnyoChargingStopReason = exports.EnyoChargingMeterValueContext = exports.EnyoStringStateEnum = exports.EnyoHeatingRodStateEnum = exports.EnyoInverterStateEnum = exports.EnyoBatteryStateEnum = exports.EnyoGridOperatorLimitTypeEnum = exports.EnyoDataBusCommandReasonCategoryEnum = exports.EnyoDataBusCommandReasonTypeEnum = void 0;
 /**
  * Enum representing the reason type for why a data bus command was issued.
  * Used to attach context to commands for logging, debugging, and UI display.
@@ -222,6 +222,8 @@ var EnyoDataBusMessageEnum;
     EnyoDataBusMessageEnum["EnergyTariffUpdateV1"] = "EnergyTariffUpdateV1";
     EnyoDataBusMessageEnum["ChargeFinishedV1"] = "ChargeFinishedV1";
     EnyoDataBusMessageEnum["ChargerStatusChangedV1"] = "ChargerStatusChangedV1";
+    /** Recurring state of the charging energy app (phases in force, phase-switch availability, applied limit, last request's verdict) reported to the energy manager. */
+    EnyoDataBusMessageEnum["EnergyManagementChargingStateV1"] = "EnergyManagementChargingStateV1";
     EnyoDataBusMessageEnum["RequestPreviewChargingScheduleV1"] = "RequestPreviewChargingScheduleV1";
     EnyoDataBusMessageEnum["PreviewChargingScheduleResponseV1"] = "PreviewChargingScheduleResponseV1";
     EnyoDataBusMessageEnum["PvForecastV1"] = "PvForecastV1";
@@ -280,6 +282,24 @@ var EnyoDataBusMessageEnum;
     EnyoDataBusMessageEnum["SetStorageControlV2"] = "SetStorageControlV2";
     EnyoDataBusMessageEnum["EnergyAppStartedV1"] = "EnergyAppStartedV1";
 })(EnyoDataBusMessageEnum || (exports.EnyoDataBusMessageEnum = EnyoDataBusMessageEnum = {}));
+/**
+ * What became of the last power/current limit the energy manager asked this
+ * charging app for.
+ *
+ * A request is not the same as a limit in force: chargers round to their
+ * ampere step, refuse values below their minimum current, and cap at their
+ * nameplate. Reporting the verdict closes the loop — without it the energy
+ * manager cannot tell a limit it set from a limit the charger quietly changed.
+ */
+var EnyoChargingLimitRequestResultEnum;
+(function (EnyoChargingLimitRequestResultEnum) {
+    /** Applied as requested. */
+    EnyoChargingLimitRequestResultEnum["Accepted"] = "accepted";
+    /** Applied, but at a different value than requested (rounded, floored, capped). */
+    EnyoChargingLimitRequestResultEnum["Clamped"] = "clamped";
+    /** Not applied at all; the previous limit stayed in force. */
+    EnyoChargingLimitRequestResultEnum["Rejected"] = "rejected";
+})(EnyoChargingLimitRequestResultEnum || (exports.EnyoChargingLimitRequestResultEnum = EnyoChargingLimitRequestResultEnum = {}));
 /**
  * Storage control mode carried by {@link EnyoDataBusSetStorageScheduleV1}.
  *

package/dist/cjs/types/enyo-data-bus-value.d.cts

@@ -2,7 +2,7 @@ import { EnyoApplianceErrorCode, EnyoApplianceStateEnum, EnyoApplianceStatusEnum
 import type { EnyoAutomationTriggerData } from "./enyo-automation.cjs";
 import { EnyoSourceEnum } from "./enyo-source.enum.cjs";
 import { EnyoOcppRelativeSchedule } from "./enyo-ocpp.cjs";
-import { EnyoChargerApplianceStatusEnum, EnyoChargerApplianceSuspendedReasonEnum } from "./enyo-charger-appliance.cjs";
+import { EnyoChargerAppliancePhase, EnyoChargerApplianceStatusEnum, EnyoChargerApplianceSuspendedReasonEnum } from "./enyo-charger-appliance.cjs";
 import { PreviewChargingSchedule, PreviewChargingScheduleCostComparison, PreviewChargingScheduleUnavailableReasonEnum } from "./enyo-energy-manager.cjs";
 import { EnyoEnergyPrices } from "./enyo-energy-prices.cjs";
 import { EnyoCurrencyEnum } from "./enyo-currency.cjs";
@@ -286,6 +286,8 @@ export declare enum EnyoDataBusMessageEnum {
     EnergyTariffUpdateV1 = "EnergyTariffUpdateV1",
     ChargeFinishedV1 = "ChargeFinishedV1",
     ChargerStatusChangedV1 = "ChargerStatusChangedV1",
+    /** Recurring state of the charging energy app (phases in force, phase-switch availability, applied limit, last request's verdict) reported to the energy manager. */
+    EnergyManagementChargingStateV1 = "EnergyManagementChargingStateV1",
     RequestPreviewChargingScheduleV1 = "RequestPreviewChargingScheduleV1",
     PreviewChargingScheduleResponseV1 = "PreviewChargingScheduleResponseV1",
     PvForecastV1 = "PvForecastV1",
@@ -997,6 +999,158 @@ export interface EnyoDataBusChargerStatusChangedV1 extends EnyoDataBusMessage {
         suspendedReason?: EnyoChargerApplianceSuspendedReasonEnum;
     };
 }
+/**
+ * What became of the last power/current limit the energy manager asked this
+ * charging app for.
+ *
+ * A request is not the same as a limit in force: chargers round to their
+ * ampere step, refuse values below their minimum current, and cap at their
+ * nameplate. Reporting the verdict closes the loop — without it the energy
+ * manager cannot tell a limit it set from a limit the charger quietly changed.
+ */
+export declare enum EnyoChargingLimitRequestResultEnum {
+    /** Applied as requested. */
+    Accepted = "accepted",
+    /** Applied, but at a different value than requested (rounded, floored, capped). */
+    Clamped = "clamped",
+    /** Not applied at all; the previous limit stayed in force. */
+    Rejected = "rejected"
+}
+/**
+ * The verdict on the last limit request, as a fact about what happened.
+ *
+ * Carries what was asked for and what the app did with it. The value actually
+ * in force afterwards is not repeated here — it is
+ * {@link EnyoDataBusEnergyManagementChargingStateV1.data.appliedCurrentLimitA}
+ * in the same message.
+ */
+export interface EnyoChargingLimitRequestOutcome {
+    /**
+     * `id` of the {@link EnyoDataBusSetChargerAvailablePowerV2} (or other limit
+     * command) this verdict belongs to, when the app tracked it. Lets the energy
+     * manager match the verdict to its own request instead of guessing by time.
+     */
+    requestMessageId?: string;
+    /** What the app did with the request. */
+    result: EnyoChargingLimitRequestResultEnum;
+    /** The active power that was requested, in Watts, as received. */
+    requestedPowerW?: number;
+    /** The current per phase that was requested, in Amperes, when the request was expressed that way. */
+    requestedCurrentA?: number;
+    /** ISO 8601 timestamp at which the app handled the request. */
+    handledAtIso: string;
+    /**
+     * Short machine-readable cause when the request was clamped or rejected,
+     * e.g. `below-minimum-current`, `above-nameplate`, `charger-offline`,
+     * `ampere-step-rounding`. Never shown to end users verbatim.
+     */
+    reason?: string;
+}
+/**
+ * Whether this charger can change its phase count right now, and if not, until
+ * when.
+ *
+ * Two different facts: {@link supported} is about the hardware and the wiring
+ * and does not change during operation; {@link available} is about this moment —
+ * a contactor switch interrupts the session, so apps bar the next switch for a
+ * cool-down after the last one, and refuse it outright while the charger is in
+ * certain states.
+ */
+export interface EnyoChargingPhaseSwitchingState {
+    /** Whether the charger can switch between one- and three-phase charging at all. */
+    supported: boolean;
+    /** Whether a phase switch can be performed right now. */
+    available: boolean;
+    /**
+     * ISO 8601 timestamp from which switching becomes available again. Set when
+     * {@link available} is `false` **and** the app knows the deadline — a
+     * cool-down expiry, typically. Omitted when the block has no known end (the
+     * charger is offline, switching is unsupported).
+     */
+    availableFromIso?: string;
+    /** Whether a phase switch is in progress at this moment. */
+    inProgress: boolean;
+    /**
+     * The phase count a switch in progress is heading for. Only present while
+     * {@link inProgress} is `true`.
+     */
+    targetPhases?: EnyoChargerAppliancePhase;
+    /** ISO 8601 timestamp of the last completed phase switch, when the app knows it. */
+    lastSwitchedAtIso?: string;
+    /**
+     * Short machine-readable cause when {@link available} is `false`, e.g.
+     * `cool-down`, `vehicle-charging`, `charger-error`, `user-pinned-phases`.
+     * Never shown to end users verbatim.
+     */
+    unavailableReason?: string;
+}
+/**
+ * The charging energy app's own state, reported to the energy manager.
+ *
+ * One **continuously updated state**, not an event: the app republishes the
+ * complete picture whenever something in it changes (a phase switch starts or
+ * finishes, a cool-down expires, a limit is applied) and periodically as a
+ * heartbeat, so a manager that just started up or missed a message converges on
+ * the current truth from the next one. Every message carries the full payload —
+ * a field is omitted to mean "unknown", never "unchanged".
+ *
+ * The payload is **facts about the charger, never advice about what to do with
+ * it**. It reports the phase count in force, whether a phase switch is possible
+ * right now and until when it is not, the limit actually applied and the power
+ * that limit implies, the verdict on the last request, and when all of this was
+ * observed. It deliberately carries no recommended minimum power, no suggested
+ * setpoint and nothing derived from the energy manager's own plan: the manager
+ * owns the planning, and a second opinion travelling with the measurements only
+ * competes with it. Static nameplate data (supported phase configurations,
+ * ampere step, nameplate power) stays where it already lives, in
+ * {@link EnyoChargerApplianceMetadata}.
+ *
+ * Publish it with `resolution: 'dynamic'`.
+ */
+export interface EnyoDataBusEnergyManagementChargingStateV1 extends EnyoDataBusMessage {
+    type: 'message';
+    message: EnyoDataBusMessageEnum.EnergyManagementChargingStateV1;
+    /** ID of the charger appliance this state describes */
+    applianceId: string;
+    data: {
+        /**
+         * ISO 8601 timestamp at which this state was observed on the charger.
+         * Distinct from {@link EnyoDataBusMessage.timestampIso}, which is when
+         * the message was sent: a value polled from a charger every 30 s is
+         * already that old when it is published, and the energy manager must be
+         * able to tell a fresh reading from a stale one.
+         */
+        measuredAtIso: string;
+        /**
+         * The phase configuration in force right now — `1` or `3` while the
+         * charger is drawing, `0` when it is not drawing at all.
+         */
+        activePhases: number;
+        /** Whether a phase switch is possible right now, and if not, until when. */
+        phaseSwitching: EnyoChargingPhaseSwitchingState;
+        /**
+         * The current limit per phase actually in force on the charger, in
+         * Amperes — the value the charger is running with, not the one that was
+         * asked for. Omitted when the app cannot read it back.
+         */
+        appliedCurrentLimitA?: number;
+        /**
+         * The active power {@link appliedCurrentLimitA} implies at the phase
+         * count in force, in Watts. Reported alongside the current because the
+         * conversion depends on {@link activePhases} and the mains voltage the
+         * app measured — facts the energy manager would otherwise have to
+         * assume.
+         */
+        appliedPowerW?: number;
+        /**
+         * What became of the last limit request the app received. Omitted when
+         * it has not handled one in this session.
+         */
+        lastLimitRequest?: EnyoChargingLimitRequestOutcome;
+        /** Connector ID on the charge point (optional, for multi-connector chargers) */
+        connectorId?: number;
+    };
+}
 /**
  * Request message to get a preview of the optimized charging schedule.
  * Sent when user wants to see the charging plan before starting.

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

@@ -22,7 +22,7 @@
  * before publishing.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.EnyoOnboardingV2TargetType = exports.EnyoOnboardingV2TransitionSourceKind = exports.EnyoOnboardingV2BlockType = exports.EnyoOnboardingV2ChoiceLayout = exports.EnyoOnboardingV2IconKey = exports.EnyoOnboardingV2DeviceSelection = exports.EnyoOnboardingV2InputValueType = exports.EnyoOnboardingV2OcppConnectOutcome = exports.EnyoOnboardingV2ActionKind = exports.EnyoOnboardingV2DynamicKind = exports.EnyoOnboardingV2HintVariant = exports.EnyoOnboardingV2PauseReason = exports.EnyoOnboardingV2StartVariant = void 0;
+exports.EnyoOnboardingV2TargetType = exports.EnyoOnboardingV2TransitionSourceKind = exports.EnyoOnboardingV2BlockType = exports.EnyoOnboardingV2ChoiceLayout = exports.EnyoOnboardingV2IconKey = exports.EnyoOnboardingV2DeviceSelection = exports.EnyoOnboardingV2InputValueType = exports.EnyoOnboardingV2OcppConnectOutcome = exports.EnyoOnboardingV2EebusPairOutcome = exports.EnyoOnboardingV2ActionKind = exports.EnyoOnboardingV2DynamicKind = exports.EnyoOnboardingV2HintVariant = exports.EnyoOnboardingV2PauseReason = exports.EnyoOnboardingV2StartVariant = void 0;
 // ---------------------------------------------------------------------------
 // Enumerable string enums
 // ---------------------------------------------------------------------------
@@ -118,7 +118,57 @@ var EnyoOnboardingV2ActionKind;
      * is the common case, not an edge case.
      */
     EnyoOnboardingV2ActionKind["OcppConnect"] = "ocpp-connect";
+    /**
+     * Let the installer pick one of the EEBUS peers discovered on the local
+     * network and trust its SKI.
+     *
+     * EEBUS is the third way a device reaches us: it is neither typed in as an
+     * IP address ({@link EnyoOnboardingV2InputValueType.IpAddress}) nor dialling
+     * out to our CSMS ({@link OcppConnect}). Heat pumps and wallboxes announce
+     * themselves over mDNS/SHIP and are addressed by their **SKI**, so pairing
+     * means *choosing one of the announced peers* — a decision only the
+     * installer standing in front of the device can make, since two identical
+     * heat pumps in one house differ only by manufacturer, model and the last
+     * bytes of their SKI.
+     *
+     * The host app renders the picker from the peers the hub discovered; the
+     * guide contributes the trigger label and the branches. Because the list
+     * comes from discovery, the guide must have scanned: either it keeps
+     * {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its default, or it
+     * carries a {@link NetworkScan} block ahead of the pairing block —
+     * otherwise the picker opens on an empty list.
+     *
+     * Outcome `value`s MUST be {@link EnyoOnboardingV2EebusPairOutcome}
+     * members. The SKI the installer picked is recorded as the block's input
+     * value, so a finished run says *which* peer was paired, and later steps —
+     * a {@link DeviceTest}, for instance — can read it back under the block's
+     * id.
+     */
+    EnyoOnboardingV2ActionKind["EebusPair"] = "eebus-pair";
 })(EnyoOnboardingV2ActionKind || (exports.EnyoOnboardingV2ActionKind = EnyoOnboardingV2ActionKind = {}));
+/**
+ * The possible results of an {@link EnyoOnboardingV2ActionKind.EebusPair}
+ * block.
+ *
+ * Three, not two: the two ways pairing fails need different guidance. Nothing
+ * was discovered at all is a different conversation from "you picked the right
+ * device but the handshake never came up".
+ */
+var EnyoOnboardingV2EebusPairOutcome;
+(function (EnyoOnboardingV2EebusPairOutcome) {
+    /** The installer picked a peer and the SHIP connection came up. */
+    EnyoOnboardingV2EebusPairOutcome["Paired"] = "paired";
+    /**
+     * Discovery turned up no EEBUS peer — the device is off, on another subnet,
+     * or EEBUS is not enabled in its menu.
+     */
+    EnyoOnboardingV2EebusPairOutcome["NotFound"] = "not-found";
+    /**
+     * A peer was picked but the SHIP handshake did not complete — the pairing
+     * was not confirmed on the device, or a PIN was rejected.
+     */
+    EnyoOnboardingV2EebusPairOutcome["Failure"] = "failure";
+})(EnyoOnboardingV2EebusPairOutcome || (exports.EnyoOnboardingV2EebusPairOutcome = EnyoOnboardingV2EebusPairOutcome = {}));
 /**
  * The possible results of an {@link EnyoOnboardingV2ActionKind.OcppConnect}
  * block. Deliberately binary: either the charger reached our CSMS or it did not.

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

@@ -107,7 +107,56 @@ export declare enum EnyoOnboardingV2ActionKind {
      * members, and both of them must be wired — a charger that never calls home
      * is the common case, not an edge case.
      */
-    OcppConnect = "ocpp-connect"
+    OcppConnect = "ocpp-connect",
+    /**
+     * Let the installer pick one of the EEBUS peers discovered on the local
+     * network and trust its SKI.
+     *
+     * EEBUS is the third way a device reaches us: it is neither typed in as an
+     * IP address ({@link EnyoOnboardingV2InputValueType.IpAddress}) nor dialling
+     * out to our CSMS ({@link OcppConnect}). Heat pumps and wallboxes announce
+     * themselves over mDNS/SHIP and are addressed by their **SKI**, so pairing
+     * means *choosing one of the announced peers* — a decision only the
+     * installer standing in front of the device can make, since two identical
+     * heat pumps in one house differ only by manufacturer, model and the last
+     * bytes of their SKI.
+     *
+     * The host app renders the picker from the peers the hub discovered; the
+     * guide contributes the trigger label and the branches. Because the list
+     * comes from discovery, the guide must have scanned: either it keeps
+     * {@link EnyoOnboardingV2Guide.requiresNetworkScan} at its default, or it
+     * carries a {@link NetworkScan} block ahead of the pairing block —
+     * otherwise the picker opens on an empty list.
+     *
+     * Outcome `value`s MUST be {@link EnyoOnboardingV2EebusPairOutcome}
+     * members. The SKI the installer picked is recorded as the block's input
+     * value, so a finished run says *which* peer was paired, and later steps —
+     * a {@link DeviceTest}, for instance — can read it back under the block's
+     * id.
+     */
+    EebusPair = "eebus-pair"
+}
+/**
+ * The possible results of an {@link EnyoOnboardingV2ActionKind.EebusPair}
+ * block.
+ *
+ * Three, not two: the two ways pairing fails need different guidance. Nothing
+ * was discovered at all is a different conversation from "you picked the right
+ * device but the handshake never came up".
+ */
+export declare enum EnyoOnboardingV2EebusPairOutcome {
+    /** The installer picked a peer and the SHIP connection came up. */
+    Paired = "paired",
+    /**
+     * Discovery turned up no EEBUS peer — the device is off, on another subnet,
+     * or EEBUS is not enabled in its menu.
+     */
+    NotFound = "not-found",
+    /**
+     * A peer was picked but the SHIP handshake did not complete — the pairing
+     * was not confirmed on the device, or a PIN was rejected.
+     */
+    Failure = "failure"
 }
 /**
  * The possible results of an {@link EnyoOnboardingV2ActionKind.OcppConnect}
@@ -565,7 +614,9 @@ export interface EnyoOnboardingV2Guide {
      * A guide that opts out cannot rely on scan results, so
      * {@link EnyoOnboardingV2DeviceSelection.Detected} has nothing to select from
      * unless the guide runs its own
-     * {@link EnyoOnboardingV2ActionKind.NetworkScan} block first.
+     * {@link EnyoOnboardingV2ActionKind.NetworkScan} block first, and an
+     * {@link EnyoOnboardingV2ActionKind.EebusPair} block would offer the
+     * installer an empty list of peers.
      */
     requiresNetworkScan?: boolean;
     /** Optional translated summary shown in the library (de/en). */

package/dist/cjs/version.cjs

@@ -9,7 +9,7 @@ exports.getSdkVersion = getSdkVersion;
 /**
  * Current version of the enyo Energy App SDK.
  */
-exports.SDK_VERSION = '0.0.193';
+exports.SDK_VERSION = '0.0.194';
 /**
  * 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 = "0.0.193";
+export declare const SDK_VERSION = "0.0.194";
 /**
  * Gets the current SDK version.
  * @returns The semantic version string of the SDK