Air quality monitor with API, MQTT and Home Assistant support

Many monitors advertise an API but it turns out to be partner-only, rate-limited to one request per hour, or paywalled behind a higher plan. Before buying, check: (1) is the API documented publicly; (2) is it available without payment for home users; (3) what is the rate limit; (4) does it cover both current and historical reads; (5) does it support webhooks for event-driven workflows.

Envora One's API meets all five. JSON over HTTPS, full historical reads, no rate limits for personal household use, signed webhooks for event-driven workflows.

Native MQTT means the device publishes directly to your broker with auto-discovery topics — Home Assistant picks the sensors up automatically, and your existing observability stack (Telegraf, Node-RED, anything subscribing to MQTT) can ingest them with no extra work.

Community MQTT means someone wrote a bridge between the vendor's cloud API and MQTT — fragile, rate-limited, dependent on someone maintaining the bridge.

Envora One is native: each device publishes to your broker, with the topic structure documented and auto-discovery enabled by default.

First-class Home Assistant support means the vendor maintains the integration and every sensor channel is exposed as an entity from day one. Community support means a forum user wrote an integration that may or may not still work.

Envora One ships with first-class Home Assistant support: 11 channels per device, each as a sensor entity, available via MQTT auto-discovery or REST API.

Envora One includes: REST API (JSON), MQTT broker (with auto-discovery), webhooks (signed), CSV export, first-class Home Assistant support, local-only mode (no cloud account required), 3-year history retention on the free home plan.

For organisations who need it: Envora Fleet adds API rate-limit tiers, scheduled report exports, signed webhooks and SSO at Estate and above. See Fleet · See developer docs.