Pump — Metadata
Pump — Metadata
Subscribe to BMS-published metadata for Pump points.
Direction: Subscribe (receive)
Channel
BMS-published metadata for Pump points.
MQTT wildcard examples
- All Pump metadata:
BMS/v1/PUB/Metadata/Pump/#
Parameters
Message: Pump PumpSpeed Metadata
Content Type: application/json
Payload
Measurement fields for PumpSpeed. Typical engUnit: RPM. The identifier (named-object XOR associate) and measurement (engUnit XOR stateText) constraints are independent and enforced by EquipmentMeasurementModeBase.
Requires a non-empty engUnit string (mutually exclusive with stateText).
Required for state/status/alarm points that carry no engineering unit.
Example payload
Message: Pump Available Metadata
Content Type: application/json
Payload
Optional fields common to all generic equipment metadata, regardless of identifier mode.
Object Mode
objectNameandobjectIdare required.servesIdis optional in Named-object mode.associateIdmust not be present.
Incompatible with EquipmentAssociateMode — validators enforce this via
the parent oneOf.
Associate Mode
associateIdis required.objectName,objectId, andservesIdmust not be present.
Incompatible with EquipmentNamedObjectMode — validators enforce this
via the parent oneOf.
Example payload
Message: GenericEquipment GenericPoint Metadata
Content Type: application/json
Payload
Field fragment for a vendor-specific or unmapped GenericPoint. processArea is required.
engUnit and stateText are both optional but mutually exclusive — include at most one. See the two variants below.
Object Mode
objectNameandobjectIdare required.servesIdis optional in Named-object mode.associateIdmust not be present.
Incompatible with EquipmentAssociateMode — validators enforce this via
the parent oneOf.
Associate Mode
associateIdis required.objectName,objectId, andservesIdmust not be present.
Incompatible with EquipmentNamedObjectMode — validators enforce this
via the parent oneOf.