@matter/types 0.13.0-alpha.0-20250304-d4a7592a4 → 0.13.0-alpha.0-20250307-ebf84a05a

package/src/clusters/device-energy-management.ts

@@ -8,8 +8,8 @@
 
 import { MutableCluster } from "../cluster/mutation/MutableCluster.js";
 import { Attribute, Command, TlvNoResponse, Event, EventPriority, FixedAttribute } from "../cluster/Cluster.js";
-import { TlvArray } from "../tlv/TlvArray.js";
 import { TlvField, TlvObject, TlvOptionalField } from "../tlv/TlvObject.js";
+import { TlvArray } from "../tlv/TlvArray.js";
 import { TlvInt64, TlvUInt32, TlvEnum, TlvUInt16, TlvEpochS, TlvInt32, TlvUInt8, TlvInt8 } from "../tlv/TlvNumber.js";
 import { TypeFromSchema } from "../tlv/TlvSchema.js";
 import { TlvNullable } from "../tlv/TlvNullable.js";
@@ -34,14 +34,15 @@ export namespace DeviceEnergyManagement {
          * curtail power requirements during peak periods, but can also be used to turn on an ESA if there is excess
          * renewable or local generation (Solar PV).
          *
-         * For example, a home may have solar PV which often produces more power than the home requires,
-         *
-         * resulting in the excess power flowing into the grid. This excess power naturally fluctuates when clouds pass
-         * overhead and other loads in the home are switched on and off.
+         * For example, a home may have solar PV which often produces more power than the home requires, resulting in
+         * the excess power flowing into the grid. This excess power naturally fluctuates when clouds pass overhead and
+         * other loads in the home are switched on and off.
          *
          * EVSE Example: An EMS may therefore be able to turn on the EVSE (if the vehicle is plugged in) and can start
          * charging the vehicle, and periodically modify the charging power depending on PV generation and other home
-         * loads, so as to minimize import and export to the grid.
+         * loads, so as to minimize import and export to the grid. An EMS may also use this feature to control the
+         * discharging (and re-charging) of the vehicle if the EVSE and vehicle support the V2X feature of the EVSE
+         * cluster of the associated EVSE device.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.2.4.1
          */
@@ -139,8 +140,9 @@ export namespace DeviceEnergyManagement {
         /**
          * Pausable (PAU)
          *
-         * ESAs which support the Pausable feature, allow an EMS to recommend a pause in the middle of a forecast power
-         * profile that the ESA is currently using.
+         * ESAs which support the Pausable feature, allow an EMS to recommend a pause in the middle of a
+         *
+         * forecast power profile that the ESA is currently using.
          *
          * Washing machine example: A Washing Machine is in operation, and starting its water heating step.
          *
@@ -197,8 +199,9 @@ export namespace DeviceEnergyManagement {
          *
          * ESAs which support the Constraint-Based Adjustment feature allow an EMS to inform the ESA of periods during
          * which power usage should be modified (for example when the EMS has been made aware that the grid supplier
-         * has requested reduced energy usage due to overall peak grid demand) and may cause the ESA to modify the
-         * intended power profile has previously suggested it would use.
+         * has requested reduced energy usage due to overall peak grid demand)
+         *
+         * and may cause the ESA to modify the intended power profile has previously suggested it would use.
          *
          * EVSE example: An EVSE scheduling system may have determined that the vehicle would be charged starting at a
          * moderate rate at 1am, so that it has enough charge by the time it is needed later that morning.
@@ -206,9 +209,8 @@ export namespace DeviceEnergyManagement {
          * However, the DSR service provider has informed the EMS that due to high forecast winds it is now forecast
          * that there will be very cheap energy available from wind generation between 2am and 3am.
          *
-         * The EMS first requests the Forecast data from each of its registered ESAs. It determines that the
-         *
-         * EVSE has a power profile suggesting it plans to start charging the vehicle at 1am.
+         * The EMS first requests the Forecast data from each of its registered ESAs. It determines that the EVSE has a
+         * power profile suggesting it plans to start charging the vehicle at 1am.
          *
          * The EMS can then try to reduce the cost of charging the EV by informing the EVSE of the desire to increase
          * the charging between scheduled times.
@@ -223,41 +225,37 @@ export namespace DeviceEnergyManagement {
     }
 
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10
      */
     export const TlvPowerAdjust = TlvObject({
         /**
          * This field shall indicate the minimum power that the ESA can have its power adjusted to.
          *
-         * Note that this is a signed value. Negative values indicate power flows away from loads (e.g. charging a
-         * battery inverter).
+         * Note that this is a signed value. Negative values indicate power flows out of the node (e.g. discharging a
+         * battery).
          *
-         * MinPower shall be less than MaxPower.
-         *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.1
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.1
          */
         minPower: TlvField(0, TlvInt64),
 
         /**
          * This field shall indicate the maximum power that the ESA can have its power adjusted to.
          *
-         * Note that this is a signed value. Negative values indicate power flows away from loads (e.g. charging a
-         * battery inverter).
-         *
-         * MinPower shall be less than MaxPower.
+         * Note that this is a signed value. Negative values indicate power flows out of the node (e.g. discharging a
+         * battery).
          *
          * For example, if the charging current of an EVSE can be adjusted within the range of 6A to 32A on a 230V
          * supply, then the power adjustment range is between 1380W and 7360W. Here the MinPower would be 1380W, and
          * MaxPower would be 7360W.
          *
-         * For example, if a battery storage inverter can discharge between 0 to 3000W towards a load, then its
-         * MinPower would be 0W and its MaxPower would be 3000W.
+         * For example, if a battery storage inverter can discharge between 0 to 3000W towards a load, then power is
+         * flowing out of the node and is therefore negative. Its MinPower would be -3000W and its MaxPower would be 0W.
          *
          * In another example, if a battery storage inverter can charge its internal battery, between 0W and 2000W.
-         * Here power is flowing away from the home loads, so the power values need to be negative. As such the
-         * MinPower becomes -2000W and MaxPower becomes 0W.
+         * Here power is flowing into the node when charging. As such the MinPower becomes 0W and MaxPower becomes
+         * 2000W.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.2
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.2
          */
         maxPower: TlvField(1, TlvInt64),
 
@@ -266,9 +264,7 @@ export namespace DeviceEnergyManagement {
          * adjustment. Manufacturers may use this to as an anti-cycling capability to avoid controllers from rapidly
          * making power adjustments.
          *
-         * Note that MinDuration shall be less than MaxDuration.
-         *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.3
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.3
          */
         minDuration: TlvField(2, TlvUInt32),
 
@@ -277,18 +273,68 @@ export namespace DeviceEnergyManagement {
          * adjustment. Manufacturers may use this to protect the user experience, to avoid over heating of the ESA,
          * ensuring that there is sufficient headroom to use or store energy in the ESA or for any other reason.
          *
-         * Note that MinDuration shall be less than MaxDuration.
-         *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.4
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.4
          */
         maxDuration: TlvField(3, TlvUInt32)
     });
 
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10
      */
     export interface PowerAdjust extends TypeFromSchema<typeof TlvPowerAdjust> {}
 
+    /**
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.8
+     */
+    export enum PowerAdjustReason {
+        /**
+         * There is no Power Adjustment active
+         */
+        NoAdjustment = 0,
+
+        /**
+         * There is PowerAdjustment active due to local EMS optimization
+         */
+        LocalOptimizationAdjustment = 1,
+
+        /**
+         * There is PowerAdjustment active due to local EMS optimization
+         */
+        GridOptimizationAdjustment = 2
+    }
+
+    /**
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11
+     */
+    export const TlvPowerAdjustCapability = TlvObject({
+        /**
+         * This field shall indicate how the ESA can be adjusted at the current time.
+         *
+         * For example, a battery storage inverter may need to regulate its internal temperature, or the charging rate
+         * of the battery may be limited due to cold temperatures, or a change in the state of charge of the battery
+         * may mean that the maximum charging or discharging rate is limited.
+         *
+         * An empty list shall indicate that no power adjustment is currently possible.
+         *
+         * Multiple entries in the list allow indicating that permutations of scenarios may be possible.
+         *
+         * For example, a 10kWh battery could be at 80% state of charge. If charging at 2kW, then it would be full in 1
+         * hour. However, it could be discharged at 2kW for 4 hours.
+         *
+         * In this example the list of PowerAdjustStructs allows multiple scenarios to be offered as follows:
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.12
+         */
+        powerAdjustCapability: TlvField(0, TlvNullable(TlvArray(TlvPowerAdjust, { maxLength: 8 }))),
+
+        cause: TlvField(1, TlvEnum<PowerAdjustReason>())
+    });
+
+    /**
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11
+     */
+    export interface PowerAdjustCapability extends TypeFromSchema<typeof TlvPowerAdjustCapability> {}
+
     /**
      * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.6
      */
@@ -398,9 +444,9 @@ export namespace DeviceEnergyManagement {
         /**
          * This field shall indicate the approximate energy used by the ESA during the session.
          *
-         * For example, if the ESA was on and was adjusted to be switched off, then this shall be 0W. If this was a
-         * battery inverter that was requested to charge it would have a negative energy use. If this was a normal load
-         * that was turned on, then it will have positive value.
+         * For example, if the ESA was on and was adjusted to be switched off, then this shall be 0 mWh. If this was a
+         * battery inverter that was requested to discharge it would have a negative EnergyUse value. If this was a
+         * normal load that was turned on, then it will have positive value.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.2.10.2.3
          */
@@ -466,13 +512,13 @@ export namespace DeviceEnergyManagement {
      * This indicates a generic mechanism for expressing cost to run an appliance, in terms of financial, GHG
      * emissions, comfort value etc.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.8
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9
      */
     export const TlvCost = TlvObject({
         /**
          * This field shall indicate the type of cost being represented (see CostTypeEnum).
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.8.1
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.1
          */
         costType: TlvField(0, TlvEnum<CostType>()),
 
@@ -482,7 +528,7 @@ export namespace DeviceEnergyManagement {
          *
          * For example, if the Value was -302 and DecimalPoints was 2, then this would represent a benefit of 3.02.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.8.2
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.2
          */
         value: TlvField(1, TlvInt32),
 
@@ -490,7 +536,7 @@ export namespace DeviceEnergyManagement {
          * This field shall indicate the number of digits to the right of the decimal point in the Value field. For
          * example, if the Value was 102 and DecimalPoints was 2, then this would represent a cost of 1.02.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.8.3
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.3
          */
         decimalPoints: TlvField(2, TlvUInt8),
 
@@ -500,7 +546,7 @@ export namespace DeviceEnergyManagement {
          *
          * This is an optional field. It shall be included if CostType is Financial.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.8.4
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9.4
          */
         currency: TlvOptionalField(3, TlvUInt16.bound({ max: 999 }))
     });
@@ -509,34 +555,34 @@ export namespace DeviceEnergyManagement {
      * This indicates a generic mechanism for expressing cost to run an appliance, in terms of financial, GHG
      * emissions, comfort value etc.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.8
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.9
      */
     export interface Cost extends TypeFromSchema<typeof TlvCost> {}
 
     /**
      * This indicates a specific stage of an ESA’s operation.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14
      */
     export const TlvSlot = TlvObject({
         /**
          * This field shall indicate the minimum time (in seconds) that the appliance expects to be in this slot for.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.1
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.1
          */
         minDuration: TlvField(0, TlvUInt32),
 
         /**
          * This field shall indicate the maximum time (in seconds) that the appliance expects to be in this slot for.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.2
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.2
          */
         maxDuration: TlvField(1, TlvUInt32),
 
         /**
          * This field shall indicate the expected time (in seconds) that the appliance expects to be in this slot for.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.3
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.3
          */
         defaultDuration: TlvField(2, TlvUInt32),
 
@@ -550,7 +596,7 @@ export namespace DeviceEnergyManagement {
          *
          * When the Forecast attribute is read, then this value shall be the most recent value.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.4
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.4
          */
         elapsedSlotTime: TlvField(3, TlvUInt32),
 
@@ -563,29 +609,34 @@ export namespace DeviceEnergyManagement {
          * When subscribed to, a change in this field value shall NOT cause the Forecast attribute to be updated, since
          * this value may change every 1 second.
          *
-         * Note that if the ESA is currently paused, then this value shall not change.
+         * Note that if the ESA is currently paused, then this value shall NOT change.
          *
          * When the Forecast attribute is read, then this value shall be the most recent value.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.5
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.5
          */
         remainingSlotTime: TlvField(4, TlvUInt32),
 
-        slotIsPauseable: TlvOptionalField(5, TlvBoolean),
+        /**
+         * This field shall indicate whether this slot can be paused.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.6
+         */
+        slotIsPausable: TlvOptionalField(5, TlvBoolean),
 
         /**
          * This field shall indicate the shortest period that the slot can be paused for. This can be set to avoid
          * controllers trying to pause ESAs for short periods and then resuming operation in a cyclic fashion which may
          * damage or cause excess energy to be consumed with restarting of an operation.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.7
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.7
          */
         minPauseDuration: TlvOptionalField(6, TlvUInt32),
 
         /**
          * This field shall indicate the longest period that the slot can be paused for.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.8
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.8
          */
         maxPauseDuration: TlvOptionalField(7, TlvUInt32),
 
@@ -605,11 +656,11 @@ export namespace DeviceEnergyManagement {
          * NOTE An ESA shall always use the same value to represent the same operating state.
          *
          * By providing this information a smart EMS may be able to learn the observed power draw when the ESA is put
-         * into a specific state. It can potentially then use the information in the PowerForecastReporting data to
-         * predict the power draw from the appliance and potentially ask it to modify its timing via one of the
-         * adjustment request commands, or adjust other ESAs power to compensate.
+         * into a specific state. It can potentially then use the ManufacturerESAState field in the Forecast attribute
+         * along with observed power drawn to predict the power draw from the appliance and potentially ask it to
+         * modify its timing via one of the adjustment request commands, or adjust other ESAs power to compensate.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.9
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.9
          */
         manufacturerEsaState: TlvOptionalField(8, TlvUInt16),
 
@@ -618,7 +669,7 @@ export namespace DeviceEnergyManagement {
          * considered the average value over the slot, and some variation from this would be expected (for example, as
          * it is ramping up).
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.10
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.10
          */
         nominalPower: TlvOptionalField(9, TlvInt64),
 
@@ -628,7 +679,7 @@ export namespace DeviceEnergyManagement {
          *
          * Some appliances (e.g. battery inverters which can charge and discharge) may have a negative power.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.11
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.11
          */
         minPower: TlvOptionalField(10, TlvInt64),
 
@@ -638,7 +689,7 @@ export namespace DeviceEnergyManagement {
          *
          * Some appliances (e.g. battery inverters which can charge and discharge) may have a negative power.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.12
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.12
          */
         maxPower: TlvOptionalField(11, TlvInt64),
 
@@ -647,7 +698,7 @@ export namespace DeviceEnergyManagement {
          *
          * Some appliances (e.g. battery inverters which can charge and discharge) may have a negative energy.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.13
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.13
          */
         nominalEnergy: TlvOptionalField(12, TlvInt64),
 
@@ -671,7 +722,7 @@ export namespace DeviceEnergyManagement {
          * If the ESA cannot calculate its cost for any reason (such as losing its connection to a Price server) it may
          * omit this field. This is treated as extra meta data that an EMS may use to optimize a system.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.14
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.14
          */
         costs: TlvOptionalField(13, TlvArray(TlvCost, { maxLength: 5 })),
 
@@ -682,7 +733,7 @@ export namespace DeviceEnergyManagement {
          * If the slot indicates a NominalPower of 0W (indicating it is expecting to be off), this allows an ESA to
          * indicate it could be switched on to charge, but this would be the minimum power limit it can be set to.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.15
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.15
          */
         minPowerAdjustment: TlvOptionalField(14, TlvInt64),
 
@@ -693,7 +744,7 @@ export namespace DeviceEnergyManagement {
          * the slot indicates a NominalPower of 0W (indicating it is expecting to be off), this allows an ESA to
          * indicate it could be switched on to charge, but this would be the maximum power limit it can be set to.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.16
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.16
          */
         maxPowerAdjustment: TlvOptionalField(15, TlvInt64),
 
@@ -706,7 +757,7 @@ export namespace DeviceEnergyManagement {
          *
          * For example, a heat pump compressor may have a minimum cycle time of order a few minutes.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.17
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.17
          */
         minDurationAdjustment: TlvOptionalField(16, TlvUInt32),
 
@@ -719,7 +770,7 @@ export namespace DeviceEnergyManagement {
          * which can be discharged, it may equally indicate the maximum time the battery could be discharged for (at
          * the MaxPowerAdjustment power level).
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11.18
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14.18
          */
         maxDurationAdjustment: TlvOptionalField(17, TlvUInt32)
     });
@@ -727,7 +778,7 @@ export namespace DeviceEnergyManagement {
     /**
      * This indicates a specific stage of an ESA’s operation.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.11
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.14
      */
     export interface Slot extends TypeFromSchema<typeof TlvSlot> {}
 
@@ -760,7 +811,7 @@ export namespace DeviceEnergyManagement {
      *
      * feature and instead report its internal state.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13
      */
     export const TlvForecast = TlvObject({
         /**
@@ -771,40 +822,39 @@ export namespace DeviceEnergyManagement {
          * previous subscriptions are lost if a device reboots. The loss of a subscription and subsequent
          * re-subscription allows the EMS to learn about any new forecasts.
          *
-         * The value of ForecastId is allowed to wrap.
+         * The value of ForecastID is allowed to wrap.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.1
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.1
          */
-        forecastId: TlvField(0, TlvUInt16),
+        forecastId: TlvField(0, TlvUInt32),
 
         /**
          * This field shall indicate which element of the Slots list is currently active in the Forecast sequence. A
          * null value indicates that the sequence has not yet started.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.2
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.2
          */
         activeSlotNumber: TlvField(1, TlvNullable(TlvUInt16)),
 
         /**
          * This field shall indicate the planned start time, in UTC, for the entire Forecast.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.3
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.3
          */
         startTime: TlvField(2, TlvEpochS),
 
         /**
          * This field shall indicate the planned end time, in UTC, for the entire Forecast.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.4
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.4
          */
         endTime: TlvField(3, TlvEpochS),
 
         /**
-         * This field shall indicate the earliest start time, in UTC, that the entire Forecast can be shifted to.
-         *
-         * A null value indicates that it can be started immediately.
+         * This field shall indicate the earliest start time, in UTC, that the entire Forecast can be shifted to. A
+         * null value indicates that it can be started immediately.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.5
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.5
          */
         earliestStartTime: TlvOptionalField(4, TlvNullable(TlvEpochS)),
 
@@ -814,7 +864,7 @@ export namespace DeviceEnergyManagement {
          * e.g. for an EVSE charging session, this may indicate the departure time for the vehicle, by which time the
          * charging session must end.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.6
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.6
          */
         latestEndTime: TlvOptionalField(5, TlvEpochS),
 
@@ -823,23 +873,23 @@ export namespace DeviceEnergyManagement {
          * this flag and if it is false, then none of the slots contain SlotIsPausable set to true. This can save a
          * client from having to check each slot in the list.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.7
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.7
          */
-        isPauseable: TlvField(6, TlvBoolean),
+        isPausable: TlvField(6, TlvBoolean),
 
         /**
          * This field shall contain a list of SlotStructs.
          *
          * It shall contain at least 1 entry, and a maximum of 10.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.8
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.8
          */
         slots: TlvField(7, TlvArray(TlvSlot, { maxLength: 10 })),
 
         /**
          * This field shall contain the reason the current Forecast was generated.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10.9
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.9
          */
         forecastUpdateReason: TlvField(8, TlvEnum<ForecastUpdateReason>())
     });
@@ -853,7 +903,7 @@ export namespace DeviceEnergyManagement {
      *
      * feature and instead report its internal state.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.10
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13
      */
     export interface Forecast extends TypeFromSchema<typeof TlvForecast> {}
 
@@ -969,7 +1019,7 @@ export namespace DeviceEnergyManagement {
     export interface StartTimeAdjustRequest extends TypeFromSchema<typeof TlvStartTimeAdjustRequest> {}
 
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.12
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.15
      */
     export const TlvSlotAdjustment = TlvObject({
         /**
@@ -977,30 +1027,33 @@ export namespace DeviceEnergyManagement {
          * be less than the actual length of the Slots list (implicitly it must be in the range 0 to 9 based on the
          * maximum length of the Slots list constraint).
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.12.1
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.15.1
          */
         slotIndex: TlvField(0, TlvUInt8),
 
         /**
          * This field shall indicate the new requested power that the ESA shall operate at. It MUST be between the
-         * MinPowerAdjustment and MaxPowerAdjustment for the slot as advertised by the ESA.
+         * AbsMinPower and AbsMaxPower attributes as advertised by the ESA if it supports PFR.
+         *
+         * This is a signed value and can be used to indicate charging or discharging. If the ESA does NOT support PFR
+         * this value shall be ignored by the ESA.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.12.2
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.15.2
          */
-        nominalPower: TlvField(1, TlvInt64),
+        nominalPower: TlvOptionalField(1, TlvInt64),
 
         /**
          * This field shall indicate the new requested duration, in seconds, that the ESA shall extend or shorten the
          * slot duration to. It MUST be between the MinDurationAdjustment and MaxDurationAdjustment for the slot as
          * advertised by the ESA.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.12.3
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.15.3
          */
         duration: TlvField(2, TlvUInt32)
     });
 
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.12
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.15
      */
     export interface SlotAdjustment extends TypeFromSchema<typeof TlvSlotAdjustment> {}
 
@@ -1011,7 +1064,7 @@ export namespace DeviceEnergyManagement {
      */
     export const TlvModifyForecastRequest = TlvObject({
         /**
-         * This field shall indicate the ForecastId that is to be modified.
+         * This field shall indicate the ForecastID that is to be modified.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.2.9.6.1
          */
@@ -1019,7 +1072,7 @@ export namespace DeviceEnergyManagement {
 
         /**
          * This field shall contain a list of SlotAdjustment parameters that should be modified in the corresponding
-         * Forecast with matching ForecastId.
+         * Forecast with matching ForecastID.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.2.9.6.2
          */
@@ -1045,7 +1098,7 @@ export namespace DeviceEnergyManagement {
      * perhaps excess solar PV). The format allows the client to suggest that the ESA can either turn up its energy
      * consumption, or turn down its energy consumption during this period.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.16
      */
     export const TlvConstraints = TlvObject({
         /**
@@ -1054,26 +1107,25 @@ export namespace DeviceEnergyManagement {
          *
          * This value is in UTC and MUST be in the future.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.1
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.16.1
          */
         startTime: TlvField(0, TlvEpochS),
 
         /**
          * This field shall indicate the duration of the constraint in seconds.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.2
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.16.2
          */
-        duration: TlvField(1, TlvUInt32.bound({ min: 0, max: 86400 })),
+        duration: TlvField(1, TlvUInt32.bound({ max: 86400 })),
 
         /**
          * This field shall indicate the nominal power that client wishes the ESA to operate at during the constrained
          * period. It MUST be between the AbsMinPower and AbsMaxPower attributes as advertised by the ESA if it
          * supports PFR.
          *
-         * This is a signed value and can be used to indicate charging or discharging. If the ESA does NOT support PFR
-         * this value shall be ignored by the ESA.
+         * This is a signed value and can be used to indicate charging or discharging.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.3
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.16.3
          */
         nominalPower: TlvOptionalField(2, TlvInt64),
 
@@ -1081,10 +1133,9 @@ export namespace DeviceEnergyManagement {
          * This field shall indicate the maximum energy that can be transferred to or from the ESA during the
          * constraint period.
          *
-         * This is a signed value and can be used to indicate charging or discharging. If the ESA does NOT support PFR
-         * this value may be ignored by the ESA.
+         * This is a signed value and can be used to indicate charging or discharging.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.4
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.16.4
          */
         maximumEnergy: TlvOptionalField(3, TlvInt64),
 
@@ -1098,7 +1149,7 @@ export namespace DeviceEnergyManagement {
          *
          * Note that the mapping between values and operation is manufacturer specific.
          *
-         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13.5
+         * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.16.5
          */
         loadControl: TlvOptionalField(4, TlvInt8)
     });
@@ -1108,7 +1159,7 @@ export namespace DeviceEnergyManagement {
      * perhaps excess solar PV). The format allows the client to suggest that the ESA can either turn up its energy
      * consumption, or turn down its energy consumption during this period.
      *
-     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.13
+     * @see {@link MatterSpecification.v13.Cluster} § 9.2.7.16
      */
     export interface Constraints extends TypeFromSchema<typeof TlvConstraints> {}
 
@@ -1120,7 +1171,8 @@ export namespace DeviceEnergyManagement {
     export const TlvRequestConstraintBasedForecastRequest = TlvObject({
         /**
          * This field shall indicate the series of turn up or turn down power requests that the ESA is being asked to
-         * constrain its operation within.
+         * constrain its operation within. These requests shall be in the future, shall be in chronological order,
+         * starting with the earliest start time, and shall NOT overlap in time.
          *
          * For example, a grid event which requires devices to reduce power (turn down) between 4pm and 6pm and due to
          * excess power on the grid overnight, may request ESAs to increase their power demand (turn up) between
@@ -1129,8 +1181,9 @@ export namespace DeviceEnergyManagement {
          * If this ESA supports PFR this would have 2 entries in the list as follows:
          *
          * If this ESA supports SFR where it does not know the actual power, but has an understanding of the functions
-         * that use more energy, it could be requested to use more or less energy using the LoadControl field as
-         * follows:
+         * that use more energy, it could be requested to use more or less energy using the LoadCon
+         *
+         * trol field as follows:
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.2.9.7.1
          */
@@ -1267,29 +1320,23 @@ export namespace DeviceEnergyManagement {
     export const PowerAdjustmentComponent = MutableCluster.Component({
         attributes: {
             /**
-             * Indicates how the ESA can be adjusted at the current time. This attribute SHOULD be updated regularly by
-             * ESAs.
+             * Indicates how the ESA can be adjusted at the current time, and the state of any active adjustment.
              *
-             * For example, a battery storage inverter may need to regulate its internal temperature, or the charging
-             * rate of the battery may be limited due to cold temperatures, or a change in the state of charge of the
-             * battery may mean that the maximum charging or discharging rate is limited.
+             * A null value indicates that no power adjustment is currently possible, and nor is any adjustment
+             * currently active.
              *
-             * An empty list shall indicate that no power adjustment is currently possible.
+             * This attribute SHOULD be updated periodically by ESAs to reflect any changes in internal state, for
+             * example temperature or stored energy, which would affect the power or duration limits.
              *
-             * Multiple entries in the list allow to indicate that permutations of scenarios may be possible.
+             * Changes to this attribute shall only be marked as reportable in the following cases:
              *
-             * For example, a 10kWh battery could be at 80% state of charge. If charging at 2kW, then it would be full
-             * in 1 hour. However, it could be discharged at 2kW for 4 hours.
+             *   • At most once every 10 seconds on changes, or
              *
-             * In this example the list of PowerAdjustStructs allows multiple scenarios to be offered as follows:
+             *   • When it changes from null to any other value and vice versa.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.2.8.6
              */
-            powerAdjustmentCapability: Attribute(
-                0x5,
-                TlvNullable(TlvArray(TlvPowerAdjust, { maxLength: 8 })),
-                { default: null }
-            )
+            powerAdjustmentCapability: Attribute(0x5, TlvNullable(TlvPowerAdjustCapability), { default: null })
         },
 
         commands: {
@@ -1335,13 +1382,23 @@ export namespace DeviceEnergyManagement {
              * This attribute allows an ESA to share its intended forecast with a client (such as an Energy Management
              * System).
              *
-             * A null value indicates that there is no forecast currently available
-             *
-             * yet been selected by the user).
+             * A null value indicates that there is no forecast currently available (for example, a program has not yet
+             * been selected by the user).
              *
              * A server may reset this value attribute to null on a reboot, and it does not need to persist any
              * previous forecasts.
              *
+             * Changes to this attribute shall only be marked as reportable in the following cases:
+             *
+             *   • At most once every 10 seconds on changes, or
+             *
+             *   • When it changes from null to any other value and vice versa, or
+             *
+             *   • As a result of a command which causes the forecast to be updated, or
+             *
+             *   • As a result of a change in the opt-out status which in turn may cause the ESA to recalculate its
+             *     forecast.
+             *
              * @see {@link MatterSpecification.v13.Cluster} § 9.2.8.7
              */
             forecast: Attribute(0x6, TlvNullable(TlvForecast), { default: null })
@@ -1363,8 +1420,29 @@ export namespace DeviceEnergyManagement {
              * optimization reasons, it shall reject any commands which have the AdjustmentCauseEnum value
              * LocalOptimization. If the ESA is in the GridOptOut or OptOut states, so it cannot be controlled by an
              * EMS for grid optimization reasons, it shall reject any commands which have the AdjustmentCauseEnum value
-             * GridOptimization. If the ESA is in the LocalOptOut, GridOptOut, or NoOptOut states, the device is still
-             * permitted to optimize its own energy usage, for example, using tariff information it may obtain.
+             * GridOptimization.
+             *
+             * If the user changes the Opt-Out state of the ESA which is currently operating with a Forecast that is
+             * due to a previous StartTimeAdjustRequest, ModifyForecastRequest or RequestConstraintBasedForecast
+             * command that would now not be permitted due to the new Opt-out state
+             *
+             * attribute ForecastUpdateReason field currently contains a reason which is now opted out), the ESA shall
+             * behave as if it had received a CancelRequest command.
+             *
+             * If the user changes the Opt-Out state of the ESA which currently has the ESAStateEnum with value Paused
+             * due to a previous PauseRequest command that would now not be permitted due to the new Opt-out state, and
+             * the ESA supports the PFR or SFR features (i.e. the Forecast attribute ForecastUpdateReason field
+             * currently contains a reason which is now opted out), the ESA shall behave as if it had received a
+             * ResumeRequest command.
+             *
+             * If the user changes the Opt-Out state of the ESA which currently has the ESAStateEnum with value
+             * PowerAdjustActive due to a previous PowerAdjustRequest command that would now not be permitted due to
+             * the new Opt-out state (i.e. the Forecast attribute ForecastUpdateReason field currently contains a
+             * reason which is now opted out), the ESA shall behave as if it had received a CancelPowerAdjustRequest
+             * command.
+             *
+             * If the ESA is in the LocalOptOut, GridOptOut, or NoOptOut states, the device is still permitted to
+             * optimize its own energy usage, for example, using tariff information it may obtain.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.2.8.8
              */
@@ -1474,7 +1552,7 @@ export namespace DeviceEnergyManagement {
     export const Base = MutableCluster.Component({
         id: 0x98,
         name: "DeviceEnergyManagement",
-        revision: 3,
+        revision: 4,
 
         features: {
             /**
@@ -1485,14 +1563,15 @@ export namespace DeviceEnergyManagement {
              * be to curtail power requirements during peak periods, but can also be used to turn on an ESA if there is
              * excess renewable or local generation (Solar PV).
              *
-             * For example, a home may have solar PV which often produces more power than the home requires,
-             *
-             * resulting in the excess power flowing into the grid. This excess power naturally fluctuates when clouds
-             * pass overhead and other loads in the home are switched on and off.
+             * For example, a home may have solar PV which often produces more power than the home requires, resulting
+             * in the excess power flowing into the grid. This excess power naturally fluctuates when clouds pass
+             * overhead and other loads in the home are switched on and off.
              *
              * EVSE Example: An EMS may therefore be able to turn on the EVSE (if the vehicle is plugged in) and can
              * start charging the vehicle, and periodically modify the charging power depending on PV generation and
-             * other home loads, so as to minimize import and export to the grid.
+             * other home loads, so as to minimize import and export to the grid. An EMS may also use this feature to
+             * control the discharging (and re-charging) of the vehicle if the EVSE and vehicle support the V2X feature
+             * of the EVSE cluster of the associated EVSE device.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.2.4.1
              */
@@ -1592,8 +1671,9 @@ export namespace DeviceEnergyManagement {
             /**
              * Pausable
              *
-             * ESAs which support the Pausable feature, allow an EMS to recommend a pause in the middle of a forecast
-             * power profile that the ESA is currently using.
+             * ESAs which support the Pausable feature, allow an EMS to recommend a pause in the middle of a
+             *
+             * forecast power profile that the ESA is currently using.
              *
              * Washing machine example: A Washing Machine is in operation, and starting its water heating step.
              *
@@ -1651,8 +1731,9 @@ export namespace DeviceEnergyManagement {
              *
              * ESAs which support the Constraint-Based Adjustment feature allow an EMS to inform the ESA of periods
              * during which power usage should be modified (for example when the EMS has been made aware that the grid
-             * supplier has requested reduced energy usage due to overall peak grid demand) and may cause the ESA to
-             * modify the intended power profile has previously suggested it would use.
+             * supplier has requested reduced energy usage due to overall peak grid demand)
+             *
+             * and may cause the ESA to modify the intended power profile has previously suggested it would use.
              *
              * EVSE example: An EVSE scheduling system may have determined that the vehicle would be charged starting
              * at a moderate rate at 1am, so that it has enough charge by the time it is needed later that morning.
@@ -1660,9 +1741,8 @@ export namespace DeviceEnergyManagement {
              * However, the DSR service provider has informed the EMS that due to high forecast winds it is now
              * forecast that there will be very cheap energy available from wind generation between 2am and 3am.
              *
-             * The EMS first requests the Forecast data from each of its registered ESAs. It determines that the
-             *
-             * EVSE has a power profile suggesting it plans to start charging the vehicle at 1am.
+             * The EMS first requests the Forecast data from each of its registered ESAs. It determines that the EVSE
+             * has a power profile suggesting it plans to start charging the vehicle at 1am.
              *
              * The EMS can then try to reduce the cost of charging the EV by informing the EVSE of the desire to
              * increase the charging between scheduled times.
@@ -1700,17 +1780,17 @@ export namespace DeviceEnergyManagement {
              * the power values reported by the ESA need to have their sign inverted when dealing with forecasts and
              * adjustments.
              *
-             * For example, a solar PV inverter (being a generator) may produce positive values to indicate generation,
-             * however an EMS when predicting the total home load would need to subtract these positive values from the
-             * loads to compute a net import at the grid meter.
+             * For example, a solar PV inverter (being a generator) may produce negative values to indicate generation
+             * (since power is flowing out of the node into the home), however a display showing the power to the
+             * consumers may need to present a positive solar production value to the consumer.
              *
              * For example, a home battery storage system (BESS) which needs to charge the battery and then discharge
              * to the home loads, would be classed as a generator. These types of devices shall have this field set to
              * true. When generating its forecast or advertising its PowerAdjustmentCapability, the power values shall
-             * be positive to indicate discharging to the loads in the home, and negative to indicate when it is
+             * be negative to indicate discharging to the loads in the home, and positive to indicate when it is
              * charging its battery.
              *
-             * GRID meter = Σ LoadPowers - Σ GeneratorPowers
+             * GRID meter = Σ LoadPowers + Σ GeneratorPowers
              *
              * Example:
              *
@@ -1737,9 +1817,11 @@ export namespace DeviceEnergyManagement {
              * Indicates the minimum electrical power that the ESA can consume when switched on. This does not include
              * when in power save or standby modes.
              *
-             * Note that for Generator ESAs that can charge an internal battery (such as a battery storage inverter),
-             * the AbsMinPower will be a negative number representing the maximum power that the ESA can charge its
-             * internal battery.
+             * NOTE
+             *
+             * For Generator ESAs that can discharge an internal battery (such as a battery storage inverter) to loads
+             * in the home, the AbsMinPower will be a negative number representing the maximum power that the ESA can
+             * discharge its internal battery.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.2.8.4
              */
@@ -1748,16 +1830,12 @@ export namespace DeviceEnergyManagement {
             /**
              * Indicates the maximum electrical power that the ESA can consume when switched on.
              *
-             * The value of the AbsMaxPower attribute shall be limited
-             *
-             * AbsMaxPower >= AbsMinPower
-             *
-             * Note that for Generator ESAs that can discharge a battery to loads in the home (such as a battery
-             * storage inverter), the AbsMaxPower will be a positive number representing the maximum power at which the
-             * ESA can discharge its internal battery.
+             * Note that for Generator ESAs that can charge a battery by importing power into the node (such as a
+             * battery storage inverter), the AbsMaxPower will be a positive number representing the maximum power at
+             * which the ESA can charge its internal battery.
              *
              * For example, a battery storage inverter that can charge its battery at a maximum power of 2000W and can
-             * discharge the battery at a maximum power of 3000W, would have a AbsMinPower: -2000, AbsMaxPower: 3000W.
+             * discharge the battery at a maximum power of 3000W, would have a AbsMinPower: -3000, AbsMaxPower: 2000W.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.2.8.5
              */
@@ -1814,34 +1892,9 @@ export namespace DeviceEnergyManagement {
                 flags: { constraintBasedAdjustment: true },
                 component: StartTimeAdjustmentOrForecastAdjustmentOrConstraintBasedAdjustmentComponent
             },
-            { flags: { feature: false, startTimeAdjustment: true, stateForecastReporting: false }, component: false },
-            { flags: { feature: false, pausable: true, stateForecastReporting: false }, component: false },
-            { flags: { feature: false, forecastAdjustment: true, stateForecastReporting: false }, component: false },
-            {
-                flags: { feature: false, constraintBasedAdjustment: true, stateForecastReporting: false },
-                component: false
-            },
-            { flags: { feature: false, startTimeAdjustment: true, powerForecastReporting: false }, component: false },
-            { flags: { feature: false, pausable: true, powerForecastReporting: false }, component: false },
-            { flags: { feature: false, forecastAdjustment: true, powerForecastReporting: false }, component: false },
-            {
-                flags: { feature: false, constraintBasedAdjustment: true, powerForecastReporting: false },
-                component: false
-            },
-
-            {
-                flags: {
-                    powerAdjustment: false,
-                    powerForecastReporting: false,
-                    stateForecastReporting: false,
-                    startTimeAdjustment: false,
-                    pausable: false,
-                    forecastAdjustment: false,
-                    constraintBasedAdjustment: false
-                },
-
-                component: false
-            }
+            { flags: { staTrue: true, pauTrue: false, faTrue: false, conTrue: false }, component: false },
+            { flags: { powerForecastReporting: true, stateForecastReporting: true }, component: false },
+            { flags: { powerForecastReporting: false, stateForecastReporting: false }, component: false }
         )
     });
 
@@ -1851,12 +1904,14 @@ export namespace DeviceEnergyManagement {
     export const ClusterInstance = MutableCluster.ExtensibleOnly(Base);
 
     /**
-     * This cluster allows a client to manage the power draw of a device. An example of such a client could be an
-     * Energy Management System (EMS) which controls an Energy Smart Appliance (ESA).
+     * This cluster allows a client to manage the power draw of a device. An example of such a client could
+     *
+     * be an Energy Management System (EMS) which controls an Energy Smart Appliance (ESA).
      *
-     * In most deployments the EMS will be the client, and the ESA will host the Energy Management Cluster server.
+     * In most deployments the EMS will be the client, and the ESA will host the Device Energy Management Cluster
+     * server.
      *
-     * Figure 15. Example of the how an EMS is a client of multiple ESAs Energy Management clusters.
+     * Figure 17. Example of the how an EMS is a client of multiple ESAs Device Energy Management clusters.
      *
      * This cluster is intended to be generic in nature and could apply to any electrical load or generator (e.g. a
      * Battery Electric Storage System - BESS, solar PV inverter, EVSE, HVAC, heat pump, hot water heater, white goods
@@ -1884,7 +1939,7 @@ export namespace DeviceEnergyManagement {
      * intensity', 'time of use' or 'type of use' tariffs to schedule its operation to run at the cheapest and greenest
      * times.
      *
-     * Figure 16. Example of the how an HVAC may use multiple clusters
+     * Figure 18. Example of the how an HVAC may use multiple clusters
      *
      * NOTE
      *
@@ -1896,8 +1951,6 @@ export namespace DeviceEnergyManagement {
      * Different markets may follow different approaches, but the UK [PAS1878] and [EUCodeOfConduct] give examples of
      * how ESAs may be mandated to support these features in the future.
      *
-     * NOTE Support of Device Energy Management Cluster is provisional.
-     *
      * Per the Matter specification you cannot use {@link DeviceEnergyManagementCluster} without enabling certain
      * feature combinations. You must use the {@link with} factory method to obtain a working cluster.
      *