System BMS — Value

Subscribe to BMS System values (heartbeat timestamps, status, etc.).

Direction: Subscribe (receive)

Channel

BMS/v1/PUB/Value/System/{pointType}/{tagPath}

BMS-published System values.

MQTT wildcard examples

All System values: BMS/v1/PUB/Value/System/#

Parameters

Parameter	Description
`pointType`	BMS-published System point type. Values: `HeartbeatTimestampBms`, `HeartbeatEchoBms`, `Status`, `Available`, `GenericPoint`
`tagPath`	Vendor-defined hierarchical tag path.

Message: Point Value

Content Type: application/json

Live value message. Payload envelope is identical for all point types. The semantic meaning of value is determined by the corresponding metadata message.

Payload

Name	Type	Required	Description
`value`	number or null	Yes	Live reading for the point (float). May be null when the BMS has no valid reading available.
`timestamp`	integer	Yes	Unix timestamp in epoch milliseconds (source event time).
`quality`	integer	Yes	`1` = good quality. Any other integer indicates value is not trustworthy

Example payload

1 {
2   "value": 22.96215,
3   "timestamp": 1743620423000,
4   "quality": 1
5 }

1	{
2	"value": 22.96215,
3	"timestamp": 1743620423000,
4	"quality": 1
5	}