SMETS requirement clause

4.5.3.17 — Remove Device Security Credentials

2 technical records havebeen identified at this reference: 1 Section 20 item and 1 explicit clause reference. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

GSMEAlert touchpoint onlyNo Section 20 bridge
1

Atomic items

Section 20 objects, attributes or methods at this source reference.

2

Documented touchpoints

Typed relationships supported by source mapping rows.

0

Linked SRVs

Unique retained services reached through exact control rows.

2

Linked alerts

Explicit requirement-to-alert references.

SMETS4.5.3.17 · item DeviceLog(notCHF).method: removeEntry

DeviceLog(notCHF) - removeEntry

No Section 20 bridge

Remove an entry from the Device Log as per section 13.

Object
DeviceLog(notCHF)
Attribute / method
method: removeEntry
Interface disposition
E
Category
Method
Section 20 meaning
Remove an entry from the Device Log as per section 13.

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Evidence:source paragraph 571, 572Section 20 row 1264

SMETS4.5.3.17 · item clause.4.5.3.17

Remove Device Security Credentials

Alert touchpoint only

This source clause is explicitly referenced by the GBCS device alert table.

Category
Alert reference

Documented touchpoints

  • Alert touchpointGSME0x8F4ADevice Unjoining failed
  • Alert touchpointGSME0x8F4BDevice Unjoining succeeded
Evidence:source paragraph 571, 572

How to read this page

Evidence is kept at record level

A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.