@matter/types 0.13.1-alpha.0-20250508-047aa0277 → 0.13.1-alpha.0-20250511-74ef153aa

package/dist/esm/clusters/device-energy-management.d.ts

@@ -28,12 +28,6 @@ export declare namespace DeviceEnergyManagement {
          * 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. 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.v14.Cluster} § 9.2.4.1
          */
         PowerAdjustment = "PowerAdjustment",
@@ -48,10 +42,6 @@ export declare namespace DeviceEnergyManagement {
          * Forecasts are defined from a current time, using a slot format, where the slot is akin to a relatively
          * constant operating mode.
          *
-         * Washing machine example: a washing machine may have stages of a washing cycle: heating, tumbling, rinse and
-         * spin stages. At each stage, the approximate minimum and maximum power consumption may be known, as well as
-         * the duration of that stage.
-         *
          * In some circumstances the ESA may allow the stage to be delayed or paused (subject to safety and
          * manufacturer’s discretion and user preferences).
          *
@@ -66,8 +56,6 @@ export declare namespace DeviceEnergyManagement {
          *
          * The PowerForecastReporting and the adjustment features aim to align to the [SAREF4ENER] ontology.
          *
-         * Inverter driven ESAs: some inverter driven ESAs can consume or generate a variable amount of power.
-         *
          * For example, a single phase EVSE can be adjusted in the range of 6-32Amps in 0.6 Amp steps in EU or on a
          * hardwired 120V supply in the range of 6-15 Amps in US.
          *
@@ -105,9 +93,6 @@ export declare namespace DeviceEnergyManagement {
          * ESAs which support the Start Time Adjustment feature, allow an EMS to recommend a change to the start time of
          * the energy transfer that the ESA has previously suggested it would use.
          *
-         * Washing machine example: A Washing Machine may have been set to start a wash cycle at 9pm when the variable
-         * tariff normally reduces.
-         *
          * However, the EMS is aware that a grid event has occurred, making it cheaper to run the cycle at a later time,
          * but the washing machine is not aware of this.
          *
@@ -126,11 +111,8 @@ export declare 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.
-         *
-         * Washing machine example: A Washing Machine is in operation, and starting its water heating step.
+         * 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.
          *
          * However, the EMS becomes aware from the smart meter that the total home load on the grid is close to
          * exceeding its allowed total grid load.
@@ -155,10 +137,6 @@ export declare namespace DeviceEnergyManagement {
          * and/or power level limits of the steps of the power profile that the ESA has previously suggested it would
          * use.
          *
-         * Heat pump and Solar PV example: A heat pump may have the ability to heat hot water as well as heating the
-         * home. The heat pump scheduling system may have determined that the home will be unoccupied during the day, or
-         * that the indoor temperature is above the set-point and so it knows that it will not need to heat the home.
-         *
          * However, the hot water tank is likely to need to be reheated before the homeowner comes home in the evening.
          * The heat pump is not aware that the property also has a solar PV inverter which is also an ESA that is
          * communicating with the EMS.
@@ -182,12 +160,8 @@ export declare 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.
-         *
-         * 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.
+         * 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.
          *
          * 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.
@@ -213,8 +187,9 @@ export declare namespace DeviceEnergyManagement {
         /**
          * 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 out of the node (e.g. discharging a
-         * battery).
+         * Note that this is a signed value. Negative values indicate power flows out of the node
+         *
+         * discharging a battery).
          *
          * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.10.1
          */
@@ -303,8 +278,9 @@ export declare namespace DeviceEnergyManagement {
             /**
              * 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 out of the node (e.g. discharging a
-             * battery).
+             * Note that this is a signed value. Negative values indicate power flows out of the node
+             *
+             * discharging a battery).
              *
              * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.10.1
              */
@@ -641,8 +617,6 @@ export declare namespace DeviceEnergyManagement {
          * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
          * Enum states meaning heating with fan, heating without fan etc.
          *
-         * 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 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
@@ -814,9 +788,8 @@ export declare namespace DeviceEnergyManagement {
      * different power and energy demands per slot. For example, slots might be used to describe the distinct stages of
      * a washing machine cycle.
      *
-     * Where an ESA does not know the actual power and energy use of the system, it may support the SFR
-     *
-     * feature and instead report its internal state.
+     * Where an ESA does not know the actual power and energy use of the system, it may support the SFR feature and
+     * instead report its internal state.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.13
      */
@@ -965,8 +938,6 @@ export declare namespace DeviceEnergyManagement {
              * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
              * Enum states meaning heating with fan, heating without fan etc.
              *
-             * 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 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
@@ -1121,9 +1092,8 @@ export declare namespace DeviceEnergyManagement {
      * different power and energy demands per slot. For example, slots might be used to describe the distinct stages of
      * a washing machine cycle.
      *
-     * Where an ESA does not know the actual power and energy use of the system, it may support the SFR
-     *
-     * feature and instead report its internal state.
+     * Where an ESA does not know the actual power and energy use of the system, it may support the SFR feature and
+     * instead report its internal state.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.13
      */
@@ -1410,9 +1380,8 @@ export declare 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 LoadCon
-         *
-         * trol field as follows:
+         * that use more energy, it could be requested to use more or less energy using the LoadControl field as
+         * follows:
          *
          * @see {@link MatterSpecification.v14.Cluster} § 9.2.9.7.1
          */
@@ -1549,7 +1518,7 @@ export declare namespace DeviceEnergyManagement {
      */
     enum EsaState {
         /**
-         * The ESA is not available to the EMS (e.g. start- up, maintenance mode)
+         * The ESA is not available to the EMS (e.g. start-up, maintenance mode)
          */
         Offline = 0,
         /**
@@ -1614,8 +1583,9 @@ export declare namespace DeviceEnergyManagement {
                     /**
                      * 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 out of the node (e.g. discharging a
-                     * battery).
+                     * Note that this is a signed value. Negative values indicate power flows out of the node
+                     *
+                     * discharging a battery).
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.10.1
                      */
@@ -1910,8 +1880,6 @@ export declare namespace DeviceEnergyManagement {
                      * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
                      * Enum states meaning heating with fan, heating without fan etc.
                      *
-                     * 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 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
@@ -2082,10 +2050,9 @@ export declare namespace DeviceEnergyManagement {
              *
              * 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.
+             * 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 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
@@ -2278,9 +2245,8 @@ export declare 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 LoadCon
-                 *
-                 * trol field as follows:
+                 * that use more energy, it could be requested to use more or less energy using the LoadControl field as
+                 * follows:
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 9.2.9.7.1
                  */
@@ -2377,12 +2343,6 @@ export declare namespace DeviceEnergyManagement {
              * 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. 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.v14.Cluster} § 9.2.4.1
              */
             readonly powerAdjustment: BitFlag;
@@ -2397,10 +2357,6 @@ export declare namespace DeviceEnergyManagement {
              * Forecasts are defined from a current time, using a slot format, where the slot is akin to a relatively
              * constant operating mode.
              *
-             * Washing machine example: a washing machine may have stages of a washing cycle: heating, tumbling, rinse
-             * and spin stages. At each stage, the approximate minimum and maximum power consumption may be known, as
-             * well as the duration of that stage.
-             *
              * In some circumstances the ESA may allow the stage to be delayed or paused (subject to safety and
              * manufacturer’s discretion and user preferences).
              *
@@ -2415,8 +2371,6 @@ export declare namespace DeviceEnergyManagement {
              *
              * The PowerForecastReporting and the adjustment features aim to align to the [SAREF4ENER] ontology.
              *
-             * Inverter driven ESAs: some inverter driven ESAs can consume or generate a variable amount of power.
-             *
              * For example, a single phase EVSE can be adjusted in the range of 6-32Amps in 0.6 Amp steps in EU or on a
              * hardwired 120V supply in the range of 6-15 Amps in US.
              *
@@ -2455,9 +2409,6 @@ export declare namespace DeviceEnergyManagement {
              * ESAs which support the Start Time Adjustment feature, allow an EMS to recommend a change to the start
              * time of the energy transfer that the ESA has previously suggested it would use.
              *
-             * Washing machine example: A Washing Machine may have been set to start a wash cycle at 9pm when the
-             * variable tariff normally reduces.
-             *
              * However, the EMS is aware that a grid event has occurred, making it cheaper to run the cycle at a later
              * time, but the washing machine is not aware of this.
              *
@@ -2477,11 +2428,8 @@ export declare 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.
-             *
-             * Washing machine example: A Washing Machine is in operation, and starting its water heating step.
+             * 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.
              *
              * However, the EMS becomes aware from the smart meter that the total home load on the grid is close to
              * exceeding its allowed total grid load.
@@ -2506,11 +2454,6 @@ export declare namespace DeviceEnergyManagement {
              * duration and/or power level limits of the steps of the power profile that the ESA has previously
              * suggested it would use.
              *
-             * Heat pump and Solar PV example: A heat pump may have the ability to heat hot water as well as heating the
-             * home. The heat pump scheduling system may have determined that the home will be unoccupied during the
-             * day, or that the indoor temperature is above the set-point and so it knows that it will not need to heat
-             * the home.
-             *
              * However, the hot water tank is likely to need to be reheated before the homeowner comes home in the
              * evening. The heat pump is not aware that the property also has a solar PV inverter which is also an ESA
              * that is communicating with the EMS.
@@ -2535,12 +2478,8 @@ export declare 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.
-             *
-             * 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.
+             * 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.
              *
              * 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.
@@ -2617,11 +2556,11 @@ export declare 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
+             * > [!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.
+             * > 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.v14.Cluster} § 9.2.8.4
              */
@@ -2690,8 +2629,9 @@ export declare namespace DeviceEnergyManagement {
                             /**
                              * 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 out of the node (e.g. discharging a
-                             * battery).
+                             * Note that this is a signed value. Negative values indicate power flows out of the node
+                             *
+                             * discharging a battery).
                              *
                              * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.10.1
                              */
@@ -2986,8 +2926,6 @@ export declare namespace DeviceEnergyManagement {
                              * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
                              * Enum states meaning heating with fan, heating without fan etc.
                              *
-                             * 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 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
@@ -3313,8 +3251,6 @@ export declare namespace DeviceEnergyManagement {
                              * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
                              * Enum states meaning heating with fan, heating without fan etc.
                              *
-                             * 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 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
@@ -3485,10 +3421,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -3528,10 +3463,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -3571,10 +3505,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -3614,10 +3547,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -3657,10 +3589,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -3857,9 +3788,8 @@ export declare 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 LoadCon
-                         *
-                         * trol field as follows:
+                         * that use more energy, it could be requested to use more or less energy using the LoadControl field as
+                         * follows:
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 9.2.9.7.1
                          */
@@ -4008,12 +3938,6 @@ export declare namespace DeviceEnergyManagement {
              * 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. 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.v14.Cluster} § 9.2.4.1
              */
             readonly powerAdjustment: BitFlag;
@@ -4028,10 +3952,6 @@ export declare namespace DeviceEnergyManagement {
              * Forecasts are defined from a current time, using a slot format, where the slot is akin to a relatively
              * constant operating mode.
              *
-             * Washing machine example: a washing machine may have stages of a washing cycle: heating, tumbling, rinse
-             * and spin stages. At each stage, the approximate minimum and maximum power consumption may be known, as
-             * well as the duration of that stage.
-             *
              * In some circumstances the ESA may allow the stage to be delayed or paused (subject to safety and
              * manufacturer’s discretion and user preferences).
              *
@@ -4046,8 +3966,6 @@ export declare namespace DeviceEnergyManagement {
              *
              * The PowerForecastReporting and the adjustment features aim to align to the [SAREF4ENER] ontology.
              *
-             * Inverter driven ESAs: some inverter driven ESAs can consume or generate a variable amount of power.
-             *
              * For example, a single phase EVSE can be adjusted in the range of 6-32Amps in 0.6 Amp steps in EU or on a
              * hardwired 120V supply in the range of 6-15 Amps in US.
              *
@@ -4086,9 +4004,6 @@ export declare namespace DeviceEnergyManagement {
              * ESAs which support the Start Time Adjustment feature, allow an EMS to recommend a change to the start
              * time of the energy transfer that the ESA has previously suggested it would use.
              *
-             * Washing machine example: A Washing Machine may have been set to start a wash cycle at 9pm when the
-             * variable tariff normally reduces.
-             *
              * However, the EMS is aware that a grid event has occurred, making it cheaper to run the cycle at a later
              * time, but the washing machine is not aware of this.
              *
@@ -4108,11 +4023,8 @@ export declare 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.
-             *
-             * Washing machine example: A Washing Machine is in operation, and starting its water heating step.
+             * 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.
              *
              * However, the EMS becomes aware from the smart meter that the total home load on the grid is close to
              * exceeding its allowed total grid load.
@@ -4137,11 +4049,6 @@ export declare namespace DeviceEnergyManagement {
              * duration and/or power level limits of the steps of the power profile that the ESA has previously
              * suggested it would use.
              *
-             * Heat pump and Solar PV example: A heat pump may have the ability to heat hot water as well as heating the
-             * home. The heat pump scheduling system may have determined that the home will be unoccupied during the
-             * day, or that the indoor temperature is above the set-point and so it knows that it will not need to heat
-             * the home.
-             *
              * However, the hot water tank is likely to need to be reheated before the homeowner comes home in the
              * evening. The heat pump is not aware that the property also has a solar PV inverter which is also an ESA
              * that is communicating with the EMS.
@@ -4166,12 +4073,8 @@ export declare 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.
-             *
-             * 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.
+             * 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.
              *
              * 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.
@@ -4248,11 +4151,11 @@ export declare 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
+             * > [!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.
+             * > 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.v14.Cluster} § 9.2.8.4
              */
@@ -4321,8 +4224,9 @@ export declare namespace DeviceEnergyManagement {
                             /**
                              * 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 out of the node (e.g. discharging a
-                             * battery).
+                             * Note that this is a signed value. Negative values indicate power flows out of the node
+                             *
+                             * discharging a battery).
                              *
                              * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.10.1
                              */
@@ -4617,8 +4521,6 @@ export declare namespace DeviceEnergyManagement {
                              * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
                              * Enum states meaning heating with fan, heating without fan etc.
                              *
-                             * 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 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
@@ -4944,8 +4846,6 @@ export declare namespace DeviceEnergyManagement {
                              * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
                              * Enum states meaning heating with fan, heating without fan etc.
                              *
-                             * 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 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
@@ -5116,10 +5016,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -5159,10 +5058,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -5202,10 +5100,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -5245,10 +5142,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -5288,10 +5184,9 @@ export declare namespace DeviceEnergyManagement {
                      *
                      * 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.
+                     * 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 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
@@ -5488,9 +5383,8 @@ export declare 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 LoadCon
-                         *
-                         * trol field as follows:
+                         * that use more energy, it could be requested to use more or less energy using the LoadControl field as
+                         * follows:
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 9.2.9.7.1
                          */
@@ -5620,15 +5514,12 @@ export declare namespace DeviceEnergyManagement {
         }];
     }>;
     /**
-     * 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 Device Energy Management Cluster
      * server.
      *
-     * 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
      * appliances etc).
@@ -5655,17 +5546,15 @@ export declare namespace DeviceEnergyManagement {
      * intensity', 'time of use' or 'type of use' tariffs to schedule its operation to run at the cheapest and greenest
      * times.
      *
-     * Figure 18. Example of the how an HVAC may use multiple clusters
+     * > [!NOTE]
      *
-     * NOTE
+     * > Grid Services are market dependent and will use other protocols ([OpenADR] / [IEEE2030.5]) to communicate grid
+     *   events to the EMS. These are outside the scope of Matter.
      *
-     * Grid Services are market dependent and will use other protocols ([OpenADR] / [IEEE2030.5]) to communicate grid
-     * events to the EMS. These are outside the scope of Matter.
+     * > [!NOTE]
      *
-     * NOTE
-     *
-     * 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.
+     * > 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.
      *
      * 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.
@@ -5695,12 +5584,6 @@ export declare namespace DeviceEnergyManagement {
              * 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. 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.v14.Cluster} § 9.2.4.1
              */
             readonly powerAdjustment: BitFlag;
@@ -5715,10 +5598,6 @@ export declare namespace DeviceEnergyManagement {
              * Forecasts are defined from a current time, using a slot format, where the slot is akin to a relatively
              * constant operating mode.
              *
-             * Washing machine example: a washing machine may have stages of a washing cycle: heating, tumbling, rinse
-             * and spin stages. At each stage, the approximate minimum and maximum power consumption may be known, as
-             * well as the duration of that stage.
-             *
              * In some circumstances the ESA may allow the stage to be delayed or paused (subject to safety and
              * manufacturer’s discretion and user preferences).
              *
@@ -5733,8 +5612,6 @@ export declare namespace DeviceEnergyManagement {
              *
              * The PowerForecastReporting and the adjustment features aim to align to the [SAREF4ENER] ontology.
              *
-             * Inverter driven ESAs: some inverter driven ESAs can consume or generate a variable amount of power.
-             *
              * For example, a single phase EVSE can be adjusted in the range of 6-32Amps in 0.6 Amp steps in EU or on a
              * hardwired 120V supply in the range of 6-15 Amps in US.
              *
@@ -5773,9 +5650,6 @@ export declare namespace DeviceEnergyManagement {
              * ESAs which support the Start Time Adjustment feature, allow an EMS to recommend a change to the start
              * time of the energy transfer that the ESA has previously suggested it would use.
              *
-             * Washing machine example: A Washing Machine may have been set to start a wash cycle at 9pm when the
-             * variable tariff normally reduces.
-             *
              * However, the EMS is aware that a grid event has occurred, making it cheaper to run the cycle at a later
              * time, but the washing machine is not aware of this.
              *
@@ -5795,11 +5669,8 @@ export declare 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.
-             *
-             * Washing machine example: A Washing Machine is in operation, and starting its water heating step.
+             * 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.
              *
              * However, the EMS becomes aware from the smart meter that the total home load on the grid is close to
              * exceeding its allowed total grid load.
@@ -5824,11 +5695,6 @@ export declare namespace DeviceEnergyManagement {
              * duration and/or power level limits of the steps of the power profile that the ESA has previously
              * suggested it would use.
              *
-             * Heat pump and Solar PV example: A heat pump may have the ability to heat hot water as well as heating the
-             * home. The heat pump scheduling system may have determined that the home will be unoccupied during the
-             * day, or that the indoor temperature is above the set-point and so it knows that it will not need to heat
-             * the home.
-             *
              * However, the hot water tank is likely to need to be reheated before the homeowner comes home in the
              * evening. The heat pump is not aware that the property also has a solar PV inverter which is also an ESA
              * that is communicating with the EMS.
@@ -5853,12 +5719,8 @@ export declare 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.
-             *
-             * 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.
+             * 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.
              *
              * 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.
@@ -5901,8 +5763,9 @@ export declare namespace DeviceEnergyManagement {
                     /**
                      * 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 out of the node (e.g. discharging a
-                     * battery).
+                     * Note that this is a signed value. Negative values indicate power flows out of the node
+                     *
+                     * discharging a battery).
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 9.2.7.10.1
                      */
@@ -6097,8 +5960,6 @@ export declare namespace DeviceEnergyManagement {
                      * choose to use values between 0-100 as a percentage of compressor modulation, or could use these values as
                      * Enum states meaning heating with fan, heating without fan etc.
                      *
-                     * 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 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
@@ -6330,11 +6191,11 @@ export declare 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
+             * > [!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.
+             * > 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.v14.Cluster} § 9.2.8.4
              */
@@ -6522,9 +6383,8 @@ export declare 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 LoadCon
-                 *
-                 * trol field as follows:
+                 * that use more energy, it could be requested to use more or less energy using the LoadControl field as
+                 * follows:
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 9.2.9.7.1
                  */