@matter/types 0.13.0-alpha.0-20250318-c1aa38b08 → 0.13.0-alpha.0-20250323-770919c6a

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

@@ -27,8 +27,8 @@ export declare namespace EnergyEvse {
          * 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 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
+         * 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
@@ -63,8 +63,8 @@ export declare namespace EnergyEvse {
          * PlugAndCharge (PNC)
          *
          * If the EVSE supports PLC, it may be able to support the Plug and Charge feature. e.g. this may allow the
-         * vehicle ID to be obtained which may allow an energy management system to track energy usage per vehicle
-         * (e.g. to give the owner an indicative cost of charging, or for work place charging).
+         * vehicle ID to be obtained which may allow an energy management system to track energy usage per vehicle (e.g.
+         * to give the owner an indicative cost of charging, or for work place charging).
          *
          * If the EVSE supports the Plug and Charge feature, it will only work if a compatible EV is connected.
          *
@@ -88,8 +88,8 @@ export declare namespace EnergyEvse {
         /**
          * V2X (V2X)
          *
-         * If the EVSE can support bi-directional charging, it may be possible to request that the vehicle can
-         * discharge to the home or grid.
+         * 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
@@ -187,8 +187,8 @@ export declare namespace EnergyEvse {
          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
          * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
          *
-         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-         * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+         * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
          * appropriately.
          *
          * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -238,21 +238,21 @@ export declare namespace EnergyEvse {
          * This field represents the amount of energy that the user would like to have added to the vehicle before the
          * TargetTimeMinutesPastMidnight.
          *
-         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-         * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-         * plugged in).
+         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+         * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+         * in).
          *
          * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-         * set this value too high then the EVSE will need to start charging immediately and continue charging until
-         * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-         * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-         * carefully choose a value.
+         * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+         * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+         * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+         * choose a value.
          *
          * NOTE
          *
-         * 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.
+         * 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.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
          */
@@ -329,8 +329,8 @@ export declare namespace EnergyEvse {
              * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
              * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
              *
-             * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-             * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+             * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+             * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
              * appropriately.
              *
              * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -380,21 +380,21 @@ export declare namespace EnergyEvse {
              * This field represents the amount of energy that the user would like to have added to the vehicle before the
              * TargetTimeMinutesPastMidnight.
              *
-             * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-             * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-             * plugged in).
+             * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+             * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+             * in).
              *
              * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-             * set this value too high then the EVSE will need to start charging immediately and continue charging until
-             * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-             * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-             * carefully choose a value.
+             * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+             * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+             * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+             * choose a value.
              *
              * NOTE
              *
-             * 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.
+             * 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.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
              */
@@ -416,8 +416,8 @@ export declare namespace EnergyEvse {
     const TlvSetTargetsRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall indicate a list of up to 7 sets of daily charging targets together with their associated
-         * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule
-         * within this list field.
+         * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule within
+         * this list field.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
          */
@@ -469,8 +469,8 @@ export declare namespace EnergyEvse {
                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                  * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                  *
-                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                 * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                 * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                  * appropriately.
                  *
                  * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -520,21 +520,21 @@ export declare namespace EnergyEvse {
                  * This field represents the amount of energy that the user would like to have added to the vehicle before the
                  * TargetTimeMinutesPastMidnight.
                  *
-                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                 * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                 * plugged in).
+                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                 * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                 * in).
                  *
                  * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                 * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                 * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                 * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                 * carefully choose a value.
+                 * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                 * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                 * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                 * choose a value.
                  *
                  * NOTE
                  *
-                 * 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.
+                 * 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.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                  */
@@ -609,8 +609,8 @@ export declare namespace EnergyEvse {
                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                  * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                  *
-                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                 * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                 * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                  * appropriately.
                  *
                  * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -660,21 +660,21 @@ export declare namespace EnergyEvse {
                  * This field represents the amount of energy that the user would like to have added to the vehicle before the
                  * TargetTimeMinutesPastMidnight.
                  *
-                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                 * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                 * plugged in).
+                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                 * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                 * in).
                  *
                  * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                 * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                 * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                 * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                 * carefully choose a value.
+                 * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                 * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                 * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                 * choose a value.
                  *
                  * NOTE
                  *
-                 * 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.
+                 * 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.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                  */
@@ -875,9 +875,8 @@ 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
          */
@@ -938,9 +937,8 @@ export declare namespace EnergyEvse {
         /**
          * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
          *
-         * 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
-         * energy.
+         * 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 energy.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.4
          */
@@ -948,8 +946,8 @@ export declare namespace EnergyEvse {
         /**
          * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
          *
-         * 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
+         * 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
          * energy.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.5
@@ -984,8 +982,8 @@ export declare namespace EnergyEvse {
         /**
          * This field shall indicate the value of the maximum charging current at the time the event was generated.
          *
-         * 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.
+         * 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
          */
@@ -1123,8 +1121,8 @@ export declare namespace EnergyEvse {
              * A value in the past or 0x0 indicates that EVSE discharging shall be disabled. The attribute is only set
              * via the payload of the EnableDischarging command.
              *
-             * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle
-             * from being discharged.
+             * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle from
+             * being discharged.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.5
              */
@@ -1194,8 +1192,8 @@ export declare namespace EnergyEvse {
              */
             readonly nextChargeStartTime: Attribute<number | null, any>;
             /**
-             * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the
-             * charging preferences.
+             * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the charging
+             * preferences.
              *
              * 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
@@ -1271,8 +1269,8 @@ export declare namespace EnergyEvse {
             readonly setTargets: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall indicate a list of up to 7 sets of daily charging targets together with their associated
-                 * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule
-                 * within this list field.
+                 * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule within
+                 * this list field.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                  */
@@ -1324,8 +1322,8 @@ export declare namespace EnergyEvse {
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                          * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                          *
-                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                         * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                         * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                          * appropriately.
                          *
                          * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -1375,21 +1373,21 @@ export declare namespace EnergyEvse {
                          * This field represents the amount of energy that the user would like to have added to the vehicle before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                         * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                         * plugged in).
+                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                         * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                         * in).
                          *
                          * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                         * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                         * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                         * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                         * carefully choose a value.
+                         * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                         * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                         * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                         * choose a value.
                          *
                          * NOTE
                          *
-                         * 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.
+                         * 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.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                          */
@@ -1457,8 +1455,8 @@ export declare namespace EnergyEvse {
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                          * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                          *
-                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                         * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                         * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                          * appropriately.
                          *
                          * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -1508,21 +1506,21 @@ export declare namespace EnergyEvse {
                          * This field represents the amount of energy that the user would like to have added to the vehicle before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                         * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                         * plugged in).
+                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                         * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                         * in).
                          *
                          * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                         * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                         * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                         * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                         * carefully choose a value.
+                         * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                         * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                         * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                         * choose a value.
                          *
                          * NOTE
                          *
-                         * 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.
+                         * 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.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                          */
@@ -1545,9 +1543,9 @@ export declare namespace EnergyEvse {
         readonly attributes: {
             /**
              * Indicates the state of charge of the EV battery in steps of 1%. The values are in the 0-100%. This
-             * attribute is only available on EVSEs which can read the state of charge from the vehicle and that
-             * support the SOC feature. If the StateOfCharge cannot be read from the vehicle it shall be returned with
-             * a NULL value.
+             * attribute is only available on EVSEs which can read the state of charge from the vehicle and that support
+             * the SOC feature. If the StateOfCharge cannot be read from the vehicle it shall be returned with a NULL
+             * value.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.17
              */
@@ -1609,25 +1607,24 @@ export declare namespace EnergyEvse {
             /**
              * ChargingPreferences
              *
-             * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer
-             * to specify a daily charging target (for adding energy to the EV’s battery). This feature allows the
-             * consumer to 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.
+             * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer to
+             * specify a daily charging target (for adding energy to the EV’s battery). This feature allows the consumer
+             * to 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 can use this information (or may allow a controller such as an EMS) to compute an
              * optimized charging schedule.
              *
-             * 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.
+             * 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). 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.
+             * 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.
              *
@@ -1644,8 +1641,8 @@ export declare namespace EnergyEvse {
              * If the EVSE supports reporting of State of Charge this feature will only work if a compatible EV is
              * connected.
              *
-             * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope
-             * of this cluster.
+             * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope of
+             * this cluster.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.2
              */
@@ -1684,9 +1681,9 @@ export declare namespace EnergyEvse {
              *
              * 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.
+             * 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
              */
@@ -1736,8 +1733,8 @@ export declare namespace EnergyEvse {
              * A value in the past or 0x0 indicates that EVSE charging shall be disabled. The attribute is only set via
              * the payload of the EnableCharging command.
              *
-             * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle
-             * from being charged.
+             * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle from
+             * being charged.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.4
              */
@@ -1784,8 +1781,8 @@ export declare namespace EnergyEvse {
             /**
              * Indicates a maximum current that can set by the consumer (e.g. via an app) as a preference to further
              * reduce the charging rate. This may be desirable if the home owner has a solar PV or battery storage
-             * system which may only be able to deliver a limited amount of power. The consumer can manually control
-             * how much they allow the EV to take.
+             * system which may only be able to deliver a limited amount of power. The consumer can manually control how
+             * much they allow the EV to take.
              *
              * This attribute value shall be limited by the EVSE to be in the range of:
              *
@@ -1794,15 +1791,15 @@ export declare namespace EnergyEvse {
              * where MinimumChargeCurrent and MaximumChargeCurrent are the values received in the EnableCharging
              * command.
              *
-             * Its default value SHOULD be initialized to the same as the CircuitCapacity attribute. This value shall
-             * be persisted across reboots to ensure it does not cause charging issues during temporary power failures.
+             * Its default value SHOULD be initialized to the same as the CircuitCapacity attribute. This value shall be
+             * persisted across reboots to ensure it does not cause charging issues during temporary power failures.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.10
              */
             readonly userMaximumChargeCurrent: OptionalWritableAttribute<number | bigint, any>;
             /**
-             * Indicates the size of a random window over which the EVSE will randomize the start of a charging
-             * session. This value is in seconds.
+             * Indicates the size of a random window over which the EVSE will randomize the start of a charging session.
+             * This value is in seconds.
              *
              * This is a feature that is mandated in some markets (such as UK) where the EVSE should by default
              * randomize its start time within the randomization window. By default in the UK this should be 600s.
@@ -1835,8 +1832,8 @@ export declare namespace EnergyEvse {
              */
             readonly disable: Command<void, void, any>;
             /**
-             * This command allows a client to enable the EVSE to charge an EV, and to provide or update the maximum
-             * and minimum charge current.
+             * 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
              */
@@ -1865,9 +1862,8 @@ 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
                  */
@@ -1923,9 +1919,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
                  *
-                 * 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
-                 * energy.
+                 * 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 energy.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.4
                  */
@@ -1933,8 +1928,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
                  *
-                 * 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
+                 * 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
                  * energy.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.5
@@ -1964,8 +1959,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the value of the maximum charging current at the time the event was generated.
                  *
-                 * 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.
+                 * 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
                  */
@@ -2081,8 +2076,8 @@ export declare namespace EnergyEvse {
                      * A value in the past or 0x0 indicates that EVSE discharging shall be disabled. The attribute is only set
                      * via the payload of the EnableDischarging command.
                      *
-                     * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle
-                     * from being discharged.
+                     * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle from
+                     * being discharged.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.5
                      */
@@ -2153,8 +2148,8 @@ export declare namespace EnergyEvse {
                      */
                     readonly nextChargeStartTime: Attribute<number | null, any>;
                     /**
-                     * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the
-                     * charging preferences.
+                     * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the charging
+                     * preferences.
                      *
                      * 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
@@ -2230,8 +2225,8 @@ export declare namespace EnergyEvse {
                     readonly setTargets: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate a list of up to 7 sets of daily charging targets together with their associated
-                         * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule
-                         * within this list field.
+                         * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule within
+                         * this list field.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                          */
@@ -2283,8 +2278,8 @@ export declare namespace EnergyEvse {
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                                  * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                                  *
-                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                                 * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                                 * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                                  * appropriately.
                                  *
                                  * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -2334,21 +2329,21 @@ export declare namespace EnergyEvse {
                                  * This field represents the amount of energy that the user would like to have added to the vehicle before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                                 * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                                 * plugged in).
+                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                                 * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                                 * in).
                                  *
                                  * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                                 * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                                 * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                                 * carefully choose a value.
+                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                                 * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                                 * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                                 * choose a value.
                                  *
                                  * NOTE
                                  *
-                                 * 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.
+                                 * 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.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                                  */
@@ -2416,8 +2411,8 @@ export declare namespace EnergyEvse {
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                                  * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                                  *
-                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                                 * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                                 * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                                  * appropriately.
                                  *
                                  * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -2467,21 +2462,21 @@ export declare namespace EnergyEvse {
                                  * This field represents the amount of energy that the user would like to have added to the vehicle before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                                 * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                                 * plugged in).
+                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                                 * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                                 * in).
                                  *
                                  * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                                 * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                                 * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                                 * carefully choose a value.
+                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                                 * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                                 * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                                 * choose a value.
                                  *
                                  * NOTE
                                  *
-                                 * 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.
+                                 * 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.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                                  */
@@ -2505,9 +2500,9 @@ export declare namespace EnergyEvse {
                 readonly attributes: {
                     /**
                      * Indicates the state of charge of the EV battery in steps of 1%. The values are in the 0-100%. This
-                     * attribute is only available on EVSEs which can read the state of charge from the vehicle and that
-                     * support the SOC feature. If the StateOfCharge cannot be read from the vehicle it shall be returned with
-                     * a NULL value.
+                     * attribute is only available on EVSEs which can read the state of charge from the vehicle and that support
+                     * the SOC feature. If the StateOfCharge cannot be read from the vehicle it shall be returned with a NULL
+                     * value.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.17
                      */
@@ -2578,25 +2573,24 @@ export declare namespace EnergyEvse {
             /**
              * ChargingPreferences
              *
-             * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer
-             * to specify a daily charging target (for adding energy to the EV’s battery). This feature allows the
-             * consumer to 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.
+             * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer to
+             * specify a daily charging target (for adding energy to the EV’s battery). This feature allows the consumer
+             * to 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 can use this information (or may allow a controller such as an EMS) to compute an
              * optimized charging schedule.
              *
-             * 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.
+             * 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). 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.
+             * 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.
              *
@@ -2613,8 +2607,8 @@ export declare namespace EnergyEvse {
              * If the EVSE supports reporting of State of Charge this feature will only work if a compatible EV is
              * connected.
              *
-             * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope
-             * of this cluster.
+             * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope of
+             * this cluster.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.2
              */
@@ -2653,9 +2647,9 @@ export declare namespace EnergyEvse {
              *
              * 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.
+             * 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
              */
@@ -2705,8 +2699,8 @@ export declare namespace EnergyEvse {
              * A value in the past or 0x0 indicates that EVSE charging shall be disabled. The attribute is only set via
              * the payload of the EnableCharging command.
              *
-             * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle
-             * from being charged.
+             * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle from
+             * being charged.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.4
              */
@@ -2753,8 +2747,8 @@ export declare namespace EnergyEvse {
             /**
              * Indicates a maximum current that can set by the consumer (e.g. via an app) as a preference to further
              * reduce the charging rate. This may be desirable if the home owner has a solar PV or battery storage
-             * system which may only be able to deliver a limited amount of power. The consumer can manually control
-             * how much they allow the EV to take.
+             * system which may only be able to deliver a limited amount of power. The consumer can manually control how
+             * much they allow the EV to take.
              *
              * This attribute value shall be limited by the EVSE to be in the range of:
              *
@@ -2763,15 +2757,15 @@ export declare namespace EnergyEvse {
              * where MinimumChargeCurrent and MaximumChargeCurrent are the values received in the EnableCharging
              * command.
              *
-             * Its default value SHOULD be initialized to the same as the CircuitCapacity attribute. This value shall
-             * be persisted across reboots to ensure it does not cause charging issues during temporary power failures.
+             * Its default value SHOULD be initialized to the same as the CircuitCapacity attribute. This value shall be
+             * persisted across reboots to ensure it does not cause charging issues during temporary power failures.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.10
              */
             readonly userMaximumChargeCurrent: OptionalWritableAttribute<number | bigint, any>;
             /**
-             * Indicates the size of a random window over which the EVSE will randomize the start of a charging
-             * session. This value is in seconds.
+             * Indicates the size of a random window over which the EVSE will randomize the start of a charging session.
+             * This value is in seconds.
              *
              * This is a feature that is mandated in some markets (such as UK) where the EVSE should by default
              * randomize its start time within the randomization window. By default in the UK this should be 600s.
@@ -2804,8 +2798,8 @@ export declare namespace EnergyEvse {
              */
             readonly disable: Command<void, void, any>;
             /**
-             * This command allows a client to enable the EVSE to charge an EV, and to provide or update the maximum
-             * and minimum charge current.
+             * 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
              */
@@ -2834,9 +2828,8 @@ 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
                  */
@@ -2892,9 +2885,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
                  *
-                 * 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
-                 * energy.
+                 * 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 energy.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.4
                  */
@@ -2902,8 +2894,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
                  *
-                 * 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
+                 * 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
                  * energy.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.5
@@ -2933,8 +2925,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the value of the maximum charging current at the time the event was generated.
                  *
-                 * 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.
+                 * 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
                  */
@@ -3050,8 +3042,8 @@ export declare namespace EnergyEvse {
                      * A value in the past or 0x0 indicates that EVSE discharging shall be disabled. The attribute is only set
                      * via the payload of the EnableDischarging command.
                      *
-                     * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle
-                     * from being discharged.
+                     * This attribute shall be persisted, for example a temporary power failure should not stop the vehicle from
+                     * being discharged.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.5
                      */
@@ -3122,8 +3114,8 @@ export declare namespace EnergyEvse {
                      */
                     readonly nextChargeStartTime: Attribute<number | null, any>;
                     /**
-                     * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the
-                     * charging preferences.
+                     * Indicates the time, in UTC, when the EVSE SHOULD complete the next scheduled charge based on the charging
+                     * preferences.
                      *
                      * 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
@@ -3199,8 +3191,8 @@ export declare namespace EnergyEvse {
                     readonly setTargets: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         /**
                          * This field shall indicate a list of up to 7 sets of daily charging targets together with their associated
-                         * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule
-                         * within this list field.
+                         * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule within
+                         * this list field.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                          */
@@ -3252,8 +3244,8 @@ export declare namespace EnergyEvse {
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                                  * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                                  *
-                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                                 * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                                 * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                                  * appropriately.
                                  *
                                  * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -3303,21 +3295,21 @@ export declare namespace EnergyEvse {
                                  * This field represents the amount of energy that the user would like to have added to the vehicle before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                                 * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                                 * plugged in).
+                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                                 * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                                 * in).
                                  *
                                  * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                                 * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                                 * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                                 * carefully choose a value.
+                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                                 * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                                 * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                                 * choose a value.
                                  *
                                  * NOTE
                                  *
-                                 * 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.
+                                 * 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.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                                  */
@@ -3385,8 +3377,8 @@ export declare namespace EnergyEvse {
                                  * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                                  * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                                  *
-                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                                 * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                                 * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                                 * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                                  * appropriately.
                                  *
                                  * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -3436,21 +3428,21 @@ export declare namespace EnergyEvse {
                                  * This field represents the amount of energy that the user would like to have added to the vehicle before the
                                  * TargetTimeMinutesPastMidnight.
                                  *
-                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                                 * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                                 * plugged in).
+                                 * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                                 * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                                 * in).
                                  *
                                  * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                                 * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                                 * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                                 * carefully choose a value.
+                                 * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                                 * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                                 * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                                 * choose a value.
                                  *
                                  * NOTE
                                  *
-                                 * 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.
+                                 * 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.
                                  *
                                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                                  */
@@ -3474,9 +3466,9 @@ export declare namespace EnergyEvse {
                 readonly attributes: {
                     /**
                      * Indicates the state of charge of the EV battery in steps of 1%. The values are in the 0-100%. This
-                     * attribute is only available on EVSEs which can read the state of charge from the vehicle and that
-                     * support the SOC feature. If the StateOfCharge cannot be read from the vehicle it shall be returned with
-                     * a NULL value.
+                     * attribute is only available on EVSEs which can read the state of charge from the vehicle and that support
+                     * the SOC feature. If the StateOfCharge cannot be read from the vehicle it shall be returned with a NULL
+                     * value.
                      *
                      * @see {@link MatterSpecification.v13.Cluster} § 9.3.8.17
                      */
@@ -3566,8 +3558,8 @@ export declare namespace EnergyEvse {
      * managed by backend system and outside scope of this cluster.
      *
      * Note that in many deployments the EVSE may be outside the home and may suffer from intermittent network
-     * connections (e.g. a weak WiFi signal). It also allows for a charging profile to be pre- configured, in case
-     * there is a temporary communications loss during a charging session.
+     * connections (e.g. a weak WiFi signal). It also allows for a charging profile to be pre- configured, in case there
+     * is a temporary communications loss during a charging session.
      *
      * EnergyEvseCluster supports optional features that you can enable with the EnergyEvseCluster.with() factory
      * method.
@@ -3588,25 +3580,24 @@ export declare namespace EnergyEvse {
             /**
              * ChargingPreferences
              *
-             * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer
-             * to specify a daily charging target (for adding energy to the EV’s battery). This feature allows the
-             * consumer to 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.
+             * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer to
+             * specify a daily charging target (for adding energy to the EV’s battery). This feature allows the consumer
+             * to 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 can use this information (or may allow a controller such as an EMS) to compute an
              * optimized charging schedule.
              *
-             * 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.
+             * 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). 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.
+             * 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.
              *
@@ -3623,8 +3614,8 @@ export declare namespace EnergyEvse {
              * If the EVSE supports reporting of State of Charge this feature will only work if a compatible EV is
              * connected.
              *
-             * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope
-             * of this cluster.
+             * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope of
+             * this cluster.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.2
              */
@@ -3663,9 +3654,9 @@ export declare namespace EnergyEvse {
              *
              * 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.
+             * 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
              */
@@ -3777,25 +3768,24 @@ export declare namespace EnergyEvse {
                 /**
                  * ChargingPreferences
                  *
-                 * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer
-                 * to specify a daily charging target (for adding energy to the EV’s battery). This feature allows the
-                 * consumer to 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.
+                 * Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer to
+                 * specify a daily charging target (for adding energy to the EV’s battery). This feature allows the consumer
+                 * to 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 can use this information (or may allow a controller such as an EMS) to compute an
                  * optimized charging schedule.
                  *
-                 * 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.
+                 * 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). 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.
+                 * 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.
                  *
@@ -3812,8 +3802,8 @@ export declare namespace EnergyEvse {
                  * If the EVSE supports reporting of State of Charge this feature will only work if a compatible EV is
                  * connected.
                  *
-                 * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope
-                 * of this cluster.
+                 * Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope of
+                 * this cluster.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.4.2
                  */
@@ -3852,9 +3842,9 @@ export declare namespace EnergyEvse {
                  *
                  * 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.
+                 * 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
                  */
@@ -3894,8 +3884,8 @@ export declare namespace EnergyEvse {
             readonly setTargets: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall indicate a list of up to 7 sets of daily charging targets together with their associated
-                 * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule
-                 * within this list field.
+                 * days of the week. Each of the days of the week may only be included in a single ChargingTargetSchedule within
+                 * this list field.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.9.5.1
                  */
@@ -3947,8 +3937,8 @@ export declare namespace EnergyEvse {
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                          * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                          *
-                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                         * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                         * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                          * appropriately.
                          *
                          * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -3998,21 +3988,21 @@ export declare namespace EnergyEvse {
                          * This field represents the amount of energy that the user would like to have added to the vehicle before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                         * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                         * plugged in).
+                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                         * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                         * in).
                          *
                          * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                         * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                         * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                         * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                         * carefully choose a value.
+                         * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                         * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                         * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                         * choose a value.
                          *
                          * NOTE
                          *
-                         * 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.
+                         * 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.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                          */
@@ -4082,8 +4072,8 @@ export declare namespace EnergyEvse {
                          * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
                          * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
                          *
-                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result
-                         * in an extra hour or one hour less in the day, the charging algorithm should take into account the shift
+                         * This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in
+                         * an extra hour or one hour less in the day, the charging algorithm should take into account the shift
                          * appropriately.
                          *
                          * Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may
@@ -4133,21 +4123,21 @@ export declare namespace EnergyEvse {
                          * This field represents the amount of energy that the user would like to have added to the vehicle before the
                          * TargetTimeMinutesPastMidnight.
                          *
-                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle
-                         * charging is stopped and started several times, this equates to the total energy since the vehicle has been
-                         * plugged in).
+                         * This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging
+                         * is stopped and started several times, this equates to the total energy since the vehicle has been plugged
+                         * in).
                          *
                          * The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to
-                         * set this value too high then the EVSE will need to start charging immediately and continue charging until
-                         * the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on
-                         * typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to
-                         * carefully choose a value.
+                         * set this value too high then the EVSE will need to start charging immediately and continue charging until the
+                         * vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical
+                         * battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully
+                         * choose a value.
                          *
                          * NOTE
                          *
-                         * 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.
+                         * 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.
                          *
                          * @see {@link MatterSpecification.v13.Cluster} § 9.3.7.6.3
                          */
@@ -4177,8 +4167,8 @@ export declare namespace EnergyEvse {
              */
             readonly disable: Command<void, void, any>;
             /**
-             * This command allows a client to enable the EVSE to charge an EV, and to provide or update the maximum
-             * and minimum charge current.
+             * 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
              */
@@ -4207,9 +4197,8 @@ 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
                  */
@@ -4280,9 +4269,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the total amount of energy transferred from the EVSE to the EV during the session.
                  *
-                 * 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
-                 * energy.
+                 * 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 energy.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.4
                  */
@@ -4290,8 +4278,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the total amount of energy transferred from the EV to the EVSE during the session.
                  *
-                 * 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
+                 * 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
                  * energy.
                  *
                  * @see {@link MatterSpecification.v13.Cluster} § 9.3.10.2.5
@@ -4321,8 +4309,8 @@ export declare namespace EnergyEvse {
                 /**
                  * This field shall indicate the value of the maximum charging current at the time the event was generated.
                  *
-                 * 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.
+                 * 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
                  */
@@ -4424,8 +4412,8 @@ export declare namespace EnergyEvse {
     /**
      * This cluster supports all EnergyEvse features. It may support illegal feature combinations.
      *
-     * If you use this cluster you must manually specify which features are active and ensure the set of active
-     * features is legal per the Matter specification.
+     * If you use this cluster you must manually specify which features are active and ensure the set of active features
+     * is legal per the Matter specification.
      */
     interface Complete extends Identity<typeof CompleteInstance> {
     }