Common Device status alarms and troubleshooting guide
The Device Status page shows you real-time alarms for your devices. This guide is your glossary: it lists the alarms you might see, what each one means, what triggers it, and where to go to fix it. For a tour of the status page itself, see the Device Status Details page.
So you know: "At least 25% of readings in the last 3-hour period" and similar criteria below describe exactly when each alarm activates. Alarms clear automatically once the underlying problem subsides.
Activity alarms
| Alarm | What it means | When it triggers | How to fix it |
|---|
| Late reading | The Node is behind schedule reporting its next reading and is now marked offline. | Specific to each device, based on its sampling frequency, sampling period, and upload time. | Troubleshoot a Late Reading alarm |
PM sensor alarms
| Alarm | What it means | When it triggers | How to fix it |
|---|
| PM2.5 mass concentration above expected bound | Raw PM2.5 is higher than expected, which may indicate a sensor malfunction. | At least 25% of readings in the last 3-hour period. | Troubleshoot PM2.5 above expected bound |
| PM2.5 mass concentration stuck to zero | Consecutive readings show zero raw PM2.5, which may indicate a fan or laser diode malfunction. | 100% of readings in the last 24-hour period. | Troubleshoot PM2.5 stuck at zero |
| Intermittent PM sensor data (PM flapping) | The Node's communication with the PM sensor is intermittent, which may indicate a malfunction. | At least 75% of readings in the last 3-hour period. | If it persists, the device needs replacing — contact support@clarity.io. |
| PM sensor not responding | The Node can't communicate with the PM sensor, which may indicate a malfunction. | 100% of readings in the last 3-hour period have no PM data. | If it persists, the device needs replacing — contact support@clarity.io. |
NO₂ sensor alarms
| Alarm | What it means | When it triggers | How to fix it |
|---|
| NO₂ readings out of expected range | Raw NO₂ readings are outside the expected range, which may indicate a malfunction. | At least 25% of readings in the last 3-hour period are outside -500 to 500 ppb. | Troubleshoot NO₂ out of range |
| Intermittent NO₂ sensor data (NO₂ flapping) | The Node's communication with the NO₂ sensor is intermittent, which may indicate a malfunction. | At least 75% of readings in the last 3-hour period have a sensor error. | If it persists, the device needs replacing — contact support@clarity.io. |
| NO₂ sensor not responding | The Node can't communicate with the NO₂ sensor, which may indicate a hardware malfunction. | 100% of readings in the last 3-hour period have no NO₂ data. | Contact support@clarity.io. |
Internal temperature / humidity sensor alarms
| Alarm | What it means | When it triggers | How to fix it |
|---|
| Temperature readings out of expected range | T-RH sensor readings are outside the expected range, which may indicate a malfunction. | At least 25% of readings in the last 3-hour period are outside -40 to 70 °C. | Contact support@clarity.io. |
| T-RH sensor not responding | The Node can't communicate with the T-RH sensor, which may indicate a malfunction. | 100% of readings in the last 3-hour period have no valid T-RH data. | Contact support@clarity.io. |
| On-board sensor module not responding | The Node can't communicate with the entire on-board sensor module, which may indicate a malfunction. | — | Contact support@clarity.io. |
Communication alarms
| Alarm | What it means | When it triggers | How to fix it |
|---|
| Weak Signal | Cellular signal at the device may be weak. This doesn't necessarily stop data, but it raises the risk of intermittent data. | At least 75% of readings in the last 3-hour period rate the signal as weak. | Troubleshoot a Weak Signal alarm |
Power alarms
| Alarm | What it means | When it triggers | How to fix it |
|---|
| Low battery | The Node's battery is very low. | At least 75% of readings in the last 24-hour period have the battery below 20%. | Troubleshoot Power, Battery, and Charging alarms |
| Too cold to charge battery | It's too cold to safely charge the battery. If it persists, the battery will fully deplete. | At least 75% of readings in the last 24-hour period have a temperature below 0 °C. | Troubleshoot Power, Battery, and Charging alarms |
| Too hot to charge battery | It's too hot to safely charge the battery. If it persists, the battery will fully deplete. | At least 75% of readings in the last 24-hour period have a temperature above 40 °C. | Troubleshoot Power, Battery, and Charging alarms |
| Battery hardware charging issue (faulty battery thermistor) | The battery can't charge due to a hardware issue. | At least 75% of readings in the last 24-hour period report an inability to charge. | If it persists, the device needs replacing — contact support@clarity.io. |
Accessory Module alarms
| Alarm | What it means | When it triggers | How to fix it |
|---|
| Module not responding | The Node can't communicate with the Module. | 100% of readings in the last 3-hour period have no data from the Module. | Troubleshoot Accessory Module alarms |
| Unpaired module detected | The Node detects a Module is present, but none was paired to it. | At least 25% of readings in the last 3-hour period have this error. | Troubleshoot Accessory Module alarms |
| Module paired but not detected | The Node was paired with a Module, but none is detected. | At least 25% of readings in the last 3-hour period have this error. | Troubleshoot Accessory Module alarms |
| Module power error | The Node is having trouble powering the Module. | At least 25% of readings in the last 3-hour period have this error. | Troubleshoot Accessory Module alarms |
Still stuck?
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
Was this article helpful?
Yes, thanks! / Not really
Still need a hand? Email us at support@clarity.io or create a support ticket, and our team will get back to you.