Why MQTT matters
A monitor that only offers cloud API access cannot do this cleanly. A monitor with a community MQTT bridge is fragile — it depends on someone maintaining the bridge against the vendor's cloud API. A native MQTT monitor just works.
Envora One MQTT topic structure
envora/{device_id}/co2 — CO₂ in ppm, integerenvora/{device_id}/pm25 — PM2.5 in µg/m³, floatenvora/{device_id}/pm1, /pm10 — same unitsenvora/{device_id}/voc — VOC indexenvora/{device_id}/co — CO in ppmenvora/{device_id}/temperature — °C, floatenvora/{device_id}/humidity — %RHenvora/{device_id}/pressure — hPaenvora/{device_id}/lux — luxenvora/{device_id}/dba — dBAenvora/{device_id}/iaq — fused IAQ score 0–100Home Assistant auto-discovery topics under
homeassistant/sensor/envora_{device_id}_{channel}/config.QoS 1 by default; retain flag on the latest reading per channel so reconnecting subscribers see current state immediately.
Setup
For local-only deployments, the device can also run its own embedded broker on port 1883 — useful if you do not have a broker already and want to keep everything offline.