@matter/types 0.13.1-alpha.0-20250516-6288f3c54 → 0.13.1-alpha.0-20250520-d699cd56d

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

@@ -1522,8 +1522,6 @@ export namespace DeviceEnergyManagement {
 
         features: {
             /**
-             * PowerAdjustment
-             *
              * For Energy Smart Appliances (ESA) the definition of being 'smart' mandates that they can report their
              * current power adjustment capability and have an EMS request a temporary adjustment. This may typically be
              * to curtail power requirements during peak periods, but can also be used to turn on an ESA if there is
@@ -1538,8 +1536,6 @@ export namespace DeviceEnergyManagement {
             powerAdjustment: BitFlag(0),
 
             /**
-             * PowerForecastReporting
-             *
              * For Energy Smart Appliances (ESA) the definition of being 'smart' implies that they can report their
              * indicative forecast power demands or generation, to a greater or lesser extent. For some ESAs this is
              * highly predictable (in terms of both power and time), in other appliances this is more challenging and
@@ -1577,8 +1573,6 @@ export namespace DeviceEnergyManagement {
             powerForecastReporting: BitFlag(1),
 
             /**
-             * StateForecastReporting
-             *
              * Some ESAs do not know their actual power consumption, but do know the state of operation. Like the
              * PowerForecastingReporting feature, this uses the same slot structure mechanism to indicate a change in
              * state vs time.
@@ -1597,8 +1591,6 @@ export namespace DeviceEnergyManagement {
             stateForecastReporting: BitFlag(2),
 
             /**
-             * StartTimeAdjustment
-             *
              * ESAs which support the Start Time Adjustment feature, allow an EMS to recommend a change to the start
              * time of the energy transfer that the ESA has previously suggested it would use.
              *
@@ -1620,8 +1612,6 @@ export namespace DeviceEnergyManagement {
             startTimeAdjustment: BitFlag(3),
 
             /**
-             * Pausable
-             *
              * ESAs which support the Pausable feature, allow an EMS to recommend a pause in the middle of a forecast
              * power profile that the ESA is currently using.
              *
@@ -1643,8 +1633,6 @@ export namespace DeviceEnergyManagement {
             pausable: BitFlag(4),
 
             /**
-             * ForecastAdjustment
-             *
              * ESAs which support the Forecast adjustment feature, allow an EMS to recommend a change to the start,
              * duration and/or power level limits of the steps of the power profile that the ESA has previously
              * suggested it would use.
@@ -1670,8 +1658,6 @@ export namespace DeviceEnergyManagement {
             forecastAdjustment: BitFlag(5),
 
             /**
-             * ConstraintBasedAdjustment
-             *
              * ESAs which support the Constraint-Based Adjustment feature allow an EMS to inform the ESA of periods
              * during which power usage should be modified (for example when the EMS has been made aware that the grid
              * supplier has requested reduced energy usage due to overall peak grid demand) and may cause the ESA to

package/src/clusters/dishwasher-alarm.ts

@@ -215,8 +215,6 @@ export namespace DishwasherAlarm {
 
         features: {
             /**
-             * Reset
-             *
              * This feature indicates that alarms can be reset via the Reset command.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 1.15.4.1

package/src/clusters/dishwasher-mode.ts

@@ -223,8 +223,6 @@ export namespace DishwasherMode {
 
         features: {
             /**
-             * OnOff
-             *
              * Dependency with the OnOff cluster
              */
             onOff: BitFlag(0)

package/src/clusters/door-lock.ts

@@ -4061,8 +4061,6 @@ export namespace DoorLock {
 
         features: {
             /**
-             * PinCredential
-             *
              * If the User Feature is also supported then any PIN Code stored in the lock shall be associated with a
              * User.
              *
@@ -4075,8 +4073,6 @@ export namespace DoorLock {
             pinCredential: BitFlag(0),
 
             /**
-             * RfidCredential
-             *
              * If the User Feature is also supported then any RFID credential stored in the lock shall be associated
              * with a User.
              *
@@ -4089,8 +4085,6 @@ export namespace DoorLock {
             rfidCredential: BitFlag(1),
 
             /**
-             * FingerCredentials
-             *
              * Currently the cluster only defines the metadata format for notifications when a fingerprint/ finger vein
              * credential is used to access the lock and doesn’t describe how to create fingerprint/finger vein
              * credentials. If the Users feature is also supported then the User that a fingerprint/finger vein is
@@ -4105,8 +4099,6 @@ export namespace DoorLock {
             fingerCredentials: BitFlag(2),
 
             /**
-             * WeekDayAccessSchedules
-             *
              * If the User feature is supported then Week Day Schedules are applied to a User and not a credential.
              *
              * Week Day Schedules are used to restrict access to a specified time window on certain days of the week.
@@ -4122,8 +4114,6 @@ export namespace DoorLock {
             weekDayAccessSchedules: BitFlag(4),
 
             /**
-             * DoorPositionSensor
-             *
              * If this feature is supported this indicates that the lock has the ability to determine the position of
              * the door which is separate from the state of the lock.
              *
@@ -4132,8 +4122,6 @@ export namespace DoorLock {
             doorPositionSensor: BitFlag(5),
 
             /**
-             * FaceCredentials
-             *
              * Currently the cluster only defines the metadata format for notifications when a face recognition, iris,
              * or retina credential is used to access the lock and doesn’t describe how to create face recognition,
              * iris, or retina credentials. If the Users feature is also supported then the User that a face
@@ -4148,8 +4136,6 @@ export namespace DoorLock {
             faceCredentials: BitFlag(6),
 
             /**
-             * CredentialOverTheAirAccess
-             *
              * If this feature is supported then the lock supports the ability to verify a credential provided in a
              * lock/unlock command. Currently the cluster only supports providing the PIN credential to the lock/unlock
              * commands. If this feature is supported then the PIN Credential feature shall also be supported.
@@ -4159,8 +4145,6 @@ export namespace DoorLock {
             credentialOverTheAirAccess: BitFlag(7),
 
             /**
-             * User
-             *
              * If the User Feature is supported then a lock employs a User database. A User within the User database is
              * used to associate credentials and schedules to single user record within the lock. This also means the
              * UserType and UserStatus fields are associated with a User and not a credential.
@@ -4170,8 +4154,6 @@ export namespace DoorLock {
             user: BitFlag(8),
 
             /**
-             * YearDayAccessSchedules
-             *
              * If the User feature is supported then Year Day Schedules are applied to a User and not a credential. Year
              * Day Schedules are used to restrict access to a specified date and time window.
              *
@@ -4185,8 +4167,6 @@ export namespace DoorLock {
             yearDayAccessSchedules: BitFlag(10),
 
             /**
-             * HolidaySchedules
-             *
              * This feature is used to setup Holiday Schedule in the lock device. A Holiday Schedule sets a start and
              * stop end date/time for the lock to use the specified operating mode set by the Holiday Schedule.
              *
@@ -4197,8 +4177,6 @@ export namespace DoorLock {
             holidaySchedules: BitFlag(11),
 
             /**
-             * Unbolting
-             *
              * Locks that support this feature differentiate between unbolting and unlocking. The Unbolt Door command
              * retracts the bolt without pulling the latch. The Unlock Door command fully unlocks the door by retracting
              * the bolt and briefly pulling the latch. While the latch is pulled, the lock state changes to Unlatched.
@@ -4210,8 +4188,6 @@ export namespace DoorLock {
             unbolting: BitFlag(12),
 
             /**
-             * AliroProvisioning
-             *
              * Locks that support this feature implement the Aliro specification as defined in [Aliro] and support
              * Matter as a method for provisioning Aliro credentials.
              *
@@ -4220,8 +4196,6 @@ export namespace DoorLock {
             aliroProvisioning: BitFlag(13),
 
             /**
-             * AliroBleuwb
-             *
              * Locks that support this feature implement the Bluetooth LE + UWB Access Control Flow as defined in
              * [Aliro].
              *

package/src/clusters/electrical-energy-measurement.ts

@@ -472,8 +472,6 @@ export namespace ElectricalEnergyMeasurement {
 
         features: {
             /**
-             * ImportedEnergy
-             *
              * The feature indicates the server is capable of measuring how much energy is imported by the server.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 2.12.4.1
@@ -481,8 +479,6 @@ export namespace ElectricalEnergyMeasurement {
             importedEnergy: BitFlag(0),
 
             /**
-             * ExportedEnergy
-             *
              * The feature indicates the server is capable of measuring how much energy is exported by the server.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 2.12.4.2
@@ -490,8 +486,6 @@ export namespace ElectricalEnergyMeasurement {
             exportedEnergy: BitFlag(1),
 
             /**
-             * CumulativeEnergy
-             *
              * The feature indicates the server is capable of measuring how much energy has been imported or exported by
              * the server over the device’s lifetime. This measurement may start from when a device’s firmware is
              * updated to include this feature, when a device’s firmware is updated to correct measurement errors, or
@@ -502,8 +496,6 @@ export namespace ElectricalEnergyMeasurement {
             cumulativeEnergy: BitFlag(2),
 
             /**
-             * PeriodicEnergy
-             *
              * The feature indicates the server is capable of measuring how much energy has been imported or exported by
              * the server during a certain period of time. The start and end times for measurement periods shall be
              * determined by the server, and may represent overlapping periods.

package/src/clusters/electrical-power-measurement.ts

@@ -554,8 +554,6 @@ export namespace ElectricalPowerMeasurement {
 
         features: {
             /**
-             * DirectCurrent
-             *
              * This feature indicates the cluster can measure a direct current.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 2.13.4.1
@@ -563,8 +561,6 @@ export namespace ElectricalPowerMeasurement {
             directCurrent: BitFlag(0),
 
             /**
-             * AlternatingCurrent
-             *
              * This feature indicates the cluster can measure an alternating current.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 2.13.4.2
@@ -572,8 +568,6 @@ export namespace ElectricalPowerMeasurement {
             alternatingCurrent: BitFlag(1),
 
             /**
-             * PolyphasePower
-             *
              * This feature indicates the cluster represents the collective measurements for a Polyphase power supply.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 2.13.4.3
@@ -581,8 +575,6 @@ export namespace ElectricalPowerMeasurement {
             polyphasePower: BitFlag(2),
 
             /**
-             * Harmonics
-             *
              * This feature indicates the cluster can measure the harmonics of an alternating current.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 2.13.4.4
@@ -590,8 +582,6 @@ export namespace ElectricalPowerMeasurement {
             harmonics: BitFlag(3),
 
             /**
-             * PowerQuality
-             *
              * This feature indicates the cluster can measure the harmonic phases of an alternating current.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 2.13.4.5

package/src/clusters/energy-evse-mode.ts

@@ -243,8 +243,6 @@ export namespace EnergyEvseMode {
 
         features: {
             /**
-             * OnOff
-             *
              * Dependency with the OnOff cluster
              */
             onOff: BitFlag(0)

package/src/clusters/energy-evse.ts

@@ -1111,8 +1111,6 @@ export namespace EnergyEvse {
 
         features: {
             /**
-             * 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
@@ -1139,8 +1137,6 @@ export namespace EnergyEvse {
             chargingPreferences: BitFlag(0),
 
             /**
-             * SoCReporting
-             *
              * Vehicles and EVSEs which support ISO 15118 may allow the vehicle to report its battery size and state of
              * charge. If the EVSE supports PLC it may have a vehicle connected which optionally supports reporting of
              * its battery size and current State of Charge (SoC).
@@ -1156,8 +1152,6 @@ export namespace EnergyEvse {
             soCReporting: BitFlag(1),
 
             /**
-             * PlugAndCharge
-             *
              * 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).
@@ -1169,8 +1163,6 @@ export namespace EnergyEvse {
             plugAndCharge: BitFlag(2),
 
             /**
-             * Rfid
-             *
              * If the EVSE is fitted with an RFID reader, it may be possible to obtain the User or Vehicle ID from an
              * RFID card. This may be used to record a charging session against a specific charging account, and may
              * optionally be used to authorize a charging session.
@@ -1184,8 +1176,6 @@ export namespace EnergyEvse {
             rfid: BitFlag(3),
 
             /**
-             * 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.
              *

package/src/clusters/energy-preference.ts

@@ -221,8 +221,6 @@ export namespace EnergyPreference {
 
         features: {
             /**
-             * 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.
              *
@@ -231,8 +229,6 @@ export namespace EnergyPreference {
             energyBalance: BitFlag(0),
 
             /**
-             * LowPowerModeSensitivity
-             *
              * 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.

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

@@ -188,16 +188,12 @@ export namespace EthernetNetworkDiagnostics {
 
         features: {
             /**
-             * PacketCounts
-             *
              * Node makes available the counts for the number of received and transmitted packets on the ethernet
              * interface.
              */
             packetCounts: BitFlag(0),
 
             /**
-             * ErrorCounts
-             *
              * Node makes available the counts for the number of errors that have occurred during the reception and
              * transmission of packets on the ethernet interface.
              */

package/src/clusters/fan-control.ts

@@ -413,8 +413,6 @@ export namespace FanControl {
 
         features: {
             /**
-             * MultiSpeed
-             *
              * 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
@@ -430,36 +428,26 @@ export namespace FanControl {
             multiSpeed: BitFlag(0),
 
             /**
-             * Auto
-             *
              * Automatic mode supported for fan speed
              */
             auto: BitFlag(1),
 
             /**
-             * Rocking
-             *
              * Rocking movement supported
              */
             rocking: BitFlag(2),
 
             /**
-             * Wind
-             *
              * Wind emulation supported
              */
             wind: BitFlag(3),
 
             /**
-             * Step
-             *
              * Step command supported
              */
             step: BitFlag(4),
 
             /**
-             * AirflowDirection
-             *
              * Airflow Direction attribute is supported
              */
             airflowDirection: BitFlag(5)

package/src/clusters/general-commissioning.ts

@@ -448,8 +448,6 @@ export namespace GeneralCommissioning {
 
         features: {
             /**
-             * TermsAndConditions
-             *
              * Supports Terms & Conditions acknowledgement
              */
             termsAndConditions: BitFlag(0)

package/src/clusters/general-diagnostics.ts

@@ -654,8 +654,6 @@ export namespace GeneralDiagnostics {
 
         features: {
             /**
-             * DataModelTest
-             *
              * This feature indicates support for extended Data Model testing commands, which are required in some
              * situations.
              *

package/src/clusters/group-key-management.ts

@@ -335,8 +335,6 @@ export namespace GroupKeyManagement {
 
         features: {
             /**
-             * CacheAndSync
-             *
              * The ability to support CacheAndSync security policy and MCSP.
              */
             cacheAndSync: BitFlag(0)

package/src/clusters/groups.ts

@@ -317,8 +317,6 @@ export namespace Groups {
 
         features: {
             /**
-             * GroupNames
-             *
              * The Group Names feature indicates the ability to store a name for a group when a group is added.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 1.3.4.1

package/src/clusters/icd-management.ts

@@ -552,8 +552,6 @@ export namespace IcdManagement {
 
         features: {
             /**
-             * CheckInProtocolSupport
-             *
              * When this feature is supported, the device shall support all the associated commands and attributes to
              * properly support the Check-In Protocol.
              *
@@ -562,8 +560,6 @@ export namespace IcdManagement {
             checkInProtocolSupport: BitFlag(0),
 
             /**
-             * UserActiveModeTrigger
-             *
              * This feature is supported if and only if the device has a user active mode trigger.
              *
              * @see {@link MatterSpecification.v14.Core} § 9.17.4.2
@@ -571,8 +567,6 @@ export namespace IcdManagement {
             userActiveModeTrigger: BitFlag(1),
 
             /**
-             * LongIdleTimeSupport
-             *
              * This feature is supported if and only the device is a Long Idle Time ICD.
              *
              * @see {@link MatterSpecification.v14.Core} § 9.17.4.3
@@ -580,8 +574,6 @@ export namespace IcdManagement {
             longIdleTimeSupport: BitFlag(2),
 
             /**
-             * DynamicSitLitSupport
-             *
              * This feature is supported if and only if the device can switch between SIT and LIT operating modes even
              * if it has a valid registered client. See the dynamic SIT / LIT operating mode switching for more details.
              *
@@ -642,11 +634,7 @@ export namespace IcdManagement {
              *
              * @see {@link MatterSpecification.v14.Core} § 9.17.6.8
              */
-            userActiveModeTriggerInstruction: OptionalFixedAttribute(
-                0x7,
-                TlvString.bound({ maxLength: 128 }),
-                { default: "" }
-            )
+            userActiveModeTriggerInstruction: OptionalFixedAttribute(0x7, TlvString.bound({ maxLength: 128 }))
         },
 
         commands: {

package/src/clusters/keypad-input.ts

@@ -207,22 +207,16 @@ export namespace KeypadInput {
 
         features: {
             /**
-             * NavigationKeyCodes
-             *
              * Supports UP, DOWN, LEFT, RIGHT, SELECT, BACK, EXIT, MENU
              */
             navigationKeyCodes: BitFlag(0),
 
             /**
-             * LocationKeys
-             *
              * Supports CEC keys 0x0A (Settings) and 0x09 (Home)
              */
             locationKeys: BitFlag(1),
 
             /**
-             * NumberKeys
-             *
              * Supports numeric input 0..9
              */
             numberKeys: BitFlag(2)

package/src/clusters/laundry-washer-controls.ts

@@ -141,8 +141,6 @@ export namespace LaundryWasherControls {
 
         features: {
             /**
-             * Spin
-             *
              * This feature indicates multiple spin speeds are supported in at least one supported mode. Note that some
              * modes may not support multiple spin speeds even if this feature is supported.
              *
@@ -151,8 +149,6 @@ export namespace LaundryWasherControls {
             spin: BitFlag(0),
 
             /**
-             * Rinse
-             *
              * This feature indicates multiple rinse cycles are supported in at least one supported mode. Note that some
              * modes may not support selection of the number of rinse cycles even if this feature is supported.
              *

package/src/clusters/laundry-washer-mode.ts

@@ -181,8 +181,6 @@ export namespace LaundryWasherMode {
 
         features: {
             /**
-             * OnOff
-             *
              * Dependency with the OnOff cluster
              */
             onOff: BitFlag(0)

package/src/clusters/level-control.ts

@@ -274,11 +274,6 @@ export namespace LevelControl {
              */
             remainingTime: Attribute(0x1, TlvUInt16, { default: 0 }),
 
-            /**
-             * Indicates the minimum value of CurrentLevel that is capable of being assigned.
-             *
-             * @see {@link MatterSpecification.v14.Cluster} § 1.6.6.4
-             */
             minLevel: OptionalAttribute(0x2, TlvUInt8.bound({ min: 1, max: 254 }), { default: 1 }),
 
             /**
@@ -369,15 +364,11 @@ export namespace LevelControl {
 
         features: {
             /**
-             * OnOff
-             *
              * Dependency with the On/Off cluster
              */
             onOff: BitFlag(0),
 
             /**
-             * Lighting
-             *
              * This feature supports an interface for controlling the level of a light source. For the CurrentLevel
              * attribute:
              *
@@ -394,8 +385,6 @@ export namespace LevelControl {
             lighting: BitFlag(1),
 
             /**
-             * Frequency
-             *
              * Supports frequency attributes and behavior.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 1.6.4.3

package/src/clusters/media-input.ts

@@ -161,8 +161,6 @@ export namespace MediaInput {
 
         features: {
             /**
-             * NameUpdates
-             *
              * Supports updates to the input names
              */
             nameUpdates: BitFlag(0)

package/src/clusters/media-playback.ts

@@ -896,8 +896,6 @@ export namespace MediaPlayback {
 
         features: {
             /**
-             * AdvancedSeek
-             *
              * This feature provides access to the time offset location within current playback media and allows for
              * jumping to a specific location using time offsets. This enables clients to implement more advanced media
              * seeking behavior in their user interface, for instance a "seek bar".
@@ -907,8 +905,6 @@ export namespace MediaPlayback {
             advancedSeek: BitFlag(0),
 
             /**
-             * VariableSpeed
-             *
              * This feature is for a device which supports variable speed playback on media that supports it.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 6.10.4.2
@@ -916,8 +912,6 @@ export namespace MediaPlayback {
             variableSpeed: BitFlag(1),
 
             /**
-             * TextTracks
-             *
              * This feature is for a device or app that supports Text Tracks.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 6.10.4.3
@@ -925,8 +919,6 @@ export namespace MediaPlayback {
             textTracks: BitFlag(2),
 
             /**
-             * AudioTracks
-             *
              * This feature is for a device or app that supports Audio Tracks.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 6.10.4.4
@@ -934,8 +926,6 @@ export namespace MediaPlayback {
             audioTracks: BitFlag(3),
 
             /**
-             * AudioAdvance
-             *
              * This feature is for a device or app that supports playing audio during fast and slow advance and rewind
              * (e.g., while playback speed is not 1). A device that supports this feature may only support playing audio
              * during certain speeds.