jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update HomeKit Bridge documentation to include 2024 US AQI PM2.5 cutoffs (#33576)

Browse Source 
Co-authored-by: J. Nick Koston <nick@koston.org>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
This commit is contained in:
Sarabveer Singh 2024-07-04 23:17:32 -04:00 committed by GitHub
parent a0351be0d7
commit c08aa6df2d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
source/_integrations/homekit.markdown
View File

@ -675,3 +675,15 @@ With either strategy, the accessory will behave as if it's the first time the ac
The HomeKit integration remembers a public key for each paired device. Occasionally the public key for a device pairing will be missing because of pairing failures. Suppose one or more devices show the accessory as unavailable. In that case, it may be necessary to unpair and re-pair the device to ensure the integration has the public key for each paired client. The `homekit.unpair` service will forcefully remove all pairings and allow re-pairing with the accessory. When setting up HomeKit from the UI, this avoids the sometimes time-consuming process of deleting and create a new instance. The HomeKit integration remembers a public key for each paired device. Occasionally the public key for a device pairing will be missing because of pairing failures. Suppose one or more devices show the accessory as unavailable. In that case, it may be necessary to unpair and re-pair the device to ensure the integration has the public key for each paired client. The `homekit.unpair` service will forcefully remove all pairings and allow re-pairing with the accessory. When setting up HomeKit from the UI, this avoids the sometimes time-consuming process of deleting and create a new instance.
The accessory will behave as if it's the first time the accessory has been set up, so you will need to restore the name, group, room, scene, and/or automation settings. The accessory will behave as if it's the first time the accessory has been set up, so you will need to restore the name, group, room, scene, and/or automation settings.
#### Air Quality Sensor Entities
HomeKit provides five values to represent air quality: Excellent, Good, Fair, Inferior, and Poor. For PM2.5 sensor entities in Home Assistant, the raw density value (µg/m3) is used to determine the corresponding value based on the [2024 US AQI](https://www.epa.gov/system/files/documents/2024-02/pm-naaqs-air-quality-index-fact-sheet.pdf) standard. The mapping is as follows:
| HomeKit | US AQI | PM2.5 µg/m³ |
|-----------|------------------------------------------|---------------|
| Excellent | Good (0-50) | 0.0 to 9.0 |
| Good | Moderate (51-100) | 9.1 to 35.4 |
| Fair | Unhealthy for Sensitive Groups (101-150) | 35.5 to 55.4 |
| Inferior | Unhealthy (151-200) | 55.5 to 125.4 |
| Poor | Very Unhealthy (201+) | 125.5+ |