Supported integrations
MQTT broker — native, no community bridge. Devices publish per-channel topics with Home Assistant auto-discovery enabled by default. Topic structure: `envora/{device_id}/{channel}` for live values, `envora/{device_id}/iaq` for the fused score.
Webhooks — HTTPS POST on alert events, signed with HMAC-SHA256. Retries with exponential backoff up to 24 hours. Signature verification documented and example code provided.
CSV export — full historical export from the dashboard, scoped by device and date range.
Home Assistant — first-class, every channel as a sensor entity via MQTT auto-discovery.
Example use cases
- Stream CO₂ readings into InfluxDB / Grafana for long-term retention beyond Envora's 3-year window.
- Push a Slack alert when PM2.5 in the kitchen exceeds a threshold (webhook → your webhook receiver → Slack API).
- Build a tenant-safe public dashboard using the REST API and your own visualisation stack.
- Integrate with a building management system (BMS) over Modbus by translating MQTT to Modbus with a small adaptor.
Data ownership and local-only mode
If Envora disappears tomorrow, your devices keep running and your data keeps flowing — that is a deliberate architectural choice, not an accident.