source/_integrations/airgradient.markdown (2)

53-57: Consider aligning header naming with Home Assistant style
Currently using “Supported functionality” → “Available sensors”. The core docs often use “Supported entities” with sub-sections “Sensors” and “Configuration entities” (no “Available” prefix).

Please verify against the documentation guidelines to ensure consistent section titles.

---

148-152: Known limitations list needs surrounding blank lines & minor wording tweak

• Add a blank line after the bullet list to satisfy markdownlint (MD032).
• Consider changing “is not able to install” → “cannot install” for conciseness.

🧰 Tools

🪛 LanguageTool

[style] ~151-~151: As a shorter alternative for ‘able to’, consider using “can not”.
Context: ...lowing limitations: - The update entity is not able to install updates automatically. You will...

(BE_ABLE_TO)

🪛 markdownlint-cli2 (0.17.2)

151-151: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

source/_integrations/airgradient.markdown (4)

30-35: Consistent bullet formatting in “Use cases”
The new bullets end with periods, whereas other lists (e.g., Supported devices) omit them. For consistency, remove the trailing periods:

- - Monitor indoor and outdoor air quality.
+ - Monitor indoor and outdoor air quality
- - Warn to open windows when CO2 levels are too high.
+ - Warn to open windows when CO2 levels are too high
- - Control ventilation systems based on air quality.
+ - Control ventilation systems based on air quality

---

75-83: Fix grammar in configuration‐entity sensor description
The sentence “instead of set it to control locally” is awkward. Update it to:

A number of configuration entities are available as sensors to automate with if you control the device via the AirGradient dashboard instead of setting it to control locally.

🧰 Tools

🪛 LanguageTool

[grammar] ~79-~79: This phrase is duplicated. You should probably use “LED bar” only once.
Context: ...nds learning offset - Data used for the LED bar - LED bar brightness - Display temperature unit -...

(PHRASE_REPETITION)

🪛 markdownlint-cli2 (0.17.2)

76-76: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)

---

84-102: Clarify “Available configuration entities” structure
This section partially overlaps with the preceding configuration‐entity sensors list. To reduce confusion, consider:

• Renaming the heading to simply “Configuration entities”.
• Grouping entities by type (number, select, switch) with subheadings.
• Adding a brief note that these are non-sensor domains.

---

150-152: Refine wording and list formatting in limitations

• Insert a blank line before the list for readability.
• Change “is not able to install updates automatically” to “cannot install updates automatically”:

- The AirGradient integration currently has the following limitations:
- - The update entity is not able to install updates automatically. You will need to reboot the device manually after installing the update.
+ The AirGradient integration currently has the following limitations:
+
+ - The update entity cannot install updates automatically; you must reboot the device manually after installing the update.

🧰 Tools

🪛 LanguageTool

[style] ~151-~151: As a shorter alternative for ‘able to’, consider using “can not”.
Context: ...lowing limitations: - The update entity is not able to install updates automatically. You will...

(BE_ABLE_TO)

🪛 markdownlint-cli2 (0.17.2)

151-151: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

source/_integrations/airgradient.markdown (1)

131-148: 🛠️ Refactor suggestion

Fix YAML example and wrap in raw tags
The automation example still uses plural keys (triggers, actions) and action: instead of service:, and it lacks a proper {% raw %} wrapper—this will break the rendered docs.

-{% endraw %}
-```yaml
-automation:
-  - alias: "Notify when CO2 level is too high"
-    triggers:
-      - trigger: numeric_state
-        entity_id: sensor.airgradient_carbon_dioxide
-        above: 1000
-
-    actions:
-      - action: notify.mobile_app_your_device
-        data:
-          title: "High CO2 Level Alert"
-          message: >
-            The CO2 level is too high at {{ states('sensor.airgradient_carbon_dioxide') }} ppm.
-            Please consider ventilating the room.
-```
+{% raw %}
+```yaml
+automation:
+  - alias: "Notify when CO2 level is too high"
+    trigger:
+      - platform: numeric_state
+        entity_id: sensor.airgradient_carbon_dioxide
+        above: 1000
+    action:
+      - service: notify.mobile_app_your_device
+        data:
+          title: "High CO2 Level Alert"
+          message: >-
+            The CO2 level is too high at {{ states('sensor.airgradient_carbon_dioxide') }} ppm.
+            Please consider ventilating the room.
+```
+{% endraw %}

source/_integrations/airgradient.markdown (2)

30-35: Refine 'Use cases' bullet phrasing for consistency
The second item could read “Warn you to open windows when CO2 levels are too high” to match the imperative tone of the other bullets.

- - Warn to open windows when CO2 levels are too high.
+ - Warn you to open windows when CO2 levels are too high.

---

103-106: Consider elaborating on the update entity usage
It may be helpful to include the actual entity ID or a sample service call (e.g., update.async_install) so users know how to trigger firmware updates via Home Assistant.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

source/_integrations/airgradient.markdown (1)

131-148: ⚠️ Potential issue

Invalid YAML example for automations
The example still uses the plural keys triggers/actions and action: instead of HA’s required trigger/action and service: fields. This will not parse correctly.

-    triggers:
-      - trigger: numeric_state
+    trigger:
+      - platform: numeric_state
       entity_id: sensor.airgradient_carbon_dioxide
       above: 1000

-    actions:
-      - action: notify.mobile_app_your_device
+    action:
+      - service: notify.mobile_app_your_device
       data:
         title: "High CO2 Level Alert"
         message: >-
           The CO2 level is too high at {{ states('sensor.airgradient_carbon_dioxide') }} ppm.
           Please consider ventilating the room.

source/_integrations/airgradient.markdown (3)

53-59: Consider simplifying heading names
To align with Home Assistant docs conventions, you might drop “Available” and rename:

## Supported functionality

### Sensors

instead of “### Available sensors.”

---

84-90: Align heading to standard schema
Similarly, change:

### Available configuration entities

to:

### Configuration entities

This keeps consistency with other integrations.

---

154-156: Minor style and formatting nits in limitations list

• Surround the list with blank lines for better markdown compliance (MD032).
• Use “cannot” instead of “not able to” for brevity.

-The AirGradient integration currently has the following limitations:
- - The update entity is not able to install updates automatically. You will need to reboot the device manually after installing the update.
+The AirGradient integration currently has the following limitations:
+
+- The update entity cannot install updates automatically. You will need to reboot the device manually after installing the update.
+

🧰 Tools

🪛 LanguageTool

[style] ~155-~155: As a shorter alternative for ‘able to’, consider using “can not”.
Context: ...lowing limitations: - The update entity is not able to install updates automatically. You will...

(BE_ABLE_TO)

🪛 markdownlint-cli2 (0.17.2)

155-155: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting