Platform events
The 5 first-party platform events you can subscribe to, rendered from the same tv-events.snapshot.json the SDK ships (v1.11.0) — this page cannot drift from what check-pact validates against.
Module events are not listed here, by design. An event published by a module is declared in that module's manifest (events.publishes) and nowhere else. The module catalog shows who publishes what; Events explains how the two sources fit together.
building.point.updated
| Field | Type | Required | Notes |
|---|---|---|---|
pointId | string | yes | uuid |
elementId | string | no | uuid |
value | number | string | boolean | null | yes | — |
unit | string | no | — |
quality | string | yes | good, uncertain, bad · default "good" |
observedAt | string | yes | date-time |
building.alarm.triggered
| Field | Type | Required | Notes |
|---|---|---|---|
alarmId | string | yes | uuid |
elementId | string | no | uuid |
severity | string | yes | info, warning, critical, emergency |
code | string | yes | — |
message | string | yes | — |
acknowledgedAt | string | no | date-time |
building.fault.created
| Field | Type | Required | Notes |
|---|---|---|---|
faultId | string | yes | uuid |
buildingId | string | yes | uuid |
elementId | string | no | uuid |
pointId | string | no | uuid |
severity | string | yes | — |
title | string | yes | — |
detectedAt | string | yes | date-time |
building.element.status_changed
| Field | Type | Required | Notes |
|---|---|---|---|
elementId | string | yes | uuid |
previousStatus | string | no | — |
newStatus | string | yes | — |
reason | string | no | — |
building.changeset.applied
| Field | Type | Required | Notes |
|---|---|---|---|
changesetId | string | yes | uuid |
appliedBy | string | yes | — |
appliedAt | string | yes | date-time |
summary | string | no | — |
affectedEntityCount | integer | no | — |