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

package/src/clusters/energy-evse.ts

@@ -56,8 +56,8 @@ export 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
@@ -94,8 +94,8 @@ export 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.
          *
@@ -121,8 +121,8 @@ export 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
@@ -230,8 +230,8 @@ export 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
@@ -283,21 +283,21 @@ export 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
          */
@@ -359,8 +359,8 @@ export namespace EnergyEvse {
     export const TlvSetTargetsRequest = TlvObject({
         /**
          * 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
          */
@@ -615,9 +615,8 @@ export 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
          */
@@ -683,9 +682,8 @@ export 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
          */
@@ -694,8 +692,8 @@ export 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
@@ -733,8 +731,8 @@ export 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
          */
@@ -886,8 +884,8 @@ export 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
              */
@@ -948,8 +946,8 @@ export namespace EnergyEvse {
             nextChargeStartTime: Attribute(0x23, TlvNullable(TlvEpochS), { default: null }),
 
             /**
-             * 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
@@ -1055,9 +1053,9 @@ export namespace EnergyEvse {
         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
              */
@@ -1117,25 +1115,24 @@ export 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.
              *
@@ -1153,8 +1150,8 @@ export 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
              */
@@ -1196,9 +1193,9 @@ export 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
              */
@@ -1252,8 +1249,8 @@ export 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
              */
@@ -1304,8 +1301,8 @@ export 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:
              *
@@ -1314,8 +1311,8 @@ export 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
              */
@@ -1326,8 +1323,8 @@ export namespace EnergyEvse {
             ),
 
             /**
-             * 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.
@@ -1373,8 +1370,8 @@ export namespace EnergyEvse {
             disable: Command(0x1, TlvNoArguments, 0x1, TlvNoResponse, { timed: true }),
 
             /**
-             * 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
              */
@@ -1487,8 +1484,8 @@ export 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.
@@ -1590,8 +1587,8 @@ export 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.
      */
     export interface Complete extends Identity<typeof CompleteInstance> {}
 

package/src/clusters/energy-preference.ts

@@ -37,9 +37,9 @@ export namespace EnergyPreference {
         /**
          * LowPowerModeSensitivity (LPMS)
          *
-         * This feature allows the user to select a condition or set of conditions which will cause the device to
-         * switch to a mode using less power. For example, a device might provide a scale of durations that must elapse
-         * without user interaction before it goes to sleep.
+         * This feature allows the user to select a condition or set of conditions which will cause the device to switch
+         * to a mode using less power. For example, a device might provide a scale of durations that must elapse without
+         * user interaction before it goes to sleep.
          *
          * @see {@link MatterSpecification.v13.Cluster} § 9.7.4.2
          */
@@ -119,10 +119,10 @@ export namespace EnergyPreference {
     export const EnergyBalanceComponent = MutableCluster.Component({
         attributes: {
             /**
-             * Indicates a list of BalanceStructs, each representing a step along a linear scale of relative
-             * priorities. A Step field with a value of zero shall indicate that the device SHOULD entirely favor the
-             * priority specified by the first element in EnergyPriorities; whereas a Step field with a value of 100
-             * shall indicate that the device SHOULD entirely favor the priority specified by the second element in
+             * Indicates a list of BalanceStructs, each representing a step along a linear scale of relative priorities.
+             * A Step field with a value of zero shall indicate that the device SHOULD entirely favor the priority
+             * specified by the first element in EnergyPriorities; whereas a Step field with a value of 100 shall
+             * indicate that the device SHOULD entirely favor the priority specified by the second element in
              * EnergyPriorities. The midpoint value of 50 shall indicate an even split between the two priorities.
              *
              * This shall contain at least two BalanceStructs.
@@ -193,8 +193,8 @@ export namespace EnergyPreference {
 
             /**
              * Indicates the current preference of the user for determining when the device should enter a low power
-             * mode. The value of this attribute is the index, 0-based, into the LowPowerModeSensitivities attribute
-             * for the currently selected preference.
+             * mode. The value of this attribute is the index, 0-based, into the LowPowerModeSensitivities attribute for
+             * the currently selected preference.
              *
              * If an attempt is made to set this attribute to an index outside the maximum index for
              * LowPowerModeSensitivities, a response with the status code CONSTRAINT_ERROR shall be returned.
@@ -221,8 +221,8 @@ export namespace EnergyPreference {
             /**
              * EnergyBalance
              *
-             * This feature allows a user to select from a list of energy balances with associated descriptions of
-             * which strategies a device will use to target the specified balance.
+             * This feature allows a user to select from a list of energy balances with associated descriptions of which
+             * strategies a device will use to target the specified balance.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 9.7.4.1
              */
@@ -308,8 +308,8 @@ export namespace EnergyPreference {
     /**
      * This cluster supports all EnergyPreference 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.
      */
     export interface Complete extends Identity<typeof CompleteInstance> {}
 

package/src/clusters/ethernet-network-diagnostics.ts

@@ -224,8 +224,8 @@ export namespace EthernetNetworkDiagnostics {
 
             /**
              * The CarrierDetect attribute shall indicate the value of the Carrier Detect control signal present on the
-             * ethernet network interface. A value of null shall indicate that the interface is not currently
-             * configured or operational.
+             * ethernet network interface. A value of null shall indicate that the interface is not currently configured
+             * or operational.
              *
              * @see {@link MatterSpecification.v13.Core} § 11.16.6.8
              */
@@ -258,8 +258,8 @@ export namespace EthernetNetworkDiagnostics {
     export const ClusterInstance = MutableCluster(Base);
 
     /**
-     * The Ethernet Network Diagnostics Cluster provides a means to acquire standardized diagnostics metrics that may
-     * be used by a Node to assist a user or Administrator in diagnosing potential problems. The Ethernet Network
+     * The Ethernet Network Diagnostics Cluster provides a means to acquire standardized diagnostics metrics that may be
+     * used by a Node to assist a user or Administrator in diagnosing potential problems. The Ethernet Network
      * Diagnostics Cluster attempts to centralize all metrics that are relevant to a potential Ethernet connection to a
      * Node.
      *
@@ -318,8 +318,8 @@ export namespace EthernetNetworkDiagnostics {
     /**
      * This cluster supports all EthernetNetworkDiagnostics 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.
      */
     export interface Complete extends Identity<typeof CompleteInstance> {}
 

package/src/clusters/fan-control.ts

@@ -272,8 +272,8 @@ export namespace FanControl {
     export const MultiSpeedComponent = MutableCluster.Component({
         attributes: {
             /**
-             * Indicates that the fan has one speed (value of 1) or the maximum speed, if the fan is capable of
-             * multiple speeds.
+             * Indicates that the fan has one speed (value of 1) or the maximum speed, if the fan is capable of multiple
+             * speeds.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 4.4.6.5
              */
@@ -285,17 +285,17 @@ export namespace FanControl {
              * shall return INVALID_IN_STATE to indicate that the fan is not in a state where the SpeedSetting can be
              * changed to the requested value.
              *
-             * If this is successfully written to 0, the server shall set the FanMode attribute value to Off. Please
-             * see the Section 4.4.6.6.1 for details on other values.
+             * If this is successfully written to 0, the server shall set the FanMode attribute value to Off. Please see
+             * the Section 4.4.6.6.1 for details on other values.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 4.4.6.6
              */
             speedSetting: WritableAttribute(0x5, TlvNullable(TlvUInt8), { default: 0 }),
 
             /**
-             * Indicates the actual currently operating fan speed, or zero to indicate that the fan is off. There may
-             * be a temporary mismatch between the value of this attribute and the value of the SpeedSetting attribute
-             * due to other system requirements that would not allow the fan to operate at the requested setting.
+             * Indicates the actual currently operating fan speed, or zero to indicate that the fan is off. There may be
+             * a temporary mismatch between the value of this attribute and the value of the SpeedSetting attribute due
+             * to other system requirements that would not allow the fan to operate at the requested setting.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 4.4.6.7
              */
@@ -320,9 +320,9 @@ export namespace FanControl {
              * only be set to 1, if the corresponding bit in the RockSupport attribute is set to 1, otherwise a status
              * code of CONSTRAINT_ERROR shall be returned.
              *
-             * If a combination of supported bits is set by the client, and the server does not support the
-             * combination, the lowest supported single bit in the combination shall be set and active, and all other
-             * bits shall indicate zero.
+             * If a combination of supported bits is set by the client, and the server does not support the combination,
+             * the lowest supported single bit in the combination shall be set and active, and all other bits shall
+             * indicate zero.
              *
              * For example: If RockUpDown and RockRound are both set, but this combination is not possible, then only
              * RockUpDown becomes active.
@@ -339,8 +339,8 @@ export namespace FanControl {
     export const WindComponent = MutableCluster.Component({
         attributes: {
             /**
-             * This attribute is a bitmap that indicates what wind modes the server supports. At least one wind mode
-             * bit shall be set.
+             * This attribute is a bitmap that indicates what wind modes the server supports. At least one wind mode bit
+             * shall be set.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 4.4.6.10
              */
@@ -351,9 +351,9 @@ export namespace FanControl {
              * only be set to 1, if the corresponding bit in the WindSupport attribute is set to 1, otherwise a status
              * code of CONSTRAINT_ERROR shall be returned.
              *
-             * If a combination of supported bits is set by the client, and the server does not support the
-             * combination, the lowest supported single bit in the combination shall be set and active, and all other
-             * bits shall indicate zero.
+             * If a combination of supported bits is set by the client, and the server does not support the combination,
+             * the lowest supported single bit in the combination shall be set and active, and all other bits shall
+             * indicate zero.
              *
              * For example: If Sleep Wind and Natural Wind are set, but this combination is not possible, then only
              * Sleep Wind becomes active.
@@ -417,11 +417,11 @@ export namespace FanControl {
              *
              * Legacy Fan Control cluster revision 0-1 defined 3 speeds (low, medium and high) plus automatic speed
              * control but left it up to the implementer to decide what was supported. Therefore, it is assumed that
-             * legacy client implementations are capable of determining, from the server, the number of speeds
-             * supported between 1, 2, or 3, and whether automatic speed control is supported.
+             * legacy client implementations are capable of determining, from the server, the number of speeds supported
+             * between 1, 2, or 3, and whether automatic speed control is supported.
              *
-             * The MultiSpeed feature includes new attributes that support a running fan speed value from 0 to
-             * SpeedMax, which has a maximum of 100.
+             * The MultiSpeed feature includes new attributes that support a running fan speed value from 0 to SpeedMax,
+             * which has a maximum of 100.
              *
              * See Section 4.4.6.6.1 for more details.
              *
@@ -507,10 +507,10 @@ export namespace FanControl {
             percentSetting: WritableAttribute(0x2, TlvNullable(TlvPercent), { default: 0 }),
 
             /**
-             * Indicates the actual currently operating fan speed, or zero to indicate that the fan is off. There may
-             * be a temporary mismatch between the value of this attribute and the value of the PercentSetting
-             * attribute due to other system requirements that would not allow the fan to operate at the requested
-             * setting. See Section 4.4.6.3.1 for more details.
+             * Indicates the actual currently operating fan speed, or zero to indicate that the fan is off. There may be
+             * a temporary mismatch between the value of this attribute and the value of the PercentSetting attribute
+             * due to other system requirements that would not allow the fan to operate at the requested setting. See
+             * Section 4.4.6.3.1 for more details.
              *
              * @see {@link MatterSpecification.v13.Cluster} § 4.4.6.4
              */
@@ -588,8 +588,8 @@ export namespace FanControl {
     /**
      * This cluster supports all FanControl 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.
      */
     export interface Complete extends Identity<typeof CompleteInstance> {}
 

package/src/clusters/fixed-label.ts

@@ -31,8 +31,8 @@ export namespace FixedLabel {
     });
 
     /**
-     * This cluster is derived from the Label cluster and provides a feature for the device to tag an endpoint with
-     * zero or more read-only labels.
+     * This cluster is derived from the Label cluster and provides a feature for the device to tag an endpoint with zero
+     * or more read-only labels.
      *
      * Examples:
      *
@@ -47,8 +47,8 @@ export namespace FixedLabel {
      * knows which of the endpoints is which of the lights.
      *
      * Note that the TagList in the Descriptor cluster provides an alternative mechanism for such self- description
-     * using standardized tags rather than manufacturer-selected strings, yielding a standardized mechanism for
-     * features defined in the various namespaces. The second example above can be implemented using semantic tags
+     * using standardized tags rather than manufacturer-selected strings, yielding a standardized mechanism for features
+     * defined in the various namespaces. The second example above can be implemented using semantic tags
      * Direction.Upward and Direction.Downward instead of (or in addition to) the Fixed Label cluster.
      *
      * @see {@link MatterSpecification.v13.Core} § 9.8

package/src/clusters/formaldehyde-concentration-measurement.ts

@@ -37,8 +37,8 @@ export namespace FormaldehydeConcentrationMeasurement {
      * This cluster supports all FormaldehydeConcentrationMeasurement 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.
      */
     export const CompleteInstance = MutableCluster({
         ...ConcentrationMeasurement.Complete,