Micronova Agua IOT
vincentwolsink/home_assistant_micronova_agua_iot · v1.3.0
Home Assistant integration controlling heating devices (pellet stoves) connected via the Agua IOT platform of Micronova
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
climate | Thermostat | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
select | Mode picker (as switches) |
What people report
Micronova-based pellet stoves (Piazzetta, MCZ, Elcofire, MySuperior) work via the vendor cloud, with an experimental local Bluetooth mode added in 2026. Cloud login and freeze problems recur.
- Works5
- Partly works1
- Requested1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Elcofire stove | Works Cloud | Support addedSaved copyThanks @moonpie Excerpt saved from GitHub on 2026-10-23. | PR #218 · 2025-03 | |
| Micronova water boiler (water_boiler climate) | Works Cloud | Water boiler climate entity support addedSaved copyThe original text was already deleted or overwritten when we archived it. | PR #300 · 2026-08 | |
| Micronova/MCZ stoves with BLE module (T009_) | Works Local | Experimental local Bluetooth mode for reads and writesSaved copySummary - add an experimental `Bluetooth local` connection mode alongside the existing cloud mode - add a Micronova BLE transport for local reads and writes through Home Assistant Bluetooth adapters / proxies - persist the BLE bootstrap metadata in the config entry after the initial cloud bootstrap - simplify the options flow so users can switch to local Bluetooth without dealing with BLE UUIDs - document the local BLE flow, limitations, and tested hardware in the README - treat alarm-like stove states as `off` in the climate entity so Home Assistant does not report `heating` during … Excerpt saved from GitHub on 2026-10-23. | PR #275 · 2026-04 | |
| MySuperior stoves | Works Cloud | Support addedSaved copyThe original text was already deleted or overwritten when we archived it. | PR #159 · 2024-10 | |
| Piazzetta pellet stove | Works Cloud | Login failure in 2023 was Piazzetta API specific; combustion and pellet quality settings addedSaved copyThe original text was already deleted or overwritten when we archived it. | PR #266 · 2026-01 | |
| Micronova Wi-Fi module (Jolly Mec stove) | Partly works Cloud | Controller froze after 0.9.2-beta1; cause traced to cloud API request handlingSaved copyEnvironment - Micronova Wi-Fi module (Jolly Mec) - Home Assistant OS 2025.11.3 - HACS with beta releases enabled at the time - Earlier AguaIOT versions have been stable for years on this hardware --- ## What happened Immediately (literally the next day) after updating the integration to 0.9.2-beta1, the Micronova controller entered a completely unresponsive state at the API level: - still responds to ping - but no TCP ports are open anymore - `curl` and `nc` fail on ports 80, 88, 1234, 8080 - AguaIOT logs show: [code] ` - Home Assistant loses the integration and the config flow crashes The … Excerpt saved from GitHub on 2026-10-23. | Issue #252 · 2025-11 | |
| Newer Micronova/MCZ BLE module (NAVEL_ prefix) | Requested Local | Proposed name-prefix support for newer modules was closed unmergedSaved copySummary Newer Micronova/MCZ BLE modules advertise their local name as `NAVEL_ ` instead of `T009_ `, while keeping the same MAC-derived 6-character suffix. Address-based discovery still works for them, but the name-based matching path in `_find_ble_device` (used both as an explicit-name match and as a prefix-only fallback) rejects these advertisements, which causes BLE recovery to fail when the address-based path doesn't return a `BLEDevice` (e.g. the address candidate window doesn't cover the actual advertised address, or HA's address tracking has expired between cycles). Real-world impact: … Excerpt saved from GitHub on 2026-10-23. | PR #288 · 2026-06 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 567 (0.08%) |
|---|---|
| GitHub stars | 83 |
| Latest version | 1.3.0 (2026-10-21) |
| Set up in the UI | Yes |
| Maintainers | @vincentwolsink |
| License | Apache-2.0 |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
