Airzone
airzone
This integration interacts with the Local API of Airzone HVAC zoning systems.
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 (humidity, temperature) | |
water_heater | Water heater (as a thermostat) | |
select | Mode picker (as switches) |
2 reports below say how a device from this integration behaves in the Home app.
What people report
Airzone local API zones work, but WebServer firmware 4.23/4.25 broke setup for some, and HomeKit exposes only heat/cool modes.
- Works2
- Partly works2
- Not working1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Airzone DHW water heater | Works Local | Water heater entities support addedSaved copyProposed change Add Water Heater entities support for Airzone. As reported by @fredericseiler, Airzone devices may also be able to control a DHW system. ## Type of change - [ ] Dependency upgrade - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [x] New feature (which adds functionality to an existing integration) - [ ] Deprecation (breaking change to happen in the Excerpt saved from GitHub on 2026-10-23. | PR #98401 · 2023-08 | |
| Airzone fan speed devices | Works Local | Fan speeds supported on devices that offer themSaved copyProposed change Now that aioairzone has been updated to v0.5.5, fan mode (fan speeds) support can be added for those devices supporting it. Fan Speed 0 means auto and the other values are different speeds specific to each device (devices may support from 2 up to 8 speeds). ## Type of change - [ ] Dependency upgrade - [ ] Excerpt saved from GitHub on 2026-10-23. | PR #92840 · 2023-05 | |
| Airzone climate zones | Partly works Local | Partly in Home Only Heat and Cool modes exposed, no Fan-only mode | Child zones lack Fan-only mode when exported to HomeKit; HomeKit limitationSaved copyThe problem AirZone local integration only export to HomeKit Bridge Heat and Cool, it is nos posible from HomeKit setup "Only Fan" mode. As you can see below. ### What version of Home Assistant Core has the issue? core-2023.6.1 ### What was the last working version of Home Assistant Core? Any ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Airzone and HomeKit Bridge ### Link to integration documentation on our website https://www.home-assistant.io/integrations/airzone ### Diagnostics information … Excerpt saved from GitHub on 2026-10-23. | Issue #94592 · 2023-06 |
| Airzone climate zones | Partly works Local | Partly in Home Only cool and heat exposed; no fan-only mode; child zone cool does nothing under parent fan-only | Maintainer says HomeKit limits modes; mapping of fan-only to cool is a known limitationSaved copy… your device it will raise an exception: https://github.com/home-assistant/core/blob/be05a749c57a7174839e75376a345bd184e97e0b/homeassistant/components/airzone/climate.py#L204-L207 This prevents the user from accidentally changing the operation mode on slave zones. In the Airzone ecosystem a slave zone can only be turned on or off and the setpoint temperature can be adjusted, but the operation mode (`heat`, `cool`, etc.) can only be changed on the master zone. What I could do is remove the following lines from the `airzone` int Excerpt saved from GitHub on 2026-10-23. | Issue #94665 · 2023-06 |
| Airzone WebServer firmware 4.23/4.25 | Not working Local | Setup fails with unknown error after firmware updateSaved copyI believe I may be experiencing the same underlying issue, although my problem did not begin immediately after a firmware update. Environment • Home Assistant Core: 2026.7.3 • Home Assistant OS (VM on QNAP) • Airzone WebServer firmware: 4.25 • Local API version: 1.81 The official Airzone integration consistently fails during initial configuration with the generic "Unknown error" message. During troubleshooting I manually verified the Local API. The following requests all succeed: POST /api/v1/version → Returns Version 1.81 POST /api/v1/hvac Body: { "systemID": 0, "zoneID": 0 } → Returns a … Excerpt saved from GitHub on 2026-10-23. | Issue #173124 · 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
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- DHCP
Details
| Installs (analytics) | 535 (0.08%) |
|---|---|
| Added in | Home Assistant 2022.4 |
| Set up in the UI | Yes |
| Maintainers | @Noltari |
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.
