Skip to content

Add a note on new number platform for airq integration #40390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 12, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions source/_integrations/airq.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ ha_domain: airq
ha_config_flow: true
ha_platforms:
- sensor
- number
ha_integration_type: hub
---

Expand Down Expand Up @@ -96,6 +97,10 @@ After the integration has been initialized, the user can configure any of the fo

- **Clip negative values**. Default: `on`. For baseline calibration purposes, certain sensor values may briefly become negative. The default behavior is to clip such values to 0.

## LED Control

In addition to sensor readings, this integration exposes the brightness of the device’s LED strips as a `number` entity named `number.<device_name>_led_brightness`. You can set the brightness (0–100) manually from the Overview panel or in automations. Setting it to 0 will turn the LEDs off.

## Troubleshooting

For troubleshooting or when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics) and restart the integration. As soon as the issue reoccurs stop the debug logging, which will trigger the download of the debug log file.
Expand Down