BESS — Metadata
BESS — Metadata
BESS — Metadata
Subscribe to BMS-published metadata for BESS points.
Direction: Subscribe (receive)
BMS-published metadata for BESS points.
MQTT wildcard examples
BMS/v1/PUB/Metadata/BESS/#Content Type: application/json
Optional fields common to all generic equipment metadata, regardless of identifier mode.
objectName and objectId are required.servesId is optional in Named-object mode.associateId must not be present.Incompatible with EquipmentAssociateMode — validators enforce this via
the parent oneOf.
associateId is required.objectName, objectId, and servesId must not be present.Incompatible with EquipmentNamedObjectMode — validators enforce this
via the parent oneOf.
Content Type: application/json
Optional fields common to all generic equipment metadata, regardless of identifier mode.
objectName and objectId are required.servesId is optional in Named-object mode.associateId must not be present.Incompatible with EquipmentAssociateMode — validators enforce this via
the parent oneOf.
associateId is required.objectName, objectId, and servesId must not be present.Incompatible with EquipmentNamedObjectMode — validators enforce this
via the parent oneOf.
Content Type: application/json
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.
objectName and objectId are required.servesId is optional in Named-object mode.associateId must not be present.Incompatible with EquipmentAssociateMode — validators enforce this via
the parent oneOf.
associateId is required.objectName, objectId, and servesId must not be present.Incompatible with EquipmentNamedObjectMode — validators enforce this
via the parent oneOf.