#Node-RED
Zigbee2MQTT → ECLYPSE APEX flow (BACnet objects through the REST API)
The flow from APEX episode #4: it reads the devices published by Zigbee2MQTT and creates the matching BACnet AV/BV points in the APEX through the v2 REST API.
- date
- 23 October 2026
- tested with
- Node-RED · ECLYPSE APEX (REST API v2) · Zigbee2MQTT
- license
- MIT
- tags
- #zigbee2mqtt,#mqtt,#eclypse-apex,#api-rest,#bacnet
flow-zigbee2mqtt-apex.json download
What it does
The flow listens to zigbee2mqtt/bridge/devices, works out which points each device needs (binary → BV, numeric or enum → AV, plus one _Online BV per device), then creates them one at a time in the APEX through the REST API, within a reserved instance range: 3000 to 3999. It then pushes the MQTT values to those objects, and relays to zigbee2mqtt/<name>/set whatever the GFX program writes to the _Cmd objects.
Adapt before running
- the APEX address and the Facilities account;
- the MQTT broker;
- the instance range, if you plug in another source;
- the exception list (devices or exposes to ignore).
Pitfalls
- No
/in Zigbee2MQTT friendly names. - Renaming a device creates new objects; the old ones must be deleted by hand.
- Don’t run it alongside an older manual flow on the same devices.
Full context and the why are in the article.
the article: APEX #4 — MQTT, Node-RED, REST API: the controller that watched the fish go by