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

package/dist/cjs/clusters/energy-evse.d.ts

@@ -24,19 +24,19 @@ export declare namespace EnergyEvse {
          * specify how many miles or km of additional range they need for their typical daily commute. This range
          * requirement can be converted into a daily energy demand with a target charging completion time.
          *
-         * The EVSE itself may use this information (or may allow a controller such as an EMS) to compute an
+         * The EVSE itself can use this information (or may allow a controller such as an EMS) to compute an optimized
+         * charging schedule.
          *
-         * optimized charging schedule.
-         *
-         * An EVSE device may implement the Device Energy Management cluster PFR (Power Forecast Reporting) and FA
-         * (Forecast Adjustment) features. This can help a controller (such as an EMS) to optimize the EVSE against
-         * other ESAs. For example, a solar PV ESA may share its Forecast and allow the EVSE to know the best time to
-         * charge so that any excess solar generation is used to charge the EV.
+         * An EVSE device which includes a Device Energy Management device with the Device Energy Management cluster
+         * PFR (Power Forecast Reporting) feature can use the charging preferences information to produce its power
+         * forecast.
          *
          * EVSE devices that support the Device Energy Management cluster’s FA feature can have their charging profiles
          * set by a controller device such as an EMS. For example, if the EVSE advertises a simple power forecast which
          * allows the EMS to adjust over a wide range of power and time durations, then the EVSE may allow the EMS to
-         * propose a revised optimized forecast (which is the charging profile).
+         * propose a revised optimized forecast (which is the charging profile). For example, a solar PV ESA may also
+         * share its Forecast, so enabling an EMS to adjust the EVSE forecast to the best time to charge so that any
+         * excess solar generation is used to charge the EV.
          *
          * See the Device Energy Management Cluster for more details.
          *
@@ -91,6 +91,12 @@ export declare namespace EnergyEvse {
          * If the EVSE can support bi-directional charging, it may be possible to request that the vehicle can
          * discharge to the home or grid.
          *
+         * The charging and discharging may be controlled by a home Energy Management System (EMS) using the Device
+         * Energy Management cluster of the associated Device Energy Management device. For example, an EMS may use the
+         * PA (Power Adjustment) feature to continually adjust the charge/discharge current to/from the EV so as to
+         * minimise the energy flow from/to the grid as the demand in the home and the solar supply to the home both
+         * fluctuate.
+         *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.5
          */
         V2X = "V2X"
@@ -104,7 +110,8 @@ export declare namespace EnergyEvse {
         /**
          * This field shall indicate the expiry time, in UTC, when discharging will be automatically disabled.
          *
-         * A value in the past in this field shall disable the EVSE whereas a null value shall enable it permanently.
+         * A value in the past in this field shall disable the EVSE discharging whereas a null value shall enable EVSE
+         * discharging permanently.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.1
          */
@@ -112,9 +119,7 @@ export declare namespace EnergyEvse {
         /**
          * This field shall indicate the maximum current that can be received by the EVSE from the EV. The EVSE current
          * limit can be advertised to an EV in 0.6A steps. The value of the MaximumDischargeCurrent attribute shall be
-         * stored and persisted across reboots by the EVSE to the value of this
-         *
-         * field.
+         * stored and persisted across reboots by the EVSE to the value of this field.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.2
          */
@@ -128,7 +133,7 @@ export declare namespace EnergyEvse {
     interface EnableDischargingRequest extends TypeFromSchema<typeof TlvEnableDischargingRequest> {
     }
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.5
+     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.1
      */
     const TargetDayOfWeek: {
         /**
@@ -207,7 +212,7 @@ export declare namespace EnergyEvse {
          * This field represents the target SoC that the vehicle should be charged to before the
          * TargetTimeMinutesPastMidnight.
          *
-         * If the EVSE can obtain the SoC of the vehicle:
+         * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
          *
          *   • the TargetSoC field shall take precedence over the AddedEnergy field.
          *
@@ -217,13 +222,14 @@ export declare namespace EnergyEvse {
          *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
          *     vehicle decides to stop charging.
          *
-         * If the EVSE cannot obtain the SoC of the vehicle:
+         * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
          *
-         *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-         *     field may only take the values null or 100%.
+         *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+         *     the SOC feature then the TargetSoC field may only take the values null or 100%.
          *
-         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-         *     until the vehicle stops demanding a charge.
+         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+         *
+         * and charge until the vehicle stops demanding a charge.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
          */
@@ -244,7 +250,7 @@ export declare namespace EnergyEvse {
          *
          * NOTE
          *
-         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
          * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
          * battery during charging, or for heating or cooling the cabin.
          *
@@ -276,7 +282,13 @@ export declare namespace EnergyEvse {
      * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.7
      */
     const TlvChargingTargetSchedule: import("../tlv/TlvObject.js").ObjectSchema<{
-        dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+        /**
+         * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+         * is a bitmap and therefore the associated targets could be applied to multiple days.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+         */
+        dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
             /**
              * Sunday
              */
@@ -306,7 +318,12 @@ export declare namespace EnergyEvse {
              */
             saturday: BitFlag;
         }>>;
-        chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+        /**
+         * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+         */
+        chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
             /**
              * This field shall indicate the desired charging completion time of the associated day. The time will be
              * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -337,7 +354,7 @@ export declare namespace EnergyEvse {
              * This field represents the target SoC that the vehicle should be charged to before the
              * TargetTimeMinutesPastMidnight.
              *
-             * If the EVSE can obtain the SoC of the vehicle:
+             * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
              *
              *   • the TargetSoC field shall take precedence over the AddedEnergy field.
              *
@@ -347,13 +364,14 @@ export declare namespace EnergyEvse {
              *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
              *     vehicle decides to stop charging.
              *
-             * If the EVSE cannot obtain the SoC of the vehicle:
+             * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
+             *
+             *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+             *     the SOC feature then the TargetSoC field may only take the values null or 100%.
              *
-             *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-             *     field may only take the values null or 100%.
+             *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
              *
-             *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-             *     until the vehicle stops demanding a charge.
+             * and charge until the vehicle stops demanding a charge.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
              */
@@ -374,7 +392,7 @@ export declare namespace EnergyEvse {
              *
              * NOTE
              *
-             * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+             * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
              * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
              * battery during charging, or for heating or cooling the cabin.
              *
@@ -404,7 +422,13 @@ export declare namespace EnergyEvse {
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
          */
         chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-            dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+            /**
+             * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+             * is a bitmap and therefore the associated targets could be applied to multiple days.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+             */
+            dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                 /**
                  * Sunday
                  */
@@ -434,7 +458,12 @@ export declare namespace EnergyEvse {
                  */
                 saturday: BitFlag;
             }>>;
-            chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+            /**
+             * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+             */
+            chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall indicate the desired charging completion time of the associated day. The time will be
                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -465,7 +494,7 @@ export declare namespace EnergyEvse {
                  * This field represents the target SoC that the vehicle should be charged to before the
                  * TargetTimeMinutesPastMidnight.
                  *
-                 * If the EVSE can obtain the SoC of the vehicle:
+                 * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                  *
                  *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                  *
@@ -475,13 +504,14 @@ export declare namespace EnergyEvse {
                  *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                  *     vehicle decides to stop charging.
                  *
-                 * If the EVSE cannot obtain the SoC of the vehicle:
+                 * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
                  *
-                 *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                 *     field may only take the values null or 100%.
+                 *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                 *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                  *
-                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                 *     until the vehicle stops demanding a charge.
+                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+                 *
+                 * and charge until the vehicle stops demanding a charge.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                  */
@@ -502,7 +532,7 @@ export declare namespace EnergyEvse {
                  *
                  * NOTE
                  *
-                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                  * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                  * battery during charging, or for heating or cooling the cabin.
                  *
@@ -532,7 +562,13 @@ export declare namespace EnergyEvse {
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.7.1
          */
         chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-            dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+            /**
+             * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+             * is a bitmap and therefore the associated targets could be applied to multiple days.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+             */
+            dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                 /**
                  * Sunday
                  */
@@ -562,7 +598,12 @@ export declare namespace EnergyEvse {
                  */
                 saturday: BitFlag;
             }>>;
-            chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+            /**
+             * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+             */
+            chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall indicate the desired charging completion time of the associated day. The time will be
                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -593,7 +634,7 @@ export declare namespace EnergyEvse {
                  * This field represents the target SoC that the vehicle should be charged to before the
                  * TargetTimeMinutesPastMidnight.
                  *
-                 * If the EVSE can obtain the SoC of the vehicle:
+                 * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                  *
                  *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                  *
@@ -603,13 +644,14 @@ export declare namespace EnergyEvse {
                  *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                  *     vehicle decides to stop charging.
                  *
-                 * If the EVSE cannot obtain the SoC of the vehicle:
+                 * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
                  *
-                 *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                 *     field may only take the values null or 100%.
+                 *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                 *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                  *
-                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                 *     until the vehicle stops demanding a charge.
+                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+                 *
+                 * and charge until the vehicle stops demanding a charge.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                  */
@@ -630,7 +672,7 @@ export declare namespace EnergyEvse {
                  *
                  * NOTE
                  *
-                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                  * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                  * battery during charging, or for heating or cooling the cabin.
                  *
@@ -668,7 +710,7 @@ export declare namespace EnergyEvse {
     interface RfidEvent extends TypeFromSchema<typeof TlvRfidEvent> {
     }
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.1
+     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.2
      */
     enum State {
         /**
@@ -701,7 +743,7 @@ export declare namespace EnergyEvse {
         Fault = 6
     }
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.2
+     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.3
      */
     enum SupplyState {
         /**
@@ -722,12 +764,16 @@ export declare namespace EnergyEvse {
          */
         DisabledError = 3,
         /**
-         * The EV is not currently allowed to charge or discharge due to Diagnostics Mode.
+         * The EV is not currently allowed to charge or discharge due to self- diagnostics mode.
+         */
+        DisabledDiagnostics = 4,
+        /**
+         * The EV is currently allowed to charge and discharge
          */
-        DisabledDiagnostics = 4
+        Enabled = 5
     }
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.3
+     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.4
      */
     enum FaultState {
         /**
@@ -829,10 +875,9 @@ export declare namespace EnergyEvse {
          * limit can be advertised to an EV in 0.6A steps.
          *
          * The value of the this field shall be stored by the EVSE to determine the value of MaximumChargeCurrent
-         * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then
-         *
-         * this value, and then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be
-         * limited to this value.
+         * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then this value, and
+         * then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be limited to this
+         * value.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.2.3
          */
@@ -892,7 +937,6 @@ export declare namespace EnergyEvse {
         sessionDuration: import("../tlv/TlvObject.js").FieldType<number>;
         /**
          * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
-         * This value shall always be positive.
          *
          * Note that if bi-directional charging occurs during the session, then this value shall only include the sum
          * of energy transferred from the EVSE to the EV, and shall NOT be a net value of charging and discharging
@@ -903,7 +947,6 @@ export declare namespace EnergyEvse {
         sessionEnergyCharged: import("../tlv/TlvObject.js").FieldType<number | bigint>;
         /**
          * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
-         * This value shall always be positive.
          *
          * Note that if bi-directional discharging occurs during the session, then this value shall only include the
          * sum of energy transferred from the EV to the EVSE, and shall NOT be a net value of charging and discharging
@@ -939,19 +982,24 @@ export declare namespace EnergyEvse {
          */
         state: import("../tlv/TlvObject.js").FieldType<State>;
         /**
-         * This field shall indicate the value of the maximum charging or discharging current at the time the event was
-         * generated.
-         *
-         * This field is signed. A positive value indicates the EV has been enabled for charging and the value is taken
-         * directly from the MaximumChargeCurrent attribute.
+         * This field shall indicate the value of the maximum charging current at the time the event was generated.
          *
-         * A negative value indicates that the EV has been enabled for discharging and the value can be taken from the
-         * MaximumDischargeCurrent attribute with its sign inverted. i.e. if the MaximumDischargeCurrent was 32000mA,
-         * this would be represented here as -32000mA.
+         * A non-zero value indicates that the EV has been enabled for charging and the value is taken directly from
+         * the MaximumChargeCurrent attribute. A zero value indicates that the EV has not been enabled for charging.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.3
          */
         maximumCurrent: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+        /**
+         * This field shall indicate the value of the maximum discharging current at the time the event was generated.
+         *
+         * A non-zero value indicates that the EV has been enabled for discharging and the value is taken directly from
+         * the MaximumDischargeCurrent attribute. A zero value indicates that the EV has not been enabled for
+         * discharging.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.4
+         */
+        maximumDischargeCurrent: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
     }>;
     /**
      * Body of the EnergyEvse energyTransferStarted event
@@ -961,7 +1009,7 @@ export declare namespace EnergyEvse {
     interface EnergyTransferStartedEvent extends TypeFromSchema<typeof TlvEnergyTransferStartedEvent> {
     }
     /**
-     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.4
+     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.5
      */
     enum EnergyTransferStoppedReason {
         /**
@@ -1001,7 +1049,20 @@ export declare namespace EnergyEvse {
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.3
          */
         reason: import("../tlv/TlvObject.js").FieldType<EnergyTransferStoppedReason>;
+        /**
+         * This field shall indicate the amount of energy transferred from the EVSE to the EV since the previous
+         * EnergyTransferStarted event, in mWh.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.4
+         */
         energyTransferred: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+        /**
+         * This field shall indicate the amount of energy transferred from the EV to the EVSE since the previous
+         * EnergyTransferStarted event, in mWh.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.5
+         */
+        energyDischarged: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
     }>;
     /**
      * Body of the EnergyEvse energyTransferStopped event
@@ -1090,7 +1151,8 @@ export declare namespace EnergyEvse {
         };
         readonly commands: {
             /**
-             * Allows a client to enable the EVSE to discharge an EV.
+             * Upon receipt, this shall allow a client to enable the discharge of an EV, and to provide or update the
+             * maximum discharge current.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3
              */
@@ -1098,7 +1160,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the expiry time, in UTC, when discharging will be automatically disabled.
                  *
-                 * A value in the past in this field shall disable the EVSE whereas a null value shall enable it permanently.
+                 * A value in the past in this field shall disable the EVSE discharging whereas a null value shall enable EVSE
+                 * discharging permanently.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.1
                  */
@@ -1106,9 +1169,7 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the maximum current that can be received by the EVSE from the EV. The EVSE current
                  * limit can be advertised to an EV in 0.6A steps. The value of the MaximumDischargeCurrent attribute shall be
-                 * stored and persisted across reboots by the EVSE to the value of this
-                 *
-                 * field.
+                 * stored and persisted across reboots by the EVSE to the value of this field.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.2
                  */
@@ -1125,7 +1186,9 @@ export declare namespace EnergyEvse {
              * Indicates the time, in UTC, when the EVSE plans to start the next scheduled charge based on the charging
              * preferences.
              *
-             * If this is null it indicates that there is no scheduled charging, or that the vehicle is not plugged in.
+             * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+             * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+             * enabled.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.12
              */
@@ -1134,7 +1197,9 @@ export declare namespace EnergyEvse {
              * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the
              * charging preferences.
              *
-             * If this is null it indicates that there is no scheduled charging, or that the vehicle is not plugged in.
+             * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+             * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+             * enabled.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.13
              */
@@ -1143,8 +1208,9 @@ export declare namespace EnergyEvse {
              * Indicates the amount of energy that the EVSE is going to attempt to add to the vehicle in the next
              * charging target.
              *
-             * If this is null it indicates that there is no scheduled charging, or that the EVSE is using the
-             * TargetSoC method to charge the vehicle.
+             * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+             * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+             * enabled, or that the next ChargingTargetStruct is using the TargetSoC value to charge the vehicle.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.14
              */
@@ -1152,8 +1218,10 @@ export declare namespace EnergyEvse {
             /**
              * Indicates the target SoC the EVSE is going to attempt to reach when the vehicle is next charged.
              *
-             * If this is null it indicates that there is no scheduled charging, or that the EVSE cannot obtain the
-             * current State of Charge from the vehicle.
+             * A null value indicates that there is no scheduled charging
+             *
+             * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+             * enabled, or that the next ChargingTargetStruct is using the AddedEnergy value to charge the vehicle.
              *
              * If the SOC feature is not supported, only the values null and 100% are supported.
              *
@@ -1184,7 +1252,9 @@ export declare namespace EnergyEvse {
              *
              * AddedRange (km) = 10,000 x 4800 / 1,000,000 = 48 km
              *
-             * AddedRange (Miles) = AddedEnergy (Wh) x ApproxEVEfficiency (km/kWh x 1000) x 0.6213
+             * AddedRange (Miles) = AddedEnergy (Wh) x ApproxEVEfficiency (km/kWh x 1000) x
+             *
+             * 0.6213
              *
              * = 29.82 Miles
              *
@@ -1207,7 +1277,13 @@ export declare namespace EnergyEvse {
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                  */
                 chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                    dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                    /**
+                     * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                     * is a bitmap and therefore the associated targets could be applied to multiple days.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                     */
+                    dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                         /**
                          * Sunday
                          */
@@ -1237,7 +1313,12 @@ export declare namespace EnergyEvse {
                          */
                         saturday: BitFlag;
                     }>>;
-                    chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                    /**
+                     * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                     */
+                    chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate the desired charging completion time of the associated day. The time will be
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -1268,7 +1349,7 @@ export declare namespace EnergyEvse {
                          * This field represents the target SoC that the vehicle should be charged to before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * If the EVSE can obtain the SoC of the vehicle:
+                         * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                          *
                          *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                          *
@@ -1278,13 +1359,14 @@ export declare namespace EnergyEvse {
                          *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                          *     vehicle decides to stop charging.
                          *
-                         * If the EVSE cannot obtain the SoC of the vehicle:
+                         * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
                          *
-                         *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                         *     field may only take the values null or 100%.
+                         *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                         *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                          *
-                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                         *     until the vehicle stops demanding a charge.
+                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+                         *
+                         * and charge until the vehicle stops demanding a charge.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                          */
@@ -1305,7 +1387,7 @@ export declare namespace EnergyEvse {
                          *
                          * NOTE
                          *
-                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                          * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                          * battery during charging, or for heating or cooling the cabin.
                          *
@@ -1328,7 +1410,13 @@ export declare namespace EnergyEvse {
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.7.1
                  */
                 chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                    dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                    /**
+                     * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                     * is a bitmap and therefore the associated targets could be applied to multiple days.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                     */
+                    dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                         /**
                          * Sunday
                          */
@@ -1358,7 +1446,12 @@ export declare namespace EnergyEvse {
                          */
                         saturday: BitFlag;
                     }>>;
-                    chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                    /**
+                     * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                     */
+                    chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate the desired charging completion time of the associated day. The time will be
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -1389,7 +1482,7 @@ export declare namespace EnergyEvse {
                          * This field represents the target SoC that the vehicle should be charged to before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * If the EVSE can obtain the SoC of the vehicle:
+                         * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                          *
                          *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                          *
@@ -1399,13 +1492,14 @@ export declare namespace EnergyEvse {
                          *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                          *     vehicle decides to stop charging.
                          *
-                         * If the EVSE cannot obtain the SoC of the vehicle:
+                         * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
+                         *
+                         *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                         *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                          *
-                         *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                         *     field may only take the values null or 100%.
+                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
                          *
-                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                         *     until the vehicle stops demanding a charge.
+                         * and charge until the vehicle stops demanding a charge.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                          */
@@ -1426,7 +1520,7 @@ export declare namespace EnergyEvse {
                          *
                          * NOTE
                          *
-                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                          * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                          * battery during charging, or for heating or cooling the cabin.
                          *
@@ -1510,7 +1604,7 @@ export declare namespace EnergyEvse {
     const Base: {
         readonly id: 153;
         readonly name: "EnergyEvse";
-        readonly revision: 2;
+        readonly revision: 3;
         readonly features: {
             /**
              * ChargingPreferences
@@ -1521,19 +1615,19 @@ export declare namespace EnergyEvse {
              * This range requirement can be converted into a daily energy demand with a target charging completion
              * time.
              *
-             * The EVSE itself may use this information (or may allow a controller such as an EMS) to compute an
-             *
+             * The EVSE itself can use this information (or may allow a controller such as an EMS) to compute an
              * optimized charging schedule.
              *
-             * An EVSE device may implement the Device Energy Management cluster PFR (Power Forecast Reporting) and FA
-             * (Forecast Adjustment) features. This can help a controller (such as an EMS) to optimize the EVSE against
-             * other ESAs. For example, a solar PV ESA may share its Forecast and allow the EVSE to know the best time
-             * to charge so that any excess solar generation is used to charge the EV.
+             * An EVSE device which includes a Device Energy Management device with the Device Energy Management
+             * cluster PFR (Power Forecast Reporting) feature can use the charging preferences information to produce
+             * its power forecast.
              *
              * EVSE devices that support the Device Energy Management cluster’s FA feature can have their charging
              * profiles set by a controller device such as an EMS. For example, if the EVSE advertises a simple power
              * forecast which allows the EMS to adjust over a wide range of power and time durations, then the EVSE may
-             * allow the EMS to propose a revised optimized forecast (which is the charging profile).
+             * allow the EMS to propose a revised optimized forecast (which is the charging profile). For example, a
+             * solar PV ESA may also share its Forecast, so enabling an EMS to adjust the EVSE forecast to the best
+             * time to charge so that any excess solar generation is used to charge the EV.
              *
              * See the Device Energy Management Cluster for more details.
              *
@@ -1588,6 +1682,12 @@ export declare namespace EnergyEvse {
              * If the EVSE can support bi-directional charging, it may be possible to request that the vehicle can
              * discharge to the home or grid.
              *
+             * The charging and discharging may be controlled by a home Energy Management System (EMS) using the Device
+             * Energy Management cluster of the associated Device Energy Management device. For example, an EMS may use
+             * the PA (Power Adjustment) feature to continually adjust the charge/discharge current to/from the EV so
+             * as to minimise the energy flow from/to the grid as the demand in the home and the solar supply to the
+             * home both fluctuate.
+             *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.5
              */
             readonly v2X: BitFlag;
@@ -1602,10 +1702,12 @@ export declare namespace EnergyEvse {
              *
              * NOTE
              *
-             * SessionEnding is not really a state but a transition. However, the transition period
+             * SessionEnding is not really a state but a transition. However, the transition period may take a few
+             * seconds and is useful for some clean up purposes.
+             *
+             * The Fault state is used to indicate that the FaultState attribute is not NoError.
              *
-             * may take a few seconds and is useful for some clean up purposes. The Fault state is used to indicate
-             * that the FaultState attribute is not NoError.
+             * A null value shall indicate that the state cannot be determined.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.1
              */
@@ -1649,8 +1751,9 @@ export declare namespace EnergyEvse {
              */
             readonly circuitCapacity: Attribute<number | bigint, any>;
             /**
-             * Indicates the minimum current that can be delivered by the EVSE to the EV. The attribute can be set
-             * using the EnableCharging command.
+             * Indicates the minimum current that can be delivered by the EVSE to the EV.
+             *
+             * The attribute can be set using the EnableCharging command.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.7
              */
@@ -1732,7 +1835,8 @@ export declare namespace EnergyEvse {
              */
             readonly disable: Command<void, void, any>;
             /**
-             * Allows a client to enable the EVSE to charge an EV.
+             * This command allows a client to enable the EVSE to charge an EV, and to provide or update the maximum
+             * and minimum charge current.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.2
              */
@@ -1761,10 +1865,9 @@ export declare namespace EnergyEvse {
                  * limit can be advertised to an EV in 0.6A steps.
                  *
                  * The value of the this field shall be stored by the EVSE to determine the value of MaximumChargeCurrent
-                 * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then
-                 *
-                 * this value, and then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be
-                 * limited to this value.
+                 * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then this value, and
+                 * then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be limited to this
+                 * value.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.2.3
                  */
@@ -1819,7 +1922,6 @@ export declare namespace EnergyEvse {
                 sessionDuration: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
                  * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
-                 * This value shall always be positive.
                  *
                  * Note that if bi-directional charging occurs during the session, then this value shall only include the sum
                  * of energy transferred from the EVSE to the EV, and shall NOT be a net value of charging and discharging
@@ -1830,7 +1932,6 @@ export declare namespace EnergyEvse {
                 sessionEnergyCharged: import("../tlv/TlvObject.js").FieldType<number | bigint>;
                 /**
                  * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
-                 * This value shall always be positive.
                  *
                  * Note that if bi-directional discharging occurs during the session, then this value shall only include the
                  * sum of energy transferred from the EV to the EVSE, and shall NOT be a net value of charging and discharging
@@ -1841,7 +1942,9 @@ export declare namespace EnergyEvse {
                 sessionEnergyDischarged: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
-             * This event shall be generated when the EV starts charging or discharging.
+             * This event shall be generated whenever the EV starts charging or discharging, except when an EV has
+             * switched between charging and discharging under the control of the PowerAdjustment feature of the Device
+             * Energy Management cluster of the associated Device Energy Management device.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3
              */
@@ -1859,22 +1962,29 @@ export declare namespace EnergyEvse {
                  */
                 state: import("../tlv/TlvObject.js").FieldType<State>;
                 /**
-                 * This field shall indicate the value of the maximum charging or discharging current at the time the event was
-                 * generated.
+                 * This field shall indicate the value of the maximum charging current at the time the event was generated.
                  *
-                 * This field is signed. A positive value indicates the EV has been enabled for charging and the value is taken
-                 * directly from the MaximumChargeCurrent attribute.
-                 *
-                 * A negative value indicates that the EV has been enabled for discharging and the value can be taken from the
-                 * MaximumDischargeCurrent attribute with its sign inverted. i.e. if the MaximumDischargeCurrent was 32000mA,
-                 * this would be represented here as -32000mA.
+                 * A non-zero value indicates that the EV has been enabled for charging and the value is taken directly from
+                 * the MaximumChargeCurrent attribute. A zero value indicates that the EV has not been enabled for charging.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.3
                  */
                 maximumCurrent: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+                /**
+                 * This field shall indicate the value of the maximum discharging current at the time the event was generated.
+                 *
+                 * A non-zero value indicates that the EV has been enabled for discharging and the value is taken directly from
+                 * the MaximumDischargeCurrent attribute. A zero value indicates that the EV has not been enabled for
+                 * discharging.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.4
+                 */
+                maximumDischargeCurrent: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
-             * This event shall be generated when the EV stops charging or discharging.
+             * This event shall be generated whenever the EV stops charging or discharging, except when an EV has
+             * switched between charging and discharging under the control of the PowerAdjustment feature of the Device
+             * Energy Management cluster of the associated Device Energy Management device.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4
              */
@@ -1897,7 +2007,20 @@ export declare namespace EnergyEvse {
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.3
                  */
                 reason: import("../tlv/TlvObject.js").FieldType<EnergyTransferStoppedReason>;
+                /**
+                 * This field shall indicate the amount of energy transferred from the EVSE to the EV since the previous
+                 * EnergyTransferStarted event, in mWh.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.4
+                 */
                 energyTransferred: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+                /**
+                 * This field shall indicate the amount of energy transferred from the EV to the EVSE since the previous
+                 * EnergyTransferStarted event, in mWh.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.5
+                 */
+                energyDischarged: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
              * If the EVSE detects a fault it shall generate a Fault Event. The SupplyState attribute shall be set to
@@ -1986,7 +2109,8 @@ export declare namespace EnergyEvse {
                 };
                 readonly commands: {
                     /**
-                     * Allows a client to enable the EVSE to discharge an EV.
+                     * Upon receipt, this shall allow a client to enable the discharge of an EV, and to provide or update the
+                     * maximum discharge current.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3
                      */
@@ -1994,7 +2118,8 @@ export declare namespace EnergyEvse {
                         /**
                          * This field shall indicate the expiry time, in UTC, when discharging will be automatically disabled.
                          *
-                         * A value in the past in this field shall disable the EVSE whereas a null value shall enable it permanently.
+                         * A value in the past in this field shall disable the EVSE discharging whereas a null value shall enable EVSE
+                         * discharging permanently.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.1
                          */
@@ -2002,9 +2127,7 @@ export declare namespace EnergyEvse {
                         /**
                          * This field shall indicate the maximum current that can be received by the EVSE from the EV. The EVSE current
                          * limit can be advertised to an EV in 0.6A steps. The value of the MaximumDischargeCurrent attribute shall be
-                         * stored and persisted across reboots by the EVSE to the value of this
-                         *
-                         * field.
+                         * stored and persisted across reboots by the EVSE to the value of this field.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.2
                          */
@@ -2022,7 +2145,9 @@ export declare namespace EnergyEvse {
                      * Indicates the time, in UTC, when the EVSE plans to start the next scheduled charge based on the charging
                      * preferences.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the vehicle is not plugged in.
+                     * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.12
                      */
@@ -2031,7 +2156,9 @@ export declare namespace EnergyEvse {
                      * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the
                      * charging preferences.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the vehicle is not plugged in.
+                     * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.13
                      */
@@ -2040,8 +2167,9 @@ export declare namespace EnergyEvse {
                      * Indicates the amount of energy that the EVSE is going to attempt to add to the vehicle in the next
                      * charging target.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the EVSE is using the
-                     * TargetSoC method to charge the vehicle.
+                     * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled, or that the next ChargingTargetStruct is using the TargetSoC value to charge the vehicle.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.14
                      */
@@ -2049,8 +2177,10 @@ export declare namespace EnergyEvse {
                     /**
                      * Indicates the target SoC the EVSE is going to attempt to reach when the vehicle is next charged.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the EVSE cannot obtain the
-                     * current State of Charge from the vehicle.
+                     * A null value indicates that there is no scheduled charging
+                     *
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled, or that the next ChargingTargetStruct is using the AddedEnergy value to charge the vehicle.
                      *
                      * If the SOC feature is not supported, only the values null and 100% are supported.
                      *
@@ -2081,7 +2211,9 @@ export declare namespace EnergyEvse {
                      *
                      * AddedRange (km) = 10,000 x 4800 / 1,000,000 = 48 km
                      *
-                     * AddedRange (Miles) = AddedEnergy (Wh) x ApproxEVEfficiency (km/kWh x 1000) x 0.6213
+                     * AddedRange (Miles) = AddedEnergy (Wh) x ApproxEVEfficiency (km/kWh x 1000) x
+                     *
+                     * 0.6213
                      *
                      * = 29.82 Miles
                      *
@@ -2104,7 +2236,13 @@ export declare namespace EnergyEvse {
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                          */
                         chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                            dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                            /**
+                             * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                             * is a bitmap and therefore the associated targets could be applied to multiple days.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                             */
+                            dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                                 /**
                                  * Sunday
                                  */
@@ -2134,7 +2272,12 @@ export declare namespace EnergyEvse {
                                  */
                                 saturday: BitFlag;
                             }>>;
-                            chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                            /**
+                             * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                             */
+                            chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                                 /**
                                  * This field shall indicate the desired charging completion time of the associated day. The time will be
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -2165,7 +2308,7 @@ export declare namespace EnergyEvse {
                                  * This field represents the target SoC that the vehicle should be charged to before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * If the EVSE can obtain the SoC of the vehicle:
+                                 * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                                  *
                                  *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                                  *
@@ -2175,13 +2318,14 @@ export declare namespace EnergyEvse {
                                  *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                                  *     vehicle decides to stop charging.
                                  *
-                                 * If the EVSE cannot obtain the SoC of the vehicle:
+                                 * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
+                                 *
+                                 *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                                 *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                                  *
-                                 *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                                 *     field may only take the values null or 100%.
+                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
                                  *
-                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                                 *     until the vehicle stops demanding a charge.
+                                 * and charge until the vehicle stops demanding a charge.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                                  */
@@ -2202,7 +2346,7 @@ export declare namespace EnergyEvse {
                                  *
                                  * NOTE
                                  *
-                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                                  * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                                  * battery during charging, or for heating or cooling the cabin.
                                  *
@@ -2225,7 +2369,13 @@ export declare namespace EnergyEvse {
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.7.1
                          */
                         chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                            dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                            /**
+                             * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                             * is a bitmap and therefore the associated targets could be applied to multiple days.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                             */
+                            dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                                 /**
                                  * Sunday
                                  */
@@ -2255,7 +2405,12 @@ export declare namespace EnergyEvse {
                                  */
                                 saturday: BitFlag;
                             }>>;
-                            chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                            /**
+                             * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                             */
+                            chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                                 /**
                                  * This field shall indicate the desired charging completion time of the associated day. The time will be
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -2286,7 +2441,7 @@ export declare namespace EnergyEvse {
                                  * This field represents the target SoC that the vehicle should be charged to before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * If the EVSE can obtain the SoC of the vehicle:
+                                 * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                                  *
                                  *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                                  *
@@ -2296,13 +2451,14 @@ export declare namespace EnergyEvse {
                                  *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                                  *     vehicle decides to stop charging.
                                  *
-                                 * If the EVSE cannot obtain the SoC of the vehicle:
+                                 * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
                                  *
-                                 *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                                 *     field may only take the values null or 100%.
+                                 *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                                 *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                                  *
-                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                                 *     until the vehicle stops demanding a charge.
+                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+                                 *
+                                 * and charge until the vehicle stops demanding a charge.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                                  */
@@ -2323,7 +2479,7 @@ export declare namespace EnergyEvse {
                                  *
                                  * NOTE
                                  *
-                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                                  * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                                  * battery during charging, or for heating or cooling the cabin.
                                  *
@@ -2404,6 +2560,11 @@ export declare namespace EnergyEvse {
                     }>, any>;
                 };
             };
+        }, {
+            readonly flags: {
+                readonly chargingPreferences: false;
+            };
+            readonly component: false;
         }];
     };
     /**
@@ -2412,7 +2573,7 @@ export declare namespace EnergyEvse {
     const ClusterInstance: MutableCluster<{
         readonly id: 153;
         readonly name: "EnergyEvse";
-        readonly revision: 2;
+        readonly revision: 3;
         readonly features: {
             /**
              * ChargingPreferences
@@ -2423,19 +2584,19 @@ export declare namespace EnergyEvse {
              * This range requirement can be converted into a daily energy demand with a target charging completion
              * time.
              *
-             * The EVSE itself may use this information (or may allow a controller such as an EMS) to compute an
-             *
+             * The EVSE itself can use this information (or may allow a controller such as an EMS) to compute an
              * optimized charging schedule.
              *
-             * An EVSE device may implement the Device Energy Management cluster PFR (Power Forecast Reporting) and FA
-             * (Forecast Adjustment) features. This can help a controller (such as an EMS) to optimize the EVSE against
-             * other ESAs. For example, a solar PV ESA may share its Forecast and allow the EVSE to know the best time
-             * to charge so that any excess solar generation is used to charge the EV.
+             * An EVSE device which includes a Device Energy Management device with the Device Energy Management
+             * cluster PFR (Power Forecast Reporting) feature can use the charging preferences information to produce
+             * its power forecast.
              *
              * EVSE devices that support the Device Energy Management cluster’s FA feature can have their charging
              * profiles set by a controller device such as an EMS. For example, if the EVSE advertises a simple power
              * forecast which allows the EMS to adjust over a wide range of power and time durations, then the EVSE may
-             * allow the EMS to propose a revised optimized forecast (which is the charging profile).
+             * allow the EMS to propose a revised optimized forecast (which is the charging profile). For example, a
+             * solar PV ESA may also share its Forecast, so enabling an EMS to adjust the EVSE forecast to the best
+             * time to charge so that any excess solar generation is used to charge the EV.
              *
              * See the Device Energy Management Cluster for more details.
              *
@@ -2490,6 +2651,12 @@ export declare namespace EnergyEvse {
              * If the EVSE can support bi-directional charging, it may be possible to request that the vehicle can
              * discharge to the home or grid.
              *
+             * The charging and discharging may be controlled by a home Energy Management System (EMS) using the Device
+             * Energy Management cluster of the associated Device Energy Management device. For example, an EMS may use
+             * the PA (Power Adjustment) feature to continually adjust the charge/discharge current to/from the EV so
+             * as to minimise the energy flow from/to the grid as the demand in the home and the solar supply to the
+             * home both fluctuate.
+             *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.5
              */
             readonly v2X: BitFlag;
@@ -2504,10 +2671,12 @@ export declare namespace EnergyEvse {
              *
              * NOTE
              *
-             * SessionEnding is not really a state but a transition. However, the transition period
+             * SessionEnding is not really a state but a transition. However, the transition period may take a few
+             * seconds and is useful for some clean up purposes.
              *
-             * may take a few seconds and is useful for some clean up purposes. The Fault state is used to indicate
-             * that the FaultState attribute is not NoError.
+             * The Fault state is used to indicate that the FaultState attribute is not NoError.
+             *
+             * A null value shall indicate that the state cannot be determined.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.1
              */
@@ -2551,8 +2720,9 @@ export declare namespace EnergyEvse {
              */
             readonly circuitCapacity: Attribute<number | bigint, any>;
             /**
-             * Indicates the minimum current that can be delivered by the EVSE to the EV. The attribute can be set
-             * using the EnableCharging command.
+             * Indicates the minimum current that can be delivered by the EVSE to the EV.
+             *
+             * The attribute can be set using the EnableCharging command.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.7
              */
@@ -2634,7 +2804,8 @@ export declare namespace EnergyEvse {
              */
             readonly disable: Command<void, void, any>;
             /**
-             * Allows a client to enable the EVSE to charge an EV.
+             * This command allows a client to enable the EVSE to charge an EV, and to provide or update the maximum
+             * and minimum charge current.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.2
              */
@@ -2663,10 +2834,9 @@ export declare namespace EnergyEvse {
                  * limit can be advertised to an EV in 0.6A steps.
                  *
                  * The value of the this field shall be stored by the EVSE to determine the value of MaximumChargeCurrent
-                 * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then
-                 *
-                 * this value, and then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be
-                 * limited to this value.
+                 * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then this value, and
+                 * then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be limited to this
+                 * value.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.2.3
                  */
@@ -2721,7 +2891,6 @@ export declare namespace EnergyEvse {
                 sessionDuration: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
                  * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
-                 * This value shall always be positive.
                  *
                  * Note that if bi-directional charging occurs during the session, then this value shall only include the sum
                  * of energy transferred from the EVSE to the EV, and shall NOT be a net value of charging and discharging
@@ -2732,7 +2901,6 @@ export declare namespace EnergyEvse {
                 sessionEnergyCharged: import("../tlv/TlvObject.js").FieldType<number | bigint>;
                 /**
                  * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
-                 * This value shall always be positive.
                  *
                  * Note that if bi-directional discharging occurs during the session, then this value shall only include the
                  * sum of energy transferred from the EV to the EVSE, and shall NOT be a net value of charging and discharging
@@ -2743,7 +2911,9 @@ export declare namespace EnergyEvse {
                 sessionEnergyDischarged: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
-             * This event shall be generated when the EV starts charging or discharging.
+             * This event shall be generated whenever the EV starts charging or discharging, except when an EV has
+             * switched between charging and discharging under the control of the PowerAdjustment feature of the Device
+             * Energy Management cluster of the associated Device Energy Management device.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3
              */
@@ -2761,22 +2931,29 @@ export declare namespace EnergyEvse {
                  */
                 state: import("../tlv/TlvObject.js").FieldType<State>;
                 /**
-                 * This field shall indicate the value of the maximum charging or discharging current at the time the event was
-                 * generated.
+                 * This field shall indicate the value of the maximum charging current at the time the event was generated.
                  *
-                 * This field is signed. A positive value indicates the EV has been enabled for charging and the value is taken
-                 * directly from the MaximumChargeCurrent attribute.
-                 *
-                 * A negative value indicates that the EV has been enabled for discharging and the value can be taken from the
-                 * MaximumDischargeCurrent attribute with its sign inverted. i.e. if the MaximumDischargeCurrent was 32000mA,
-                 * this would be represented here as -32000mA.
+                 * A non-zero value indicates that the EV has been enabled for charging and the value is taken directly from
+                 * the MaximumChargeCurrent attribute. A zero value indicates that the EV has not been enabled for charging.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.3
                  */
                 maximumCurrent: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+                /**
+                 * This field shall indicate the value of the maximum discharging current at the time the event was generated.
+                 *
+                 * A non-zero value indicates that the EV has been enabled for discharging and the value is taken directly from
+                 * the MaximumDischargeCurrent attribute. A zero value indicates that the EV has not been enabled for
+                 * discharging.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.4
+                 */
+                maximumDischargeCurrent: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
-             * This event shall be generated when the EV stops charging or discharging.
+             * This event shall be generated whenever the EV stops charging or discharging, except when an EV has
+             * switched between charging and discharging under the control of the PowerAdjustment feature of the Device
+             * Energy Management cluster of the associated Device Energy Management device.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4
              */
@@ -2799,7 +2976,20 @@ export declare namespace EnergyEvse {
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.3
                  */
                 reason: import("../tlv/TlvObject.js").FieldType<EnergyTransferStoppedReason>;
+                /**
+                 * This field shall indicate the amount of energy transferred from the EVSE to the EV since the previous
+                 * EnergyTransferStarted event, in mWh.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.4
+                 */
                 energyTransferred: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+                /**
+                 * This field shall indicate the amount of energy transferred from the EV to the EVSE since the previous
+                 * EnergyTransferStarted event, in mWh.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.5
+                 */
+                energyDischarged: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
              * If the EVSE detects a fault it shall generate a Fault Event. The SupplyState attribute shall be set to
@@ -2888,7 +3078,8 @@ export declare namespace EnergyEvse {
                 };
                 readonly commands: {
                     /**
-                     * Allows a client to enable the EVSE to discharge an EV.
+                     * Upon receipt, this shall allow a client to enable the discharge of an EV, and to provide or update the
+                     * maximum discharge current.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3
                      */
@@ -2896,7 +3087,8 @@ export declare namespace EnergyEvse {
                         /**
                          * This field shall indicate the expiry time, in UTC, when discharging will be automatically disabled.
                          *
-                         * A value in the past in this field shall disable the EVSE whereas a null value shall enable it permanently.
+                         * A value in the past in this field shall disable the EVSE discharging whereas a null value shall enable EVSE
+                         * discharging permanently.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.1
                          */
@@ -2904,9 +3096,7 @@ export declare namespace EnergyEvse {
                         /**
                          * This field shall indicate the maximum current that can be received by the EVSE from the EV. The EVSE current
                          * limit can be advertised to an EV in 0.6A steps. The value of the MaximumDischargeCurrent attribute shall be
-                         * stored and persisted across reboots by the EVSE to the value of this
-                         *
-                         * field.
+                         * stored and persisted across reboots by the EVSE to the value of this field.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.2
                          */
@@ -2924,7 +3114,9 @@ export declare namespace EnergyEvse {
                      * Indicates the time, in UTC, when the EVSE plans to start the next scheduled charge based on the charging
                      * preferences.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the vehicle is not plugged in.
+                     * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.12
                      */
@@ -2933,7 +3125,9 @@ export declare namespace EnergyEvse {
                      * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the
                      * charging preferences.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the vehicle is not plugged in.
+                     * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.13
                      */
@@ -2942,8 +3136,9 @@ export declare namespace EnergyEvse {
                      * Indicates the amount of energy that the EVSE is going to attempt to add to the vehicle in the next
                      * charging target.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the EVSE is using the
-                     * TargetSoC method to charge the vehicle.
+                     * A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled, or that the next ChargingTargetStruct is using the TargetSoC value to charge the vehicle.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.14
                      */
@@ -2951,8 +3146,10 @@ export declare namespace EnergyEvse {
                     /**
                      * Indicates the target SoC the EVSE is going to attempt to reach when the vehicle is next charged.
                      *
-                     * If this is null it indicates that there is no scheduled charging, or that the EVSE cannot obtain the
-                     * current State of Charge from the vehicle.
+                     * A null value indicates that there is no scheduled charging
+                     *
+                     * Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is
+                     * enabled, or that the next ChargingTargetStruct is using the AddedEnergy value to charge the vehicle.
                      *
                      * If the SOC feature is not supported, only the values null and 100% are supported.
                      *
@@ -2983,7 +3180,9 @@ export declare namespace EnergyEvse {
                      *
                      * AddedRange (km) = 10,000 x 4800 / 1,000,000 = 48 km
                      *
-                     * AddedRange (Miles) = AddedEnergy (Wh) x ApproxEVEfficiency (km/kWh x 1000) x 0.6213
+                     * AddedRange (Miles) = AddedEnergy (Wh) x ApproxEVEfficiency (km/kWh x 1000) x
+                     *
+                     * 0.6213
                      *
                      * = 29.82 Miles
                      *
@@ -3006,7 +3205,13 @@ export declare namespace EnergyEvse {
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                          */
                         chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                            dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                            /**
+                             * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                             * is a bitmap and therefore the associated targets could be applied to multiple days.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                             */
+                            dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                                 /**
                                  * Sunday
                                  */
@@ -3036,7 +3241,12 @@ export declare namespace EnergyEvse {
                                  */
                                 saturday: BitFlag;
                             }>>;
-                            chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                            /**
+                             * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                             */
+                            chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                                 /**
                                  * This field shall indicate the desired charging completion time of the associated day. The time will be
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -3067,7 +3277,7 @@ export declare namespace EnergyEvse {
                                  * This field represents the target SoC that the vehicle should be charged to before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * If the EVSE can obtain the SoC of the vehicle:
+                                 * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                                  *
                                  *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                                  *
@@ -3077,13 +3287,14 @@ export declare namespace EnergyEvse {
                                  *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                                  *     vehicle decides to stop charging.
                                  *
-                                 * If the EVSE cannot obtain the SoC of the vehicle:
+                                 * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
+                                 *
+                                 *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                                 *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                                  *
-                                 *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                                 *     field may only take the values null or 100%.
+                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
                                  *
-                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                                 *     until the vehicle stops demanding a charge.
+                                 * and charge until the vehicle stops demanding a charge.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                                  */
@@ -3104,7 +3315,7 @@ export declare namespace EnergyEvse {
                                  *
                                  * NOTE
                                  *
-                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                                  * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                                  * battery during charging, or for heating or cooling the cabin.
                                  *
@@ -3127,7 +3338,13 @@ export declare namespace EnergyEvse {
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.7.1
                          */
                         chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                            dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                            /**
+                             * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                             * is a bitmap and therefore the associated targets could be applied to multiple days.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                             */
+                            dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                                 /**
                                  * Sunday
                                  */
@@ -3157,7 +3374,12 @@ export declare namespace EnergyEvse {
                                  */
                                 saturday: BitFlag;
                             }>>;
-                            chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                            /**
+                             * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                             *
+                             * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                             */
+                            chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                                 /**
                                  * This field shall indicate the desired charging completion time of the associated day. The time will be
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -3188,7 +3410,7 @@ export declare namespace EnergyEvse {
                                  * This field represents the target SoC that the vehicle should be charged to before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * If the EVSE can obtain the SoC of the vehicle:
+                                 * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                                  *
                                  *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                                  *
@@ -3198,13 +3420,14 @@ export declare namespace EnergyEvse {
                                  *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                                  *     vehicle decides to stop charging.
                                  *
-                                 * If the EVSE cannot obtain the SoC of the vehicle:
+                                 * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
                                  *
-                                 *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                                 *     field may only take the values null or 100%.
+                                 *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                                 *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                                  *
-                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                                 *     until the vehicle stops demanding a charge.
+                                 *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+                                 *
+                                 * and charge until the vehicle stops demanding a charge.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                                  */
@@ -3225,7 +3448,7 @@ export declare namespace EnergyEvse {
                                  *
                                  * NOTE
                                  *
-                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                                 * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                                  * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                                  * battery during charging, or for heating or cooling the cabin.
                                  *
@@ -3306,6 +3529,11 @@ export declare namespace EnergyEvse {
                     }>, any>;
                 };
             };
+        }, {
+            readonly flags: {
+                readonly chargingPreferences: false;
+            };
+            readonly component: false;
         }];
     }, []>;
     /**
@@ -3319,8 +3547,9 @@ export declare namespace EnergyEvse {
      * IEC61841 define Pilot signal as a modulated DC voltage on a single wire.
      *
      * Power Line Communication (PLC) is supported by some EVSEs (e.g. for support of ISO 15118 in Europe and SAE
-     * J2931/4 in NA) and may enable features such as Vehicle to Grid (V2G) or Vehicle to Home (V2H) that allows for
-     * bi-directional charging/discharging of electric vehicles.
+     * J2931/4 in NA) and may enable features such as Vehicle to Grid (V2G) or Vehicle to
+     *
+     * Home (V2H) that allows for bi-directional charging/discharging of electric vehicles.
      *
      * More modern EVSE devices may optionally support ISO 15118-20 in Europe and SAE J2836/3 for NA to support
      * bi-directional charging (Vehicle to Grid - V2G) and Plug and Charge capabilities.
@@ -3354,7 +3583,7 @@ export declare namespace EnergyEvse {
     const CompleteInstance: MutableCluster<{
         readonly id: import("#general").Branded<153, "ClusterId">;
         readonly name: "EnergyEvse";
-        readonly revision: 2;
+        readonly revision: 3;
         readonly features: {
             /**
              * ChargingPreferences
@@ -3365,19 +3594,19 @@ export declare namespace EnergyEvse {
              * This range requirement can be converted into a daily energy demand with a target charging completion
              * time.
              *
-             * The EVSE itself may use this information (or may allow a controller such as an EMS) to compute an
-             *
+             * The EVSE itself can use this information (or may allow a controller such as an EMS) to compute an
              * optimized charging schedule.
              *
-             * An EVSE device may implement the Device Energy Management cluster PFR (Power Forecast Reporting) and FA
-             * (Forecast Adjustment) features. This can help a controller (such as an EMS) to optimize the EVSE against
-             * other ESAs. For example, a solar PV ESA may share its Forecast and allow the EVSE to know the best time
-             * to charge so that any excess solar generation is used to charge the EV.
+             * An EVSE device which includes a Device Energy Management device with the Device Energy Management
+             * cluster PFR (Power Forecast Reporting) feature can use the charging preferences information to produce
+             * its power forecast.
              *
              * EVSE devices that support the Device Energy Management cluster’s FA feature can have their charging
              * profiles set by a controller device such as an EMS. For example, if the EVSE advertises a simple power
              * forecast which allows the EMS to adjust over a wide range of power and time durations, then the EVSE may
-             * allow the EMS to propose a revised optimized forecast (which is the charging profile).
+             * allow the EMS to propose a revised optimized forecast (which is the charging profile). For example, a
+             * solar PV ESA may also share its Forecast, so enabling an EMS to adjust the EVSE forecast to the best
+             * time to charge so that any excess solar generation is used to charge the EV.
              *
              * See the Device Energy Management Cluster for more details.
              *
@@ -3432,6 +3661,12 @@ export declare namespace EnergyEvse {
              * If the EVSE can support bi-directional charging, it may be possible to request that the vehicle can
              * discharge to the home or grid.
              *
+             * The charging and discharging may be controlled by a home Energy Management System (EMS) using the Device
+             * Energy Management cluster of the associated Device Energy Management device. For example, an EMS may use
+             * the PA (Power Adjustment) feature to continually adjust the charge/discharge current to/from the EV so
+             * as to minimise the energy flow from/to the grid as the demand in the home and the solar supply to the
+             * home both fluctuate.
+             *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.5
              */
             readonly v2X: BitFlag;
@@ -3548,19 +3783,19 @@ export declare namespace EnergyEvse {
                  * This range requirement can be converted into a daily energy demand with a target charging completion
                  * time.
                  *
-                 * The EVSE itself may use this information (or may allow a controller such as an EMS) to compute an
-                 *
+                 * The EVSE itself can use this information (or may allow a controller such as an EMS) to compute an
                  * optimized charging schedule.
                  *
-                 * An EVSE device may implement the Device Energy Management cluster PFR (Power Forecast Reporting) and FA
-                 * (Forecast Adjustment) features. This can help a controller (such as an EMS) to optimize the EVSE against
-                 * other ESAs. For example, a solar PV ESA may share its Forecast and allow the EVSE to know the best time
-                 * to charge so that any excess solar generation is used to charge the EV.
+                 * An EVSE device which includes a Device Energy Management device with the Device Energy Management
+                 * cluster PFR (Power Forecast Reporting) feature can use the charging preferences information to produce
+                 * its power forecast.
                  *
                  * EVSE devices that support the Device Energy Management cluster’s FA feature can have their charging
                  * profiles set by a controller device such as an EMS. For example, if the EVSE advertises a simple power
                  * forecast which allows the EMS to adjust over a wide range of power and time durations, then the EVSE may
-                 * allow the EMS to propose a revised optimized forecast (which is the charging profile).
+                 * allow the EMS to propose a revised optimized forecast (which is the charging profile). For example, a
+                 * solar PV ESA may also share its Forecast, so enabling an EMS to adjust the EVSE forecast to the best
+                 * time to charge so that any excess solar generation is used to charge the EV.
                  *
                  * See the Device Energy Management Cluster for more details.
                  *
@@ -3615,6 +3850,12 @@ export declare namespace EnergyEvse {
                  * If the EVSE can support bi-directional charging, it may be possible to request that the vehicle can
                  * discharge to the home or grid.
                  *
+                 * The charging and discharging may be controlled by a home Energy Management System (EMS) using the Device
+                 * Energy Management cluster of the associated Device Energy Management device. For example, an EMS may use
+                 * the PA (Power Adjustment) feature to continually adjust the charge/discharge current to/from the EV so
+                 * as to minimise the energy flow from/to the grid as the demand in the home and the solar supply to the
+                 * home both fluctuate.
+                 *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.5
                  */
                 readonly v2X: BitFlag;
@@ -3628,7 +3869,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the expiry time, in UTC, when discharging will be automatically disabled.
                  *
-                 * A value in the past in this field shall disable the EVSE whereas a null value shall enable it permanently.
+                 * A value in the past in this field shall disable the EVSE discharging whereas a null value shall enable EVSE
+                 * discharging permanently.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.1
                  */
@@ -3636,9 +3878,7 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the maximum current that can be received by the EVSE from the EV. The EVSE current
                  * limit can be advertised to an EV in 0.6A steps. The value of the MaximumDischargeCurrent attribute shall be
-                 * stored and persisted across reboots by the EVSE to the value of this
-                 *
-                 * field.
+                 * stored and persisted across reboots by the EVSE to the value of this field.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.3.2
                  */
@@ -3660,7 +3900,13 @@ export declare namespace EnergyEvse {
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                  */
                 chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                    dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                    /**
+                     * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                     * is a bitmap and therefore the associated targets could be applied to multiple days.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                     */
+                    dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                         /**
                          * Sunday
                          */
@@ -3690,7 +3936,12 @@ export declare namespace EnergyEvse {
                          */
                         saturday: BitFlag;
                     }>>;
-                    chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                    /**
+                     * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                     */
+                    chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate the desired charging completion time of the associated day. The time will be
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -3721,7 +3972,7 @@ export declare namespace EnergyEvse {
                          * This field represents the target SoC that the vehicle should be charged to before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * If the EVSE can obtain the SoC of the vehicle:
+                         * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                          *
                          *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                          *
@@ -3731,13 +3982,14 @@ export declare namespace EnergyEvse {
                          *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                          *     vehicle decides to stop charging.
                          *
-                         * If the EVSE cannot obtain the SoC of the vehicle:
+                         * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
                          *
-                         *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                         *     field may only take the values null or 100%.
+                         *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                         *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                          *
-                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                         *     until the vehicle stops demanding a charge.
+                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+                         *
+                         * and charge until the vehicle stops demanding a charge.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                          */
@@ -3758,7 +4010,7 @@ export declare namespace EnergyEvse {
                          *
                          * NOTE
                          *
-                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                          * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                          * battery during charging, or for heating or cooling the cabin.
                          *
@@ -3783,7 +4035,13 @@ export declare namespace EnergyEvse {
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.7.1
                  */
                 chargingTargetSchedules: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
-                    dayOfWeekForSequence: import("../tlv/TlvObject.js").OptionalFieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                    /**
+                     * This field shall indicate the days of the week that the charging targets SHOULD be associated to. This field
+                     * is a bitmap and therefore the associated targets could be applied to multiple days.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.8
+                     */
+                    dayOfWeekForSequence: import("../tlv/TlvObject.js").FieldType<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                         /**
                          * Sunday
                          */
@@ -3813,7 +4071,12 @@ export declare namespace EnergyEvse {
                          */
                         saturday: BitFlag;
                     }>>;
-                    chargingTargets: import("../tlv/TlvObject.js").OptionalFieldType<import("../tlv/TlvObject.js").TypeFromFields<{
+                    /**
+                     * This field shall indicate a list of up to 10 charging targets for each of the associated days of the week.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.9
+                     */
+                    chargingTargets: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate the desired charging completion time of the associated day. The time will be
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
@@ -3844,7 +4107,7 @@ export declare namespace EnergyEvse {
                          * This field represents the target SoC that the vehicle should be charged to before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * If the EVSE can obtain the SoC of the vehicle:
+                         * If the EVSE supports the SOC feature and can obtain the SoC of the vehicle:
                          *
                          *   • the TargetSoC field shall take precedence over the AddedEnergy field.
                          *
@@ -3854,13 +4117,14 @@ export declare namespace EnergyEvse {
                          *   • if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the
                          *     vehicle decides to stop charging.
                          *
-                         * If the EVSE cannot obtain the SoC of the vehicle:
+                         * If the EVSE does not support the SOC feature or cannot obtain the SoC of the vehicle:
                          *
-                         *   • in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC
-                         *     field may only take the values null or 100%.
+                         *   • the AddedEnergy field shall take precedence over the TargetSoC field, and if the EVSE does not support
+                         *     the SOC feature then the TargetSoC field may only take the values null or 100%.
                          *
-                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge
-                         *     until the vehicle stops demanding a charge.
+                         *   • if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty
+                         *
+                         * and charge until the vehicle stops demanding a charge.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.2
                          */
@@ -3881,7 +4145,7 @@ export declare namespace EnergyEvse {
                          *
                          * NOTE
                          *
-                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to
+                         * If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD NOT limit this AddedEnergy value to
                          * the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the
                          * battery during charging, or for heating or cooling the cabin.
                          *
@@ -3913,7 +4177,8 @@ export declare namespace EnergyEvse {
              */
             readonly disable: Command<void, void, any>;
             /**
-             * Allows a client to enable the EVSE to charge an EV.
+             * This command allows a client to enable the EVSE to charge an EV, and to provide or update the maximum
+             * and minimum charge current.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.2
              */
@@ -3942,10 +4207,9 @@ export declare namespace EnergyEvse {
                  * limit can be advertised to an EV in 0.6A steps.
                  *
                  * The value of the this field shall be stored by the EVSE to determine the value of MaximumChargeCurrent
-                 * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then
-                 *
-                 * this value, and then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be
-                 * limited to this value.
+                 * attribute. For example, if the UserMaximumChargeCurrent attribute is adjusted below then this value, and
+                 * then later adjusted above this value, the resulting MaximumChargeCurrent attribute will be limited to this
+                 * value.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.2.3
                  */
@@ -4015,7 +4279,6 @@ export declare namespace EnergyEvse {
                 sessionDuration: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
                  * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
-                 * This value shall always be positive.
                  *
                  * Note that if bi-directional charging occurs during the session, then this value shall only include the sum
                  * of energy transferred from the EVSE to the EV, and shall NOT be a net value of charging and discharging
@@ -4026,7 +4289,6 @@ export declare namespace EnergyEvse {
                 sessionEnergyCharged: import("../tlv/TlvObject.js").FieldType<number | bigint>;
                 /**
                  * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
-                 * This value shall always be positive.
                  *
                  * Note that if bi-directional discharging occurs during the session, then this value shall only include the
                  * sum of energy transferred from the EV to the EVSE, and shall NOT be a net value of charging and discharging
@@ -4037,7 +4299,9 @@ export declare namespace EnergyEvse {
                 sessionEnergyDischarged: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
-             * This event shall be generated when the EV starts charging or discharging.
+             * This event shall be generated whenever the EV starts charging or discharging, except when an EV has
+             * switched between charging and discharging under the control of the PowerAdjustment feature of the Device
+             * Energy Management cluster of the associated Device Energy Management device.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3
              */
@@ -4055,22 +4319,29 @@ export declare namespace EnergyEvse {
                  */
                 state: import("../tlv/TlvObject.js").FieldType<State>;
                 /**
-                 * This field shall indicate the value of the maximum charging or discharging current at the time the event was
-                 * generated.
+                 * This field shall indicate the value of the maximum charging current at the time the event was generated.
                  *
-                 * This field is signed. A positive value indicates the EV has been enabled for charging and the value is taken
-                 * directly from the MaximumChargeCurrent attribute.
-                 *
-                 * A negative value indicates that the EV has been enabled for discharging and the value can be taken from the
-                 * MaximumDischargeCurrent attribute with its sign inverted. i.e. if the MaximumDischargeCurrent was 32000mA,
-                 * this would be represented here as -32000mA.
+                 * A non-zero value indicates that the EV has been enabled for charging and the value is taken directly from
+                 * the MaximumChargeCurrent attribute. A zero value indicates that the EV has not been enabled for charging.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.3
                  */
                 maximumCurrent: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+                /**
+                 * This field shall indicate the value of the maximum discharging current at the time the event was generated.
+                 *
+                 * A non-zero value indicates that the EV has been enabled for discharging and the value is taken directly from
+                 * the MaximumDischargeCurrent attribute. A zero value indicates that the EV has not been enabled for
+                 * discharging.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.3.4
+                 */
+                maximumDischargeCurrent: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
-             * This event shall be generated when the EV stops charging or discharging.
+             * This event shall be generated whenever the EV stops charging or discharging, except when an EV has
+             * switched between charging and discharging under the control of the PowerAdjustment feature of the Device
+             * Energy Management cluster of the associated Device Energy Management device.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4
              */
@@ -4093,7 +4364,20 @@ export declare namespace EnergyEvse {
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.3
                  */
                 reason: import("../tlv/TlvObject.js").FieldType<EnergyTransferStoppedReason>;
+                /**
+                 * This field shall indicate the amount of energy transferred from the EVSE to the EV since the previous
+                 * EnergyTransferStarted event, in mWh.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.4
+                 */
                 energyTransferred: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+                /**
+                 * This field shall indicate the amount of energy transferred from the EV to the EVSE since the previous
+                 * EnergyTransferStarted event, in mWh.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.4.5
+                 */
+                energyDischarged: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, any>;
             /**
              * If the EVSE detects a fault it shall generate a Fault Event. The SupplyState attribute shall be set to