Readonly
granularity: Attribute<TimeSynchronization.Granularity, any>The granularity of the error that the node is willing to guarantee on the time synchronization. It is of type GranularityEnum.
This value shall be set to NoTimeGranularity if UTCTime is null and shall NOT be set to NoTimeGranularity if UTCTime is non-null.
Readonly
timeThe node’s time source. This attribute indicates what method the node is using to sync, whether the source uses NTS or not and whether the source is internal or external to the Matter network. This attribute may be used by a client to determine its level of trust in the UTCTime. It is of type TimeSourceEnum.
If a node is unsure if the selected NTP server is within the Matter network, it SHOULD select one of the NonMatter* values.
This value shall be set to None if UTCTime is null and shall NOT be set to None if UTCTime is non-null.
Readonly
utcIf the node has achieved time synchronization, this shall indicate the current time as a UTC epoch-us (Epoch Time in Microseconds).
If the node has not achieved time synchronization, this shall be null. This attribute may be set when a SetUTCTime is received.
Readonly
setThis command may be issued by Administrator to set the time. If the Commissioner does not have a valid time source, it may send a Granularity of NoTimeGranularity.
Upon receipt of this command, the node may update its UTCTime attribute to match the time specified in the command, if the stated Granularity and TimeSource are acceptable. The node shall update its UTCTime attribute if its current Granularity is NoTimeGranularity.
If the time is updated, the node shall also update its Granularity attribute based on the granularity specified in the command and the expected clock drift of the node. This SHOULD normally be one level lower than the stated command Granularity. It shall also update its TimeSource attribute to Admin. It shall also update its Last Known Good UTC Time as defined in Section 3.5.6.1, “Last Known Good UTC Time”.
If the node updates its UTCTime attribute, it shall accept the command with a status code of SUCCESS. If it opts to not update its time, it shall fail the command with a cluster specific Status Code of TimeNotAccepted.
Readonly
timeThis event shall be generated if the node has not generated a TimeFailure event in the last hour, and the node is unable to get a time from any source. This event SHOULD NOT be generated more often than once per hour.
Readonly
ntpNtpClient
Allows a node to use NTP/SNTP for time synchronization.
Readonly
ntpNtpServer
Allows a Node to host an NTP server for the network so that other Nodes can achieve a high accuracy time synchronization within the network. See Section 11.17.15, “Acting as an NTP Server”.
Readonly
timeTimeSyncClient
This node also supports a time synchronization client and can connect to and read time from other nodes.
Readonly
timeTimeZone
Allows a server to translate a UTC time to a local time using the time zone and daylight savings time (DST) offsets. If a server supports the TimeZone feature, it shall support the SetTimeZone and SetDSTOffset commands, and TimeZone and DSTOffset attributes, and shall expose the local time through the LocalTime attribute.
Modify elements using ElementModifier.alter.
Modify elements using ElementModifier.enable.
Modify elements using ElementModifier.set.
Select features using ClusterComposer.compose.
Rest
...selection: SelectionT
Accurate time is required for a number of reasons, including scheduling, display and validating security materials.
This section describes a mechanism for Nodes to achieve and maintain time synchronization. The Time Synchronization cluster provides attributes for reading a Node’s current time. It also allows Administrators to set current time, time zone and daylight savings time (DST) settings.
The Time Synchronization cluster may be present on the root node endpoint, and shall NOT be present on any other Endpoint of any Node.
TimeSynchronizationCluster supports optional features that you can enable with the TimeSynchronizationCluster.with() factory method.
See
MatterSpecification.v13.Core § 11.17