Variable CheckInProtocolSupportComponentConst

Type declaration

• Readonlyattributes: {
      clientsSupportedPerFabric: FixedAttribute<number, any>;
      icdCounter: Attribute<number, any>;
      registeredClients: FabricScopedAttribute<TypeFromFields[], any>;
  }

  • ReadonlyclientsSupportedPerFabric: FixedAttribute<number, any>

    Indicates the maximum number of entries that the server is able to store for each fabric in the RegisteredClients attribute.

    See

    MatterSpecification.v13.Core § 9.17.6.6

  • ReadonlyicdCounter: Attribute<number, any>

    This attribute returns the value of the ICD Counter.

    See

    MatterSpecification.v13.Core § 9.17.6.5

  • ReadonlyregisteredClients: FabricScopedAttribute<TypeFromFields[], any>

    This attribute shall contain all clients registered to receive notification if their subscription is lost. The maximum number of entries that can be in the list shall be ClientsSupportedPerFabric for each fabric supported on the server, as indicated by the value of the SupportedFabrics attribute in the Operational Credentials cluster.

    See

    MatterSpecification.v13.Core § 9.17.6.4

• Readonlycommands: {
      registerClient: Command<TypeFromFields, TypeFromFields, any>;
      unregisterClient: Command<TypeFromFields, void, any>;
  }

  • ReadonlyregisterClient: Command<TypeFromFields, TypeFromFields, any>

    This command allows a client to register itself with the ICD to be notified when the device is available for communication.

    See

    MatterSpecification.v13.Core § 9.17.7.1

  • ReadonlyunregisterClient: Command<TypeFromFields, void, any>

    This command allows a client to unregister itself with the ICD. Example: a client that is leaving the network (e.g. running on a phone which is leaving the home) can (and should) remove its subscriptions and send this UnregisterClient command before leaving to prevent the burden on the ICD of an absent client.

    See

    MatterSpecification.v13.Core § 9.17.7.3