@matter/types 0.13.1-alpha.0-20250515-a4c61c546 → 0.13.1-alpha.0-20250517-99a1e848a

package/dist/esm/clusters/door-lock.d.ts

@@ -4623,8 +4623,6 @@ export declare namespace DoorLock {
         readonly revision: 8;
         readonly features: {
             /**
-             * PinCredential
-             *
              * If the User Feature is also supported then any PIN Code stored in the lock shall be associated with a
              * User.
              *
@@ -4636,8 +4634,6 @@ export declare namespace DoorLock {
              */
             readonly pinCredential: BitFlag;
             /**
-             * RfidCredential
-             *
              * If the User Feature is also supported then any RFID credential stored in the lock shall be associated
              * with a User.
              *
@@ -4649,8 +4645,6 @@ export declare namespace DoorLock {
              */
             readonly rfidCredential: BitFlag;
             /**
-             * 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
@@ -4664,8 +4658,6 @@ export declare namespace DoorLock {
              */
             readonly fingerCredentials: BitFlag;
             /**
-             * 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.
@@ -4680,8 +4672,6 @@ export declare namespace DoorLock {
              */
             readonly weekDayAccessSchedules: BitFlag;
             /**
-             * 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.
              *
@@ -4689,8 +4679,6 @@ export declare namespace DoorLock {
              */
             readonly doorPositionSensor: BitFlag;
             /**
-             * 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
@@ -4704,8 +4692,6 @@ export declare namespace DoorLock {
              */
             readonly faceCredentials: BitFlag;
             /**
-             * 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.
@@ -4714,8 +4700,6 @@ export declare namespace DoorLock {
              */
             readonly credentialOverTheAirAccess: BitFlag;
             /**
-             * 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.
@@ -4724,8 +4708,6 @@ export declare namespace DoorLock {
              */
             readonly user: BitFlag;
             /**
-             * 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.
              *
@@ -4738,8 +4720,6 @@ export declare namespace DoorLock {
              */
             readonly yearDayAccessSchedules: BitFlag;
             /**
-             * 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.
              *
@@ -4749,8 +4729,6 @@ export declare namespace DoorLock {
              */
             readonly holidaySchedules: BitFlag;
             /**
-             * 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.
@@ -4761,8 +4739,6 @@ export declare namespace DoorLock {
              */
             readonly unbolting: BitFlag;
             /**
-             * AliroProvisioning
-             *
              * Locks that support this feature implement the Aliro specification as defined in [Aliro] and support
              * Matter as a method for provisioning Aliro credentials.
              *
@@ -4770,8 +4746,6 @@ export declare namespace DoorLock {
              */
             readonly aliroProvisioning: BitFlag;
             /**
-             * AliroBleuwb
-             *
              * Locks that support this feature implement the Bluetooth LE + UWB Access Control Flow as defined in
              * [Aliro].
              *
@@ -7090,8 +7064,6 @@ export declare namespace DoorLock {
             readonly revision: 8;
             readonly features: {
                 /**
-                 * PinCredential
-                 *
                  * If the User Feature is also supported then any PIN Code stored in the lock shall be associated with a
                  * User.
                  *
@@ -7103,8 +7075,6 @@ export declare namespace DoorLock {
                  */
                 readonly pinCredential: BitFlag;
                 /**
-                 * RfidCredential
-                 *
                  * If the User Feature is also supported then any RFID credential stored in the lock shall be associated
                  * with a User.
                  *
@@ -7116,8 +7086,6 @@ export declare namespace DoorLock {
                  */
                 readonly rfidCredential: BitFlag;
                 /**
-                 * 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
@@ -7131,8 +7099,6 @@ export declare namespace DoorLock {
                  */
                 readonly fingerCredentials: BitFlag;
                 /**
-                 * 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.
@@ -7147,8 +7113,6 @@ export declare namespace DoorLock {
                  */
                 readonly weekDayAccessSchedules: BitFlag;
                 /**
-                 * 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.
                  *
@@ -7156,8 +7120,6 @@ export declare namespace DoorLock {
                  */
                 readonly doorPositionSensor: BitFlag;
                 /**
-                 * 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
@@ -7171,8 +7133,6 @@ export declare namespace DoorLock {
                  */
                 readonly faceCredentials: BitFlag;
                 /**
-                 * 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.
@@ -7181,8 +7141,6 @@ export declare namespace DoorLock {
                  */
                 readonly credentialOverTheAirAccess: BitFlag;
                 /**
-                 * 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.
@@ -7191,8 +7149,6 @@ export declare namespace DoorLock {
                  */
                 readonly user: BitFlag;
                 /**
-                 * 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.
                  *
@@ -7205,8 +7161,6 @@ export declare namespace DoorLock {
                  */
                 readonly yearDayAccessSchedules: BitFlag;
                 /**
-                 * 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.
                  *
@@ -7216,8 +7170,6 @@ export declare namespace DoorLock {
                  */
                 readonly holidaySchedules: BitFlag;
                 /**
-                 * 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.
@@ -7228,8 +7180,6 @@ export declare namespace DoorLock {
                  */
                 readonly unbolting: BitFlag;
                 /**
-                 * AliroProvisioning
-                 *
                  * Locks that support this feature implement the Aliro specification as defined in [Aliro] and support
                  * Matter as a method for provisioning Aliro credentials.
                  *
@@ -7237,8 +7187,6 @@ export declare namespace DoorLock {
                  */
                 readonly aliroProvisioning: BitFlag;
                 /**
-                 * AliroBleuwb
-                 *
                  * Locks that support this feature implement the Bluetooth LE + UWB Access Control Flow as defined in
                  * [Aliro].
                  *
@@ -9552,8 +9500,6 @@ export declare namespace DoorLock {
         readonly revision: 8;
         readonly features: {
             /**
-             * PinCredential
-             *
              * If the User Feature is also supported then any PIN Code stored in the lock shall be associated with a
              * User.
              *
@@ -9565,8 +9511,6 @@ export declare namespace DoorLock {
              */
             readonly pinCredential: BitFlag;
             /**
-             * RfidCredential
-             *
              * If the User Feature is also supported then any RFID credential stored in the lock shall be associated
              * with a User.
              *
@@ -9578,8 +9522,6 @@ export declare namespace DoorLock {
              */
             readonly rfidCredential: BitFlag;
             /**
-             * 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
@@ -9593,8 +9535,6 @@ export declare namespace DoorLock {
              */
             readonly fingerCredentials: BitFlag;
             /**
-             * 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.
@@ -9609,8 +9549,6 @@ export declare namespace DoorLock {
              */
             readonly weekDayAccessSchedules: BitFlag;
             /**
-             * 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.
              *
@@ -9618,8 +9556,6 @@ export declare namespace DoorLock {
              */
             readonly doorPositionSensor: BitFlag;
             /**
-             * 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
@@ -9633,8 +9569,6 @@ export declare namespace DoorLock {
              */
             readonly faceCredentials: BitFlag;
             /**
-             * 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.
@@ -9643,8 +9577,6 @@ export declare namespace DoorLock {
              */
             readonly credentialOverTheAirAccess: BitFlag;
             /**
-             * 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.
@@ -9653,8 +9585,6 @@ export declare namespace DoorLock {
              */
             readonly user: BitFlag;
             /**
-             * 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.
              *
@@ -9667,8 +9597,6 @@ export declare namespace DoorLock {
              */
             readonly yearDayAccessSchedules: BitFlag;
             /**
-             * 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.
              *
@@ -9678,8 +9606,6 @@ export declare namespace DoorLock {
              */
             readonly holidaySchedules: BitFlag;
             /**
-             * 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.
@@ -9690,8 +9616,6 @@ export declare namespace DoorLock {
              */
             readonly unbolting: BitFlag;
             /**
-             * AliroProvisioning
-             *
              * Locks that support this feature implement the Aliro specification as defined in [Aliro] and support
              * Matter as a method for provisioning Aliro credentials.
              *
@@ -9699,8 +9623,6 @@ export declare namespace DoorLock {
              */
             readonly aliroProvisioning: BitFlag;
             /**
-             * AliroBleuwb
-             *
              * Locks that support this feature implement the Bluetooth LE + UWB Access Control Flow as defined in
              * [Aliro].
              *
@@ -12030,8 +11952,6 @@ export declare namespace DoorLock {
         readonly revision: 8;
         readonly features: {
             /**
-             * PinCredential
-             *
              * If the User Feature is also supported then any PIN Code stored in the lock shall be associated with a
              * User.
              *
@@ -12043,8 +11963,6 @@ export declare namespace DoorLock {
              */
             readonly pinCredential: BitFlag;
             /**
-             * RfidCredential
-             *
              * If the User Feature is also supported then any RFID credential stored in the lock shall be associated
              * with a User.
              *
@@ -12056,8 +11974,6 @@ export declare namespace DoorLock {
              */
             readonly rfidCredential: BitFlag;
             /**
-             * 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
@@ -12071,8 +11987,6 @@ export declare namespace DoorLock {
              */
             readonly fingerCredentials: BitFlag;
             /**
-             * 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.
@@ -12087,8 +12001,6 @@ export declare namespace DoorLock {
              */
             readonly weekDayAccessSchedules: BitFlag;
             /**
-             * 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.
              *
@@ -12096,8 +12008,6 @@ export declare namespace DoorLock {
              */
             readonly doorPositionSensor: BitFlag;
             /**
-             * 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
@@ -12111,8 +12021,6 @@ export declare namespace DoorLock {
              */
             readonly faceCredentials: BitFlag;
             /**
-             * 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.
@@ -12121,8 +12029,6 @@ export declare namespace DoorLock {
              */
             readonly credentialOverTheAirAccess: BitFlag;
             /**
-             * 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.
@@ -12131,8 +12037,6 @@ export declare namespace DoorLock {
              */
             readonly user: BitFlag;
             /**
-             * 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.
              *
@@ -12145,8 +12049,6 @@ export declare namespace DoorLock {
              */
             readonly yearDayAccessSchedules: BitFlag;
             /**
-             * 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.
              *
@@ -12156,8 +12058,6 @@ export declare namespace DoorLock {
              */
             readonly holidaySchedules: BitFlag;
             /**
-             * 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.
@@ -12168,8 +12068,6 @@ export declare namespace DoorLock {
              */
             readonly unbolting: BitFlag;
             /**
-             * AliroProvisioning
-             *
              * Locks that support this feature implement the Aliro specification as defined in [Aliro] and support
              * Matter as a method for provisioning Aliro credentials.
              *
@@ -12177,8 +12075,6 @@ export declare namespace DoorLock {
              */
             readonly aliroProvisioning: BitFlag;
             /**
-             * AliroBleuwb
-             *
              * Locks that support this feature implement the Bluetooth LE + UWB Access Control Flow as defined in
              * [Aliro].
              *
@@ -12449,8 +12345,6 @@ export declare namespace DoorLock {
             readonly clusterRevision: Attribute<number, never>;
             readonly featureMap: Attribute<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
                 /**
-                 * PinCredential
-                 *
                  * If the User Feature is also supported then any PIN Code stored in the lock shall be associated with a
                  * User.
                  *
@@ -12462,8 +12356,6 @@ export declare namespace DoorLock {
                  */
                 readonly pinCredential: BitFlag;
                 /**
-                 * RfidCredential
-                 *
                  * If the User Feature is also supported then any RFID credential stored in the lock shall be associated
                  * with a User.
                  *
@@ -12475,8 +12367,6 @@ export declare namespace DoorLock {
                  */
                 readonly rfidCredential: BitFlag;
                 /**
-                 * 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
@@ -12490,8 +12380,6 @@ export declare namespace DoorLock {
                  */
                 readonly fingerCredentials: BitFlag;
                 /**
-                 * 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.
@@ -12506,8 +12394,6 @@ export declare namespace DoorLock {
                  */
                 readonly weekDayAccessSchedules: BitFlag;
                 /**
-                 * 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.
                  *
@@ -12515,8 +12401,6 @@ export declare namespace DoorLock {
                  */
                 readonly doorPositionSensor: BitFlag;
                 /**
-                 * 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
@@ -12530,8 +12414,6 @@ export declare namespace DoorLock {
                  */
                 readonly faceCredentials: BitFlag;
                 /**
-                 * 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.
@@ -12540,8 +12422,6 @@ export declare namespace DoorLock {
                  */
                 readonly credentialOverTheAirAccess: BitFlag;
                 /**
-                 * 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.
@@ -12550,8 +12430,6 @@ export declare namespace DoorLock {
                  */
                 readonly user: BitFlag;
                 /**
-                 * 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.
                  *
@@ -12564,8 +12442,6 @@ export declare namespace DoorLock {
                  */
                 readonly yearDayAccessSchedules: BitFlag;
                 /**
-                 * 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.
                  *
@@ -12575,8 +12451,6 @@ export declare namespace DoorLock {
                  */
                 readonly holidaySchedules: BitFlag;
                 /**
-                 * 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.
@@ -12587,8 +12461,6 @@ export declare namespace DoorLock {
                  */
                 readonly unbolting: BitFlag;
                 /**
-                 * AliroProvisioning
-                 *
                  * Locks that support this feature implement the Aliro specification as defined in [Aliro] and support
                  * Matter as a method for provisioning Aliro credentials.
                  *
@@ -12596,8 +12468,6 @@ export declare namespace DoorLock {
                  */
                 readonly aliroProvisioning: BitFlag;
                 /**
-                 * AliroBleuwb
-                 *
                  * Locks that support this feature implement the Bluetooth LE + UWB Access Control Flow as defined in
                  * [Aliro].
                  *