Expand description
Matter event paths, filters, and reports — EventPathIB / EventFilterIB /
EventDataIB / EventReportIB (Matter §10.6 / Appendix A).
Distinct from the attribute path/report code: EventPathIB uses tag base 0
(Node), not 2. Wire shapes are pinned by the matter.js byte-parity fixtures
(test-vectors/commissioning/im/{read/events_basic_information,report/report_data_event}.json)
and cross-checked against connectedhomeip src/app/MessageDef/Event*IB.h:
EventPathIB is a TLV list, EventFilterIB is a TLV structure.
Structs§
- Event
Filter - An
EventFilterIB: only events withevent_number >= event_minare reported (used to resume after the last seen event).nodeis omitted whenNone. - Event
Path - A read/subscribe event path with optional (wildcard) components. A
Nonefield is omitted from the encodedEventPathIB, which the IM interprets as a wildcard.nodeis normallyNonefor a controller addressing the connected node;is_urgentrequests urgent reporting on a subscription (B2). - Event
Report Item - One
EventDataIB(a real event with data).
Enums§
- Event
Priority - Event priority (Matter §14.3). Unknown values are preserved verbatim so a newer-revision device does not break decoding.
- Event
Report - One
EventReportIB: a real event (Data) or a per-path error (Status). - Event
Timestamp - The timestamp carried by an
EventDataIB. A report carries exactly one of these (absolute epoch/system, or a delta against the prior event in a subscription stream);Noneif the device omitted all four (tolerated rather than rejected).