@enyo-energy/energy-app-sdk 0.0.140 → 0.0.141

package/dist/cjs/packages/eebus/eebus-cevc-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusCevcAck, EebusCevcChargingPlan, EebusOhpcfIncentiveTable } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.cevc}.
  */
@@ -33,7 +34,7 @@ export interface CevcClientOptions {
  * until `ElectricalConnectionClient` and `TimeSeriesClient` both land
  * in `@enyo-energy/eebus`.
  */
-export interface EebusCevcClient {
+export interface EebusCevcClient extends EebusUseCaseClient {
     /**
      * Send a time-series charging plan to the EV. The EV ack carries
      * either acceptance or a reason for rejection (e.g. plan exceeds

package/dist/cjs/packages/eebus/eebus-evcc-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusEvCommunicationStandardEnum, EebusEvConnectionState, EebusEvIdentification } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evcc}.
  *
@@ -34,7 +35,7 @@ export interface EvccClientOptions {
  * `@enyo-energy/eebus`. The SDK interface is shipped now so consumers
  * can compile against the final shape.
  */
-export interface EebusEvccClient {
+export interface EebusEvccClient extends EebusUseCaseClient {
     /**
      * Read the EV's identification (EVCCID and identification type).
      * Returns `undefined` when the EV does not publish an

package/dist/cjs/packages/eebus/eebus-evcem-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusEvcemReading } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evcem}.
  */
@@ -26,7 +27,7 @@ export interface EvcemClientOptions {
  * {@link EebusFeatureUnavailableError} from the `connect-core` runtime
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  */
-export interface EebusEvcemClient {
+export interface EebusEvcemClient extends EebusUseCaseClient {
     /**
      * Read the most recent telemetry sample from the EV charging session.
      *

package/dist/cjs/packages/eebus/eebus-evsecc-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusEvseManufacturerData, EebusEvseOperatingState } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evsecc}.
  *
@@ -44,7 +45,7 @@ export interface EvseccClientOptions {
  * present in the EEBUS library, so this client is fully wired
  * immediately (no missing-library throws).
  */
-export interface EebusEvseccClient {
+export interface EebusEvseccClient extends EebusUseCaseClient {
     /**
      * Read the EVSE's `DeviceClassification.ManufacturerData` — vendor /
      * model identifiers and revisions.

package/dist/cjs/packages/eebus/eebus-evsoc-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusEvSocReading } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evsoc}.
  */
@@ -25,7 +26,7 @@ export interface EvsocClientOptions {
  * {@link EebusFeatureUnavailableError} from the `connect-core` runtime
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  */
-export interface EebusEvsocClient {
+export interface EebusEvsocClient extends EebusUseCaseClient {
     /**
      * Read the most recent SoC sample, in percent (0–100).
      *

package/dist/cjs/packages/eebus/eebus-hvac-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusHvacOperationMode, EebusHvacZoneState } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.hvac}.
  *
@@ -53,7 +54,7 @@ export interface HvacClientOptions {
  * `EebusFeatureUnavailableError` is thrown only when no `Hvac` server
  * feature exists on the peer at all.
  */
-export interface EebusHvacClient {
+export interface EebusHvacClient extends EebusUseCaseClient {
     /**
      * Read the active heating/cooling operation mode from the remote node.
      */

package/dist/cjs/packages/eebus/eebus-lpc-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
-import { EebusLpcAck, EebusLpcFailsafe, EebusLpcLimit } from '../../types/enyo-eebus-use-cases.cjs';
+import { EebusLpcAck, EebusLpcFailsafe, EebusLpcLimit, EebusLpcNack } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.lpc}.
  *
@@ -38,21 +39,53 @@ export interface LpcClientOptions {
  * {@link EebusLppClient} which is a recommendation.
  *
  * The client exposes both actor roles on a single interface:
- * - **EMS role (outbound):** {@link setConsumptionLimit}, {@link getActiveConsumptionLimit},
- *   {@link getFailsafeLimit}
- * - **CS role (inbound):** {@link onConsumptionLimitReceived}, {@link provideFailsafeLimit}
+ * - **EMS role (outbound):** {@link setConsumptionLimit}, {@link setFailsafeLimit},
+ *   {@link getActiveConsumptionLimit}, {@link getFailsafeLimit}
+ * - **EMS role (inbound):** {@link onActiveConsumptionLimitChanged},
+ *   {@link onConsumptionLimitNack}, {@link onFailsafeChanged}
+ * - **CS role (inbound):** {@link onConsumptionLimitReceived},
+ *   {@link provideFailsafeLimit}
  *
  * Consumers that only act in one role simply never call the other half — there is
  * no `asManager` / `asAppliance` split.
+ *
+ * **Acknowledgement semantics.** {@link setConsumptionLimit} resolves once
+ * the SPINE write-ack lands — the CS has accepted the message into its
+ * queue. That is *not* the same as the CS having applied the limit; for
+ * the latter, subscribe to {@link onActiveConsumptionLimitChanged}.
+ * Explicit rejections (limit out of permitted set, failsafe override
+ * engaged, etc.) arrive via {@link onConsumptionLimitNack} so EMS code
+ * does not have to poll {@link getActiveConsumptionLimit} to detect them.
  */
-export interface EebusLpcClient {
+export interface EebusLpcClient extends EebusUseCaseClient {
     /**
      * Send a consumption limit to the controllable system. The remote is
      * obligated to respect the limit until it expires, is replaced, or is
      * cleared by sending a limit with `isActive: false`.
+     *
+     * Resolves on the SPINE write-ack. See the class-level note for the
+     * difference between "accepted" and "applied"; subscribe to
+     * {@link onActiveConsumptionLimitChanged} and
+     * {@link onConsumptionLimitNack} to observe the CS's downstream
+     * decision.
+     *
      * @param limit The consumption limit to apply
      */
     setConsumptionLimit: (limit: EebusLpcLimit) => Promise<void>;
+    /**
+     * Configure the controllable system's failsafe limit — the value it
+     * falls back to when the SHIP connection to this EMS drops. The
+     * canonical use case is §14a EnWG, where a grid-operator-acting
+     * EMS pushes a 4.2 kW (or jurisdictional equivalent) floor and a
+     * fall-back duration that survives transient disconnects.
+     *
+     * Resolves on the SPINE write-ack. To learn about subsequent
+     * CS-side revisions (e.g. the CS rounds the value to its nearest
+     * supported set-point), subscribe to {@link onFailsafeChanged}.
+     *
+     * @param failsafe The failsafe configuration to apply on the CS
+     */
+    setFailsafeLimit: (failsafe: EebusLpcFailsafe) => Promise<void>;
     /**
      * Read the consumption limit currently active on the controllable system,
      * if any. Useful for verifying that a previously-sent limit was applied,
@@ -65,6 +98,45 @@ export interface EebusLpcClient {
      * it loses the connection to this EMS.
      */
     getFailsafeLimit: () => Promise<EebusLpcFailsafe>;
+    /**
+     * Subscribe to changes in the *active* consumption limit reported by
+     * the CS — fires on every inbound `loadControlLimitListData` notify.
+     * The handler receives the new active limit, or `undefined` when the
+     * CS clears the active limit (e.g. on expiry).
+     *
+     * Use this instead of polling {@link getActiveConsumptionLimit} after
+     * a {@link setConsumptionLimit} call: the SPINE write-ack resolves
+     * before the CS publishes its updated active state, so the polling
+     * pattern races against the notify.
+     *
+     * @param handler Callback invoked with the new active limit (or `undefined`)
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onActiveConsumptionLimitChanged: (handler: (limit: EebusLpcLimit | undefined) => void) => string;
+    /**
+     * Subscribe to explicit NACKs from the CS — fires when the CS
+     * rejects a previously-sent limit with a reason (e.g. value
+     * out-of-range, failsafe override active, command queue full).
+     * Distinct from the SPINE write-ack that {@link setConsumptionLimit}
+     * resolves on: a write-ack means "received", a NACK arrives as a
+     * separate event when the CS subsequently decides not to honour
+     * the limit.
+     *
+     * @param handler Callback invoked with the NACK payload
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onConsumptionLimitNack: (handler: (nack: EebusLpcNack) => void) => string;
+    /**
+     * Subscribe to CS-published failsafe revisions — fires on every
+     * inbound `deviceConfigurationKeyValueListData` notify carrying
+     * a new failsafe value or duration. Allowed by the LPC UC TS as
+     * a mid-session signal; consumers that only read the failsafe at
+     * warm-up time will otherwise miss it.
+     *
+     * @param handler Callback invoked with the revised failsafe
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onFailsafeChanged: (handler: (failsafe: EebusLpcFailsafe) => void) => string;
     /**
      * Register a handler invoked when a remote EMS sends a consumption limit
      * to this device. The handler MUST return an acknowledgement.

package/dist/cjs/packages/eebus/eebus-lpp-client.d.cts

@@ -1,4 +1,5 @@
-import { EebusLppAck, EebusLppFailsafe, EebusLppLimit } from '../../types/enyo-eebus-use-cases.cjs';
+import { EebusLppAck, EebusLppFailsafe, EebusLppLimit, EebusLppNack } from '../../types/enyo-eebus-use-cases.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Client for the EEBUS **Limitation of Power Production (LPP)** use case.
  *
@@ -8,16 +9,46 @@ import { EebusLppAck, EebusLppFailsafe, EebusLppLimit } from '../../types/enyo-e
  * is an obligation.
  *
  * The client exposes both actor roles on a single interface:
- * - **EMS role (outbound):** {@link setProductionLimit}, {@link getActiveProductionLimit},
- *   {@link getFailsafeLimit}
- * - **CS role (inbound):** {@link onProductionLimitReceived}, {@link provideFailsafeLimit}
+ * - **EMS role (outbound):** {@link setProductionLimit}, {@link setFailsafeLimit},
+ *   {@link getActiveProductionLimit}, {@link getFailsafeLimit}
+ * - **EMS role (inbound):** {@link onActiveProductionLimitChanged},
+ *   {@link onProductionLimitNack}, {@link onFailsafeChanged}
+ * - **CS role (inbound):** {@link onProductionLimitReceived},
+ *   {@link provideFailsafeLimit}
+ *
+ * **Acknowledgement semantics.** {@link setProductionLimit} resolves once
+ * the SPINE write-ack lands — the CS has accepted the message into its
+ * queue. That is *not* the same as the CS having applied the
+ * recommendation; for the latter, subscribe to
+ * {@link onActiveProductionLimitChanged}. Because LPP is advisory, a
+ * producer is free to decline; explicit declines arrive via
+ * {@link onProductionLimitNack}.
  */
-export interface EebusLppClient {
+export interface EebusLppClient extends EebusUseCaseClient {
     /**
      * Send a production limit recommendation to the producing controllable system.
+     *
+     * Resolves on the SPINE write-ack. See the class-level note for the
+     * difference between "accepted" and "applied"; subscribe to
+     * {@link onActiveProductionLimitChanged} and
+     * {@link onProductionLimitNack} to observe the producer's downstream
+     * decision.
+     *
      * @param limit The production limit recommendation to apply
      */
     setProductionLimit: (limit: EebusLppLimit) => Promise<void>;
+    /**
+     * Configure the producing controllable system's failsafe limit — the
+     * value it falls back to when the SHIP connection to this EMS drops.
+     * Used to enforce a feed-in cap (e.g. 70 % of nameplate) that
+     * survives transient disconnects even when LPP itself is advisory.
+     *
+     * Resolves on the SPINE write-ack. To learn about subsequent
+     * CS-side revisions, subscribe to {@link onFailsafeChanged}.
+     *
+     * @param failsafe The failsafe configuration to apply on the producer
+     */
+    setFailsafeLimit: (failsafe: EebusLppFailsafe) => Promise<void>;
     /**
      * Read the production limit currently active on the controllable system,
      * if any.
@@ -29,6 +60,46 @@ export interface EebusLppClient {
      * it loses the connection to this EMS.
      */
     getFailsafeLimit: () => Promise<EebusLppFailsafe>;
+    /**
+     * Subscribe to changes in the *active* production limit reported by
+     * the producer — fires on every inbound `loadControlLimitListData`
+     * notify. The handler receives the new active limit, or `undefined`
+     * when the producer clears the active limit.
+     *
+     * Use this instead of polling {@link getActiveProductionLimit} after
+     * a {@link setProductionLimit} call: the SPINE write-ack resolves
+     * before the producer publishes its updated active state, so the
+     * polling pattern races against the notify.
+     *
+     * @param handler Callback invoked with the new active limit (or `undefined`)
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onActiveProductionLimitChanged: (handler: (limit: EebusLppLimit | undefined) => void) => string;
+    /**
+     * Subscribe to explicit declines from the producer — fires when the
+     * producer rejects a previously-sent recommendation with a reason.
+     * LPP being advisory, a NACK does not breach the use case; it just
+     * tells the EMS that the producer chose not to honour the value
+     * (e.g. self-consumption priority is engaged on the inverter).
+     *
+     * Distinct from the SPINE write-ack that
+     * {@link setProductionLimit} resolves on.
+     *
+     * @param handler Callback invoked with the NACK payload
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onProductionLimitNack: (handler: (nack: EebusLppNack) => void) => string;
+    /**
+     * Subscribe to producer-published failsafe revisions — fires on every
+     * inbound `deviceConfigurationKeyValueListData` notify carrying
+     * a new failsafe value or duration. Allowed by the LPP UC TS as a
+     * mid-session signal; consumers that only read the failsafe at
+     * warm-up time will otherwise miss it.
+     *
+     * @param handler Callback invoked with the revised failsafe
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onFailsafeChanged: (handler: (failsafe: EebusLppFailsafe) => void) => string;
     /**
      * Register a handler invoked when a remote EMS sends a production limit
      * recommendation to this device.

package/dist/cjs/packages/eebus/eebus-mgcp-client.d.cts

@@ -1,4 +1,5 @@
 import { EebusMgcpReading } from '../../types/enyo-eebus-use-cases.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Client for the EEBUS **Monitoring of Grid Connection Point (MGCP)** use case.
  *
@@ -10,7 +11,7 @@ import { EebusMgcpReading } from '../../types/enyo-eebus-use-cases.cjs';
  * - **CEM role (consume):** {@link getReading}, {@link onReading}
  * - **GCP role (provide):** {@link provideReading}
  */
-export interface EebusMgcpClient {
+export interface EebusMgcpClient extends EebusUseCaseClient {
     /**
      * Read the latest telemetry from the grid connection point.
      */

package/dist/cjs/packages/eebus/eebus-mpc-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusMpcReading } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.mpc}.
  *
@@ -62,7 +63,7 @@ export interface MpcClientOptions {
  * `EebusFeatureUnavailableError` when no `Measurement` server feature
  * exists at all on the peer.
  */
-export interface EebusMpcClient {
+export interface EebusMpcClient extends EebusUseCaseClient {
     /**
      * Read the latest consumption telemetry from the controllable system.
      */

package/dist/cjs/packages/eebus/eebus-ohpcf-client.d.cts

@@ -1,5 +1,6 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusOhpcfAnnouncement, EebusOhpcfApplianceContext, EebusOhpcfFlavour, EebusOhpcfFlexibility, EebusOhpcfIncentiveTable, EebusOhpcfPlanState } from '../../types/enyo-eebus-use-cases.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.ohpcf}.
  *
@@ -59,7 +60,7 @@ export interface OhpcfClientOptions {
  * @see https://techdocs.wago.com/Software/EEBUS_Connector/en-US/3657311371.html
  * @see https://github.com/enbility/eebus-go/pull/122
  */
-export interface EebusOhpcfClient {
+export interface EebusOhpcfClient extends EebusUseCaseClient {
     /**
      * Send an incentive table to the heat pump. The heat pump will use
      * the table to plan its compressor operation over the covered horizon.

package/dist/cjs/packages/eebus/eebus-opev-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusOpevAck, EebusOpevLimit } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.opev}.
  */
@@ -34,7 +35,7 @@ export interface OpevClientOptions {
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`
  * (LoadControl itself is already present).
  */
-export interface EebusOpevClient {
+export interface EebusOpevClient extends EebusUseCaseClient {
     /**
      * Send a per-phase current limit to the EVSE. The EVSE MUST respect
      * the limit; ack is the EVSE's accept / reject decision.

package/dist/cjs/packages/eebus/eebus-oscev-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusOscevAck, EebusOscevLimit } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.oscev}.
  */
@@ -22,7 +23,7 @@ export interface OscevClientOptions {
  * {@link EebusFeatureUnavailableError} from the `connect-core` runtime
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  */
-export interface EebusOscevClient {
+export interface EebusOscevClient extends EebusUseCaseClient {
     /**
      * Send a per-phase current recommendation to the EVSE.
      *

package/dist/cjs/packages/eebus/eebus-setpoint-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusSetpointValue } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.setpoint}.
  *
@@ -54,7 +55,7 @@ export interface SetpointClientOptions {
  * supported. `EebusFeatureUnavailableError` is thrown only when no
  * `Setpoint` server feature exists on the peer at all.
  */
-export interface EebusSetpointClient {
+export interface EebusSetpointClient extends EebusUseCaseClient {
     /**
      * Read the current setpoints reported by the remote node.
      * @returns The full list of setpoints currently published by the remote.

package/dist/cjs/packages/eebus/eebus-use-case-client.cjs

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/packages/eebus/eebus-use-case-client.d.cts

@@ -0,0 +1,26 @@
+/**
+ * Common shape inherited by every typed EEBUS use-case client.
+ *
+ * Adding a shared base avoids each client growing its own warm-up
+ * vocabulary. Today vendor packages trigger the lazy SPINE handshake
+ * by issuing a fake call (e.g. `onReading(noop)` on
+ * {@link EebusMpcClient}) just to make the description-list reads
+ * happen. {@link ready} replaces that ritual with an explicit hook.
+ */
+export interface EebusUseCaseClient {
+    /**
+     * Drive the SPINE binding + description-list reads for this
+     * use-case client to completion without dispatching any real
+     * read, write, or subscription. Resolves once the handshake has
+     * landed (or rejects with an {@link EebusFeatureUnavailableError}
+     * / {@link EebusFeatureNotResolvedError} /
+     * {@link EebusRequestTimeoutError} if the peer cannot satisfy it
+     * within the client's configured `descriptionReadTimeoutMs`).
+     *
+     * Idempotent: subsequent calls resolve as soon as the handshake
+     * has succeeded once. Safe to call from package start-up to
+     * surface "peer is not ready" early instead of letting the first
+     * real call fail later.
+     */
+    ready: () => Promise<void>;
+}

package/dist/cjs/packages/eebus/eebus-vabd-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusVabdTelemetry } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.vabd}.
  */
@@ -29,7 +30,7 @@ export interface VabdClientOptions {
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  * `Measurement` and `DeviceConfiguration` are already present.
  */
-export interface EebusVabdClient {
+export interface EebusVabdClient extends EebusUseCaseClient {
     /**
      * Read the battery's current state of charge in percent (0–100).
      *

package/dist/cjs/packages/eebus/eebus-vapd-client.d.cts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.cjs';
 import { EebusVapdTelemetry } from '../../types/enyo-eebus-use-cases.cjs';
 import { SpineEntityType } from '../../types/enyo-spine.cjs';
+import { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.vapd}.
  */
@@ -28,7 +29,7 @@ export interface VapdClientOptions {
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  * `Measurement` and `DeviceConfiguration` are already present.
  */
-export interface EebusVapdClient {
+export interface EebusVapdClient extends EebusUseCaseClient {
     /**
      * Read the PV system's current active production in Watts.
      *

package/dist/cjs/packages/eebus/energy-app-eebus.d.cts

@@ -7,6 +7,7 @@ export { EebusDeviceManagement } from './eebus-device-management.cjs';
 export { EebusFeatureCatalog, EebusFeatureAddressMatch } from './eebus-feature-catalog.cjs';
 export { EebusIdentityService } from './eebus-identity-service.cjs';
 export { EebusSpineLowLevel } from './eebus-spine-low-level.cjs';
+export { EebusUseCaseClient } from './eebus-use-case-client.cjs';
 export { EebusUseCaseRegistry } from './eebus-use-case-registry.cjs';
 export { EebusHvacClient, HvacClientOptions } from './eebus-hvac-client.cjs';
 export { EebusLpcClient, LpcClientOptions } from './eebus-lpc-client.cjs';

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

@@ -54,6 +54,27 @@ export interface EebusLpcAck {
     /** Optional human-readable reason when {@link accepted} is `false` */
     reason?: string;
 }
+/**
+ * Push-side rejection from a controllable system, delivered to an EMS
+ * subscriber via {@link EebusLpcClient.onConsumptionLimitNack}.
+ *
+ * Distinct from the SPINE write-ack that
+ * {@link EebusLpcClient.setConsumptionLimit} resolves on: a write-ack
+ * means "the CS received the limit message". A NACK arrives as a
+ * separate event when the CS subsequently decides not to honour the
+ * limit (out-of-range value, failsafe override active, queue full,
+ * etc.).
+ */
+export interface EebusLpcNack {
+    /** Human-readable reason the CS rejected the limit. */
+    reason: string;
+    /**
+     * The limit the CS rejected, when attribution to the originating
+     * write is available. Omitted on peers that don't echo the
+     * rejected payload (some VICTRON / KEBA firmwares).
+     */
+    rejectedLimit?: EebusLpcLimit;
+}
 /**
  * A production limit issued by an Energy Management System to a producing
  * Controllable System (e.g. a PV inverter). LPP limits are recommendations:
@@ -89,6 +110,26 @@ export interface EebusLppAck {
     /** Optional human-readable reason when {@link accepted} is `false` */
     reason?: string;
 }
+/**
+ * Push-side rejection from a producing controllable system, delivered to
+ * an EMS subscriber via {@link EebusLppClient.onProductionLimitNack}.
+ *
+ * LPP is a *recommendation*: the producing CS may decline a
+ * recommendation without violating the use case (compare with LPC,
+ * where a NACK means the obligation could not be honoured). A NACK
+ * arrives as a separate event after the SPINE write-ack that
+ * {@link EebusLppClient.setProductionLimit} resolves on.
+ */
+export interface EebusLppNack {
+    /** Human-readable reason the producer declined the recommendation. */
+    reason: string;
+    /**
+     * The recommendation the producer declined, when attribution to the
+     * originating write is available. Omitted on peers that don't echo
+     * the declined payload.
+     */
+    rejectedLimit?: EebusLppLimit;
+}
 /**
  * A single telemetry reading from a grid connection point.
  * Positive power values indicate import (consumption from the grid);

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.140';
+exports.SDK_VERSION = '0.0.141';
 /**
  * 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.140";
+export declare const SDK_VERSION = "0.0.141";
 /**
  * Gets the current SDK version.
  * @returns The semantic version string of the SDK

package/dist/packages/eebus/eebus-cevc-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusCevcAck, EebusCevcChargingPlan, EebusOhpcfIncentiveTable } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.cevc}.
  */
@@ -33,7 +34,7 @@ export interface CevcClientOptions {
  * until `ElectricalConnectionClient` and `TimeSeriesClient` both land
  * in `@enyo-energy/eebus`.
  */
-export interface EebusCevcClient {
+export interface EebusCevcClient extends EebusUseCaseClient {
     /**
      * Send a time-series charging plan to the EV. The EV ack carries
      * either acceptance or a reason for rejection (e.g. plan exceeds

package/dist/packages/eebus/eebus-evcc-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusEvCommunicationStandardEnum, EebusEvConnectionState, EebusEvIdentification } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evcc}.
  *
@@ -34,7 +35,7 @@ export interface EvccClientOptions {
  * `@enyo-energy/eebus`. The SDK interface is shipped now so consumers
  * can compile against the final shape.
  */
-export interface EebusEvccClient {
+export interface EebusEvccClient extends EebusUseCaseClient {
     /**
      * Read the EV's identification (EVCCID and identification type).
      * Returns `undefined` when the EV does not publish an

package/dist/packages/eebus/eebus-evcem-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusEvcemReading } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evcem}.
  */
@@ -26,7 +27,7 @@ export interface EvcemClientOptions {
  * {@link EebusFeatureUnavailableError} from the `connect-core` runtime
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  */
-export interface EebusEvcemClient {
+export interface EebusEvcemClient extends EebusUseCaseClient {
     /**
      * Read the most recent telemetry sample from the EV charging session.
      *

package/dist/packages/eebus/eebus-evsecc-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusEvseManufacturerData, EebusEvseOperatingState } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evsecc}.
  *
@@ -44,7 +45,7 @@ export interface EvseccClientOptions {
  * present in the EEBUS library, so this client is fully wired
  * immediately (no missing-library throws).
  */
-export interface EebusEvseccClient {
+export interface EebusEvseccClient extends EebusUseCaseClient {
     /**
      * Read the EVSE's `DeviceClassification.ManufacturerData` — vendor /
      * model identifiers and revisions.

package/dist/packages/eebus/eebus-evsoc-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusEvSocReading } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.evsoc}.
  */
@@ -25,7 +26,7 @@ export interface EvsocClientOptions {
  * {@link EebusFeatureUnavailableError} from the `connect-core` runtime
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  */
-export interface EebusEvsocClient {
+export interface EebusEvsocClient extends EebusUseCaseClient {
     /**
      * Read the most recent SoC sample, in percent (0–100).
      *

package/dist/packages/eebus/eebus-hvac-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusHvacOperationMode, EebusHvacZoneState } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.hvac}.
  *
@@ -53,7 +54,7 @@ export interface HvacClientOptions {
  * `EebusFeatureUnavailableError` is thrown only when no `Hvac` server
  * feature exists on the peer at all.
  */
-export interface EebusHvacClient {
+export interface EebusHvacClient extends EebusUseCaseClient {
     /**
      * Read the active heating/cooling operation mode from the remote node.
      */

package/dist/packages/eebus/eebus-lpc-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
-import { EebusLpcAck, EebusLpcFailsafe, EebusLpcLimit } from '../../types/enyo-eebus-use-cases.js';
+import { EebusLpcAck, EebusLpcFailsafe, EebusLpcLimit, EebusLpcNack } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.lpc}.
  *
@@ -38,21 +39,53 @@ export interface LpcClientOptions {
  * {@link EebusLppClient} which is a recommendation.
  *
  * The client exposes both actor roles on a single interface:
- * - **EMS role (outbound):** {@link setConsumptionLimit}, {@link getActiveConsumptionLimit},
- *   {@link getFailsafeLimit}
- * - **CS role (inbound):** {@link onConsumptionLimitReceived}, {@link provideFailsafeLimit}
+ * - **EMS role (outbound):** {@link setConsumptionLimit}, {@link setFailsafeLimit},
+ *   {@link getActiveConsumptionLimit}, {@link getFailsafeLimit}
+ * - **EMS role (inbound):** {@link onActiveConsumptionLimitChanged},
+ *   {@link onConsumptionLimitNack}, {@link onFailsafeChanged}
+ * - **CS role (inbound):** {@link onConsumptionLimitReceived},
+ *   {@link provideFailsafeLimit}
  *
  * Consumers that only act in one role simply never call the other half — there is
  * no `asManager` / `asAppliance` split.
+ *
+ * **Acknowledgement semantics.** {@link setConsumptionLimit} resolves once
+ * the SPINE write-ack lands — the CS has accepted the message into its
+ * queue. That is *not* the same as the CS having applied the limit; for
+ * the latter, subscribe to {@link onActiveConsumptionLimitChanged}.
+ * Explicit rejections (limit out of permitted set, failsafe override
+ * engaged, etc.) arrive via {@link onConsumptionLimitNack} so EMS code
+ * does not have to poll {@link getActiveConsumptionLimit} to detect them.
  */
-export interface EebusLpcClient {
+export interface EebusLpcClient extends EebusUseCaseClient {
     /**
      * Send a consumption limit to the controllable system. The remote is
      * obligated to respect the limit until it expires, is replaced, or is
      * cleared by sending a limit with `isActive: false`.
+     *
+     * Resolves on the SPINE write-ack. See the class-level note for the
+     * difference between "accepted" and "applied"; subscribe to
+     * {@link onActiveConsumptionLimitChanged} and
+     * {@link onConsumptionLimitNack} to observe the CS's downstream
+     * decision.
+     *
      * @param limit The consumption limit to apply
      */
     setConsumptionLimit: (limit: EebusLpcLimit) => Promise<void>;
+    /**
+     * Configure the controllable system's failsafe limit — the value it
+     * falls back to when the SHIP connection to this EMS drops. The
+     * canonical use case is §14a EnWG, where a grid-operator-acting
+     * EMS pushes a 4.2 kW (or jurisdictional equivalent) floor and a
+     * fall-back duration that survives transient disconnects.
+     *
+     * Resolves on the SPINE write-ack. To learn about subsequent
+     * CS-side revisions (e.g. the CS rounds the value to its nearest
+     * supported set-point), subscribe to {@link onFailsafeChanged}.
+     *
+     * @param failsafe The failsafe configuration to apply on the CS
+     */
+    setFailsafeLimit: (failsafe: EebusLpcFailsafe) => Promise<void>;
     /**
      * Read the consumption limit currently active on the controllable system,
      * if any. Useful for verifying that a previously-sent limit was applied,
@@ -65,6 +98,45 @@ export interface EebusLpcClient {
      * it loses the connection to this EMS.
      */
     getFailsafeLimit: () => Promise<EebusLpcFailsafe>;
+    /**
+     * Subscribe to changes in the *active* consumption limit reported by
+     * the CS — fires on every inbound `loadControlLimitListData` notify.
+     * The handler receives the new active limit, or `undefined` when the
+     * CS clears the active limit (e.g. on expiry).
+     *
+     * Use this instead of polling {@link getActiveConsumptionLimit} after
+     * a {@link setConsumptionLimit} call: the SPINE write-ack resolves
+     * before the CS publishes its updated active state, so the polling
+     * pattern races against the notify.
+     *
+     * @param handler Callback invoked with the new active limit (or `undefined`)
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onActiveConsumptionLimitChanged: (handler: (limit: EebusLpcLimit | undefined) => void) => string;
+    /**
+     * Subscribe to explicit NACKs from the CS — fires when the CS
+     * rejects a previously-sent limit with a reason (e.g. value
+     * out-of-range, failsafe override active, command queue full).
+     * Distinct from the SPINE write-ack that {@link setConsumptionLimit}
+     * resolves on: a write-ack means "received", a NACK arrives as a
+     * separate event when the CS subsequently decides not to honour
+     * the limit.
+     *
+     * @param handler Callback invoked with the NACK payload
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onConsumptionLimitNack: (handler: (nack: EebusLpcNack) => void) => string;
+    /**
+     * Subscribe to CS-published failsafe revisions — fires on every
+     * inbound `deviceConfigurationKeyValueListData` notify carrying
+     * a new failsafe value or duration. Allowed by the LPC UC TS as
+     * a mid-session signal; consumers that only read the failsafe at
+     * warm-up time will otherwise miss it.
+     *
+     * @param handler Callback invoked with the revised failsafe
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onFailsafeChanged: (handler: (failsafe: EebusLpcFailsafe) => void) => string;
     /**
      * Register a handler invoked when a remote EMS sends a consumption limit
      * to this device. The handler MUST return an acknowledgement.

package/dist/packages/eebus/eebus-lpp-client.d.ts

@@ -1,4 +1,5 @@
-import { EebusLppAck, EebusLppFailsafe, EebusLppLimit } from '../../types/enyo-eebus-use-cases.js';
+import { EebusLppAck, EebusLppFailsafe, EebusLppLimit, EebusLppNack } from '../../types/enyo-eebus-use-cases.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Client for the EEBUS **Limitation of Power Production (LPP)** use case.
  *
@@ -8,16 +9,46 @@ import { EebusLppAck, EebusLppFailsafe, EebusLppLimit } from '../../types/enyo-e
  * is an obligation.
  *
  * The client exposes both actor roles on a single interface:
- * - **EMS role (outbound):** {@link setProductionLimit}, {@link getActiveProductionLimit},
- *   {@link getFailsafeLimit}
- * - **CS role (inbound):** {@link onProductionLimitReceived}, {@link provideFailsafeLimit}
+ * - **EMS role (outbound):** {@link setProductionLimit}, {@link setFailsafeLimit},
+ *   {@link getActiveProductionLimit}, {@link getFailsafeLimit}
+ * - **EMS role (inbound):** {@link onActiveProductionLimitChanged},
+ *   {@link onProductionLimitNack}, {@link onFailsafeChanged}
+ * - **CS role (inbound):** {@link onProductionLimitReceived},
+ *   {@link provideFailsafeLimit}
+ *
+ * **Acknowledgement semantics.** {@link setProductionLimit} resolves once
+ * the SPINE write-ack lands — the CS has accepted the message into its
+ * queue. That is *not* the same as the CS having applied the
+ * recommendation; for the latter, subscribe to
+ * {@link onActiveProductionLimitChanged}. Because LPP is advisory, a
+ * producer is free to decline; explicit declines arrive via
+ * {@link onProductionLimitNack}.
  */
-export interface EebusLppClient {
+export interface EebusLppClient extends EebusUseCaseClient {
     /**
      * Send a production limit recommendation to the producing controllable system.
+     *
+     * Resolves on the SPINE write-ack. See the class-level note for the
+     * difference between "accepted" and "applied"; subscribe to
+     * {@link onActiveProductionLimitChanged} and
+     * {@link onProductionLimitNack} to observe the producer's downstream
+     * decision.
+     *
      * @param limit The production limit recommendation to apply
      */
     setProductionLimit: (limit: EebusLppLimit) => Promise<void>;
+    /**
+     * Configure the producing controllable system's failsafe limit — the
+     * value it falls back to when the SHIP connection to this EMS drops.
+     * Used to enforce a feed-in cap (e.g. 70 % of nameplate) that
+     * survives transient disconnects even when LPP itself is advisory.
+     *
+     * Resolves on the SPINE write-ack. To learn about subsequent
+     * CS-side revisions, subscribe to {@link onFailsafeChanged}.
+     *
+     * @param failsafe The failsafe configuration to apply on the producer
+     */
+    setFailsafeLimit: (failsafe: EebusLppFailsafe) => Promise<void>;
     /**
      * Read the production limit currently active on the controllable system,
      * if any.
@@ -29,6 +60,46 @@ export interface EebusLppClient {
      * it loses the connection to this EMS.
      */
     getFailsafeLimit: () => Promise<EebusLppFailsafe>;
+    /**
+     * Subscribe to changes in the *active* production limit reported by
+     * the producer — fires on every inbound `loadControlLimitListData`
+     * notify. The handler receives the new active limit, or `undefined`
+     * when the producer clears the active limit.
+     *
+     * Use this instead of polling {@link getActiveProductionLimit} after
+     * a {@link setProductionLimit} call: the SPINE write-ack resolves
+     * before the producer publishes its updated active state, so the
+     * polling pattern races against the notify.
+     *
+     * @param handler Callback invoked with the new active limit (or `undefined`)
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onActiveProductionLimitChanged: (handler: (limit: EebusLppLimit | undefined) => void) => string;
+    /**
+     * Subscribe to explicit declines from the producer — fires when the
+     * producer rejects a previously-sent recommendation with a reason.
+     * LPP being advisory, a NACK does not breach the use case; it just
+     * tells the EMS that the producer chose not to honour the value
+     * (e.g. self-consumption priority is engaged on the inverter).
+     *
+     * Distinct from the SPINE write-ack that
+     * {@link setProductionLimit} resolves on.
+     *
+     * @param handler Callback invoked with the NACK payload
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onProductionLimitNack: (handler: (nack: EebusLppNack) => void) => string;
+    /**
+     * Subscribe to producer-published failsafe revisions — fires on every
+     * inbound `deviceConfigurationKeyValueListData` notify carrying
+     * a new failsafe value or duration. Allowed by the LPP UC TS as a
+     * mid-session signal; consumers that only read the failsafe at
+     * warm-up time will otherwise miss it.
+     *
+     * @param handler Callback invoked with the revised failsafe
+     * @returns Listener ID that can be passed to {@link removeListener}
+     */
+    onFailsafeChanged: (handler: (failsafe: EebusLppFailsafe) => void) => string;
     /**
      * Register a handler invoked when a remote EMS sends a production limit
      * recommendation to this device.

package/dist/packages/eebus/eebus-mgcp-client.d.ts

@@ -1,4 +1,5 @@
 import { EebusMgcpReading } from '../../types/enyo-eebus-use-cases.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Client for the EEBUS **Monitoring of Grid Connection Point (MGCP)** use case.
  *
@@ -10,7 +11,7 @@ import { EebusMgcpReading } from '../../types/enyo-eebus-use-cases.js';
  * - **CEM role (consume):** {@link getReading}, {@link onReading}
  * - **GCP role (provide):** {@link provideReading}
  */
-export interface EebusMgcpClient {
+export interface EebusMgcpClient extends EebusUseCaseClient {
     /**
      * Read the latest telemetry from the grid connection point.
      */

package/dist/packages/eebus/eebus-mpc-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusMpcReading } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.mpc}.
  *
@@ -62,7 +63,7 @@ export interface MpcClientOptions {
  * `EebusFeatureUnavailableError` when no `Measurement` server feature
  * exists at all on the peer.
  */
-export interface EebusMpcClient {
+export interface EebusMpcClient extends EebusUseCaseClient {
     /**
      * Read the latest consumption telemetry from the controllable system.
      */

package/dist/packages/eebus/eebus-ohpcf-client.d.ts

@@ -1,5 +1,6 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusOhpcfAnnouncement, EebusOhpcfApplianceContext, EebusOhpcfFlavour, EebusOhpcfFlexibility, EebusOhpcfIncentiveTable, EebusOhpcfPlanState } from '../../types/enyo-eebus-use-cases.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.ohpcf}.
  *
@@ -59,7 +60,7 @@ export interface OhpcfClientOptions {
  * @see https://techdocs.wago.com/Software/EEBUS_Connector/en-US/3657311371.html
  * @see https://github.com/enbility/eebus-go/pull/122
  */
-export interface EebusOhpcfClient {
+export interface EebusOhpcfClient extends EebusUseCaseClient {
     /**
      * Send an incentive table to the heat pump. The heat pump will use
      * the table to plan its compressor operation over the covered horizon.

package/dist/packages/eebus/eebus-opev-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusOpevAck, EebusOpevLimit } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.opev}.
  */
@@ -34,7 +35,7 @@ export interface OpevClientOptions {
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`
  * (LoadControl itself is already present).
  */
-export interface EebusOpevClient {
+export interface EebusOpevClient extends EebusUseCaseClient {
     /**
      * Send a per-phase current limit to the EVSE. The EVSE MUST respect
      * the limit; ack is the EVSE's accept / reject decision.

package/dist/packages/eebus/eebus-oscev-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusOscevAck, EebusOscevLimit } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.oscev}.
  */
@@ -22,7 +23,7 @@ export interface OscevClientOptions {
  * {@link EebusFeatureUnavailableError} from the `connect-core` runtime
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  */
-export interface EebusOscevClient {
+export interface EebusOscevClient extends EebusUseCaseClient {
     /**
      * Send a per-phase current recommendation to the EVSE.
      *

package/dist/packages/eebus/eebus-setpoint-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusSetpointValue } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.setpoint}.
  *
@@ -54,7 +55,7 @@ export interface SetpointClientOptions {
  * supported. `EebusFeatureUnavailableError` is thrown only when no
  * `Setpoint` server feature exists on the peer at all.
  */
-export interface EebusSetpointClient {
+export interface EebusSetpointClient extends EebusUseCaseClient {
     /**
      * Read the current setpoints reported by the remote node.
      * @returns The full list of setpoints currently published by the remote.

package/dist/packages/eebus/eebus-use-case-client.d.ts

@@ -0,0 +1,26 @@
+/**
+ * Common shape inherited by every typed EEBUS use-case client.
+ *
+ * Adding a shared base avoids each client growing its own warm-up
+ * vocabulary. Today vendor packages trigger the lazy SPINE handshake
+ * by issuing a fake call (e.g. `onReading(noop)` on
+ * {@link EebusMpcClient}) just to make the description-list reads
+ * happen. {@link ready} replaces that ritual with an explicit hook.
+ */
+export interface EebusUseCaseClient {
+    /**
+     * Drive the SPINE binding + description-list reads for this
+     * use-case client to completion without dispatching any real
+     * read, write, or subscription. Resolves once the handshake has
+     * landed (or rejects with an {@link EebusFeatureUnavailableError}
+     * / {@link EebusFeatureNotResolvedError} /
+     * {@link EebusRequestTimeoutError} if the peer cannot satisfy it
+     * within the client's configured `descriptionReadTimeoutMs`).
+     *
+     * Idempotent: subsequent calls resolve as soon as the handshake
+     * has succeeded once. Safe to call from package start-up to
+     * surface "peer is not ready" early instead of letting the first
+     * real call fail later.
+     */
+    ready: () => Promise<void>;
+}

package/dist/packages/eebus/eebus-use-case-client.js

@@ -0,0 +1 @@
+export {};

package/dist/packages/eebus/eebus-vabd-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusVabdTelemetry } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.vabd}.
  */
@@ -29,7 +30,7 @@ export interface VabdClientOptions {
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  * `Measurement` and `DeviceConfiguration` are already present.
  */
-export interface EebusVabdClient {
+export interface EebusVabdClient extends EebusUseCaseClient {
     /**
      * Read the battery's current state of charge in percent (0–100).
      *

package/dist/packages/eebus/eebus-vapd-client.d.ts

@@ -1,6 +1,7 @@
 import { SpineRemoteTarget } from '../../types/enyo-eebus.js';
 import { EebusVapdTelemetry } from '../../types/enyo-eebus-use-cases.js';
 import { SpineEntityType } from '../../types/enyo-spine.js';
+import { EebusUseCaseClient } from './eebus-use-case-client.js';
 /**
  * Per-call configuration for {@link EebusUseCaseRegistry.vapd}.
  */
@@ -28,7 +29,7 @@ export interface VapdClientOptions {
  * until `ElectricalConnectionClient` lands in `@enyo-energy/eebus`.
  * `Measurement` and `DeviceConfiguration` are already present.
  */
-export interface EebusVapdClient {
+export interface EebusVapdClient extends EebusUseCaseClient {
     /**
      * Read the PV system's current active production in Watts.
      *

package/dist/packages/eebus/energy-app-eebus.d.ts

@@ -7,6 +7,7 @@ export { EebusDeviceManagement } from './eebus-device-management.js';
 export { EebusFeatureCatalog, EebusFeatureAddressMatch } from './eebus-feature-catalog.js';
 export { EebusIdentityService } from './eebus-identity-service.js';
 export { EebusSpineLowLevel } from './eebus-spine-low-level.js';
+export { EebusUseCaseClient } from './eebus-use-case-client.js';
 export { EebusUseCaseRegistry } from './eebus-use-case-registry.js';
 export { EebusHvacClient, HvacClientOptions } from './eebus-hvac-client.js';
 export { EebusLpcClient, LpcClientOptions } from './eebus-lpc-client.js';

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

@@ -54,6 +54,27 @@ export interface EebusLpcAck {
     /** Optional human-readable reason when {@link accepted} is `false` */
     reason?: string;
 }
+/**
+ * Push-side rejection from a controllable system, delivered to an EMS
+ * subscriber via {@link EebusLpcClient.onConsumptionLimitNack}.
+ *
+ * Distinct from the SPINE write-ack that
+ * {@link EebusLpcClient.setConsumptionLimit} resolves on: a write-ack
+ * means "the CS received the limit message". A NACK arrives as a
+ * separate event when the CS subsequently decides not to honour the
+ * limit (out-of-range value, failsafe override active, queue full,
+ * etc.).
+ */
+export interface EebusLpcNack {
+    /** Human-readable reason the CS rejected the limit. */
+    reason: string;
+    /**
+     * The limit the CS rejected, when attribution to the originating
+     * write is available. Omitted on peers that don't echo the
+     * rejected payload (some VICTRON / KEBA firmwares).
+     */
+    rejectedLimit?: EebusLpcLimit;
+}
 /**
  * A production limit issued by an Energy Management System to a producing
  * Controllable System (e.g. a PV inverter). LPP limits are recommendations:
@@ -89,6 +110,26 @@ export interface EebusLppAck {
     /** Optional human-readable reason when {@link accepted} is `false` */
     reason?: string;
 }
+/**
+ * Push-side rejection from a producing controllable system, delivered to
+ * an EMS subscriber via {@link EebusLppClient.onProductionLimitNack}.
+ *
+ * LPP is a *recommendation*: the producing CS may decline a
+ * recommendation without violating the use case (compare with LPC,
+ * where a NACK means the obligation could not be honoured). A NACK
+ * arrives as a separate event after the SPINE write-ack that
+ * {@link EebusLppClient.setProductionLimit} resolves on.
+ */
+export interface EebusLppNack {
+    /** Human-readable reason the producer declined the recommendation. */
+    reason: string;
+    /**
+     * The recommendation the producer declined, when attribution to the
+     * originating write is available. Omitted on peers that don't echo
+     * the declined payload.
+     */
+    rejectedLimit?: EebusLppLimit;
+}
 /**
  * A single telemetry reading from a grid connection point.
  * Positive power values indicate import (consumption from the grid);

package/dist/version.d.ts

@@ -5,7 +5,7 @@
 /**
  * Current version of the enyo Energy App SDK.
  */
-export declare const SDK_VERSION = "0.0.140";
+export declare const SDK_VERSION = "0.0.141";
 /**
  * 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 = '0.0.140';
+export const SDK_VERSION = '0.0.141';
 /**
  * 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": "0.0.140",
+  "version": "0.0.141",
   "description": "enyo Energy App SDK",
   "type": "module",
   "main": "dist/index.js",