ConstReadonlyattributes: { ReadonlyactiveReadonlyactiveThe ActiveNetworkFaults attribute shall indicate the set of faults currently detected by the Node. When the Node detects a fault has been raised, the appropriate NetworkFaultEnum value shall be added to this list. This list shall NOT contain more than one instance of a specific NetworkFaultEnum value. When the Node detects that all conditions contributing to a fault has been cleared, the corresponding NetworkFaultEnum value shall be removed from this list. An empty list shall indicate there are currently no active faults. The order of this list SHOULD have no significance. Clients interested in monitoring changes in active faults may subscribe to this attribute, or they may subscribe to NetworkFaultChange.
ReadonlyactiveThe ActiveRadioFaults attribute shall indicate the set of faults currently detected by the Node. When the Node detects a fault has been raised, the appropriate RadioFaultEnum value shall be added to this list. This list shall NOT contain more than one instance of a specific RadioFaultEnum value. When the Node detects that all conditions contributing to a fault has been cleared, the corresponding RadioFaultEnum value shall be removed from this list. An empty list shall indicate there are currently no active faults. The order of this list SHOULD have no significance. Clients interested in monitoring changes in active faults may subscribe to this attribute, or they may subscribe to RadioFaultChange.
ReadonlybootThe BootReason attribute shall indicate the reason for the Node’s most recent boot.
ReadonlynetworkThe NetworkInterfaces attribute shall be a list of NetworkInterface structs. Each logical network interface on the Node shall be represented by a single entry within the NetworkInterfaces attribute.
ReadonlyrebootThe RebootCount attribute shall indicate a best-effort count of the number of times the Node has rebooted. The RebootCount attribute SHOULD be incremented each time the Node reboots. The RebootCount attribute shall NOT be incremented when a Node wakes from a low-power or sleep state. The RebootCount attribute shall only be reset to 0 upon a factory reset of the Node.
ReadonlytestThe TestEventTriggersEnabled attribute shall indicate whether the Node has any TestEventTrigger configured. When this attribute is true, the Node has been configured with one or more test event triggers by virtue of the internally programmed EnableKey value (see Section 11.12.7.1, “TestEventTrigger Command”) being set to a non-zero value. This attribute can be used by Administrators to detect if a device was inadvertently commissioned with test event trigger mode enabled, and take appropriate action (e.g. warn the user and/or offer to remove all fabrics on the Node).
ReadonlytotalThe TotalOperationalHours attribute shall indicate a best-effort attempt at tracking the length of time, in hours, that the Node has been operational. The TotalOperationalHours attribute SHOULD be incremented to account for the periods of time that a Node is in a low-power or sleep state. The TotalOperationalHours attribute shall only be reset upon a factory reset of the Node.
ReadonlyupThe UpTime attribute shall indicate a best-effort assessment of the length of time, in seconds, since the Node’s last reboot. This attribute SHOULD be incremented to account for the periods of time that a Node is in a low-power or sleep state. This attribute shall only be reset upon a device reboot. This attribute shall be based on the same System Time source as those used to fulfill any usage of the system-us and system-ms data types within the server.
Readonlycommands: { ReadonlytestThis command shall be supported to provide a means for certification tests to trigger some test- plan-specific events, necessary to assist in automation of device interactions for some certification test cases. This command shall NOT cause any changes to the state of the device that persist after the last fabric is removed.
The fields for the TestEventTrigger command are as follows:
ReadonlytimeThis command may be used by a client to obtain a correlated view of both System Time, and, if currently synchronized and supported, "wall clock time" of the server. This can help clients establish
time correlation between their concept of time and the server’s concept of time. This is especially useful when processing event histories where some events only contain System Time.
Upon command invocation, the server shall respond with a TimeSnapshotResponse.
Readonlyevents: { ReadonlybootThe BootReason Event shall indicate the reason that caused the device to start-up.
ReadonlyhardwareThe HardwareFaultChange Event shall indicate a change in the set of hardware faults currently detected by the Node.
ReadonlynetworkThe NetworkFaultChange Event shall indicate a change in the set of network faults currently detected by the Node.
ReadonlyradioThe RadioFaultChange Event shall indicate a change in the set of radio faults currently detected by the Node.
Readonlyextensions: readonly [{ This metadata controls which GeneralDiagnosticsCluster elements matter.js activates for specific feature combinations.
Readonlyfeatures: { ReadonlydataDataModelTest
This feature indicates support for extended Data Model testing commands, which are required in some situations.
This feature shall be supported if the MaxPathsPerInvoke attribute of the Basic Information Cluster has a value > 1.
Readonlyid: 51Readonlyname: "GeneralDiagnostics"Readonlyrevision: 2
The ActiveHardwareFaults attribute shall indicate the set of faults currently detected by the Node. When the Node detects a fault has been raised, the appropriate HardwareFaultEnum value shall be added to this list. This list shall NOT contain more than one instance of a specific HardwareFaultEnum value. When the Node detects that all conditions contributing to a fault has been cleared, the corresponding HardwareFaultEnum value shall be removed from this list. An empty list shall indicate there are currently no active faults. The order of this list SHOULD have no significance. Clients interested in monitoring changes in active faults may subscribe to this attribute, or they may subscribe to HardwareFaultChange.