Skip to main content

Troubleshooting the alarm when PM2.5 mass concentration above expected bound

A "PM2.5 mass concentration above expected bound" alarm fires when at least 25% of the device's raw PM2.5 readings in the last three-hour period are higher than expected (above 3,000 µg/m³). This often means something is stuck inside the sensor. This article helps you check and fix it.

1. Check whether the readings look stuck or unusually high

A blockage, typically a bug or spider web, is the usual cause. When it happens, the Node tends to show raw PM2.5 values much higher than nearby Nodes, or values "stuck" at very high or very low levels.

2. Clear the blockage

If something appears to be stuck inside the sensor, follow the steps to clean the Node-S airways.

If these steps don't resolve the issue, or you have questions, email support@clarity.io and we'll get back to you shortly.

What's next

Still need a hand? Email us at support@clarity.io or create a support ticket, and our team will get back to you.

Was this helpful?