Awair Local
homebridge-awair-local · v2.2.4
Adds Awair air monitors with CO2, TVOC, PM and climate sensors to HomeKit over the local API.
What it says it supports
Brands
- Awair
Devices it names
- Awair Mint
- Awair Omni
- Awair 2nd Edition
- Awair Element
Shows up in Apple Home as from its README
Sensor readings in its code
What people report
Works with Awair local API devices such as Awair 2nd Edition and Elements; v2.x had a duplicate-device bug that was fixed.
- Works2
- Partly works1
| Device | Status | What they said | Source |
|---|---|---|---|
| Awair air quality monitors | Works | Awair Local keeps traffic on LAN; four plugin options confusingSaved copyWith Awair, use Awair Local. That’s the one that keeps all the traffic on your LAN. Excerpt saved from Arctic Shift Reddit archive on 2026-10-22. | Reddit comment · 2021-01 |
| Awair Element | Works | Duplicate devices after 2.x upgrade, fixed after report.Saved copy… being created. I observed this behavior after doing a manual upgrade; I modified my legacy HB 1.x "accessories" into the new platforms object, so all my Awair Elements were manually enumerated: While working on this, some of my Awairs dropped off my wifi briefly. I believe this caused an issue where the `identity` value computed by `deviceIdentity()` resolved to the serial or IP I had configured. When the devices came back online, `deviceIdentity()` resolved to the `device_uuid`, creating a new device and leaving the version of the HAP accessory whose HAP ID had been generated from the IP as … Excerpt saved from GitHub on 2026-10-22. | Issue #33 · 2026-08 |
| Awair 2nd Edition (firmware 1.0.9) | Partly works | Works locally; PM10 shown is legacy dust value (always 0), model/serial not read initially.Saved copyTo the first comment on PM10 ... The original Awair device reported " aggregated dust". As HomeKit does not have a "dust" characteristic, "PM10" was repurposed in the Awair plugin for reporting "dust". It will be "0" for all other devices. I found myself going in circles as the Awair documentation was inconsistent. The chart shows my findings: I am pretty sure that the index.js could be updated to only add the PM10 characteristic to the Air Quality sensor if you have an original Awair device. I am a bit of a dabbler when it comes to code also but do see that a GET request to: … Excerpt saved from GitHub on 2026-10-22. | Issue #2 · 2020-03 |
Gathered from the plugin’s GitHub issues, pull requests, discussions, wiki and docs, and from r/homebridge. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local
Awair Local API
You’ll need
- Awair Local API enabled
- Node 22 or 24
Compatibility
| Verified by Homebridge | Yes |
|---|---|
| Homebridge versions | >=2.0.0 |
| Homebridge 2.0 | Yes |
| Node.js | >=22.0.0 <25 |
| Settings in Homebridge UI | Yes |
| Matter | No |
| Platform name | AwairLocal |
| License | MIT |
Community signals
| Downloads a week | 18 |
|---|---|
| Downloads a month | 228 |
| GitHub stars | 24 |
| Open issues | 2 |
| Closed issues | 13 |
| Last code push | 2026-10-06 |
| Latest version | 2.2.4 (2026-10-05) |
| First published | 2020-02-09 |
| Releases | 52 |
In ReReHome
Whatever this plugin publishes reaches Apple Home as a normal HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Bridges get their own settings page listing the accessories behind them.
HomeKit services in its code
Found by scanning the published npm package. A plugin can register a service only for some devices.
- AirQualitySensor
- CarbonDioxideSensor
- HumiditySensor
- LightSensor
- TemperatureSensor
