What the possible Device status alarms are and how to troubleshoot them.
The Clarity Device Status page provides you with the real-time detailed status of your Clarity devices. This article will go into detail about the possible Clarity device alarms you may encounter with information on how to troubleshoot.
If you’d like an overview of the Clarity Device Status page, please refer to Understanding the Device Status Details page.
|
Type |
Possible Alarms |
Description |
Criteria for Alarm |
How to troubleshoot |
|
Activity |
Late reading |
The Clarity Node is behind schedule in reporting its anticipated next reading and it is now marked offline. |
Specific to each device based on device settings for sampling frequency, sampling period, and data upload time |
|
|
PM sensor |
PM2.5 mass concentration above expected bound |
The raw PM2.5 mass concentration above expected bound. This might indicate a sensor malfunction. |
At least 25% of readings in the last 3-hour period |
Troubleshooting when PM2.5 mass concentration is above expected bound |
|
PM sensor |
PM2.5 mass concentration stuck to zero |
Several consecutive sensor readings show zero raw PM2.5 mass concentration. This might indicate a fan or laser diode malfunction |
100% of readings in the last 24-hour period |
Troubleshooting when PM2.5 mass concentration is stuck to zero |
|
PM sensor |
Intermittent PM sensor data (PM flapping) |
The Clarity Node’s ability to communicate with the PM sensor is intermittent. This might indicate a sensor malfunction |
At least 75% of the readings in the last 3-hour period |
If the alarm persists, the device will need to be replaced. Please contact the Support team to start this process. |
|
PM sensor |
PM sensor not responding |
The Clarity Node is unable to communicate with the PM sensor. This might indicate a sensor malfunction |
100% of the readings in the last 3-hour period have no PM data |
If the alarm persists, the device will need to be replaced. Please contact the Support team to start this process. |
|
NO₂ sensor |
NO₂ readings out of expected range |
Several raw NO₂ sensor readings show concentrations out of the expected range. This might indicate a sensor malfunction |
At least 25% of readings in the last 3-hour period where the raw NO₂ readings are outside the range of -500 to 500ppb. |
Troubleshooting the alarm when NO2 readings out of expected range |
|
NO₂ sensor |
Intermittent NO₂ sensor data (NO₂ flapping) |
The Clarity Node’s ability to communicate with the NO₂ sensor is intermittent. This might indicate a sensor malfunction |
At least 75% of readings in the last 3-hour period have a sensor error. |
If the alarm persists, the device will need to be replaced. Please contact the Support team to start this process. |
|
NO₂ sensor |
NO₂ sensor not responding |
The Clarity Node is unable to communicate with the NO₂ sensor. There might be a hardware malfunction. |
100% of the readings in the last 3-hour period have no NO₂ data |
|
|
Internal T/RH sensor |
Temperature readings out of expected range |
Several T-RH sensor readings show temperatures out of the expected range. This might indicate a sensor malfunction. |
At least 25% of the readings in the last 3-hour period are outside the range of -40 to 70°C |
|
|
Internal T/RH sensor |
T-RH sensor not responding |
The Clarity Node is unable to communicate with the T-RH sensor. This might indicate a sensor malfunction |
100% of readings in the last 3-hour period have no valid T-RH data |
|
|
All Sensors |
On-board sensor module not responding |
The Clarity Node is unable to communicate with the entire on-board sensor module. This might indicate on-board sensor module malfunction |
||
|
Communication |
Weak Signal |
Cellular signal at the device location may be weak. This may not necessarily affect regular transmission of data but increases the risk of intermittent data. |
At least 75% of readings in the last 3-hour period where the signal is rated as weak |
|
|
Power |
Low battery |
The Node’s battery is very low. |
At least 75% of readings in the last 24-hour period where the battery is below 20% |
|
|
Power |
Too cold to charge battery |
It is too cold to safely charge the Node’s battery. If this condition persists the battery will be completely depleted. |
At least 75% of readings in the last 24-hour period have a T below 0°C |
|
|
Power |
Too hot to charge battery |
It is too hot to safely charge the Node’s battery. If this condition persists the battery will be completely depleted. |
At least 75% of readings in the last 24-hour period have a T above 40°C |
|
|
Power |
Battery hardware charging issue (Faulty battery thermistor) |
The Clarity Node battery is unable to charge due to a hardware issue. |
If at least 75% of readings in the last 24-hour period have reported an inability of charge for the device |
If the alarm persists, the device will need to be replaced. Please contact the Support team to start this process. |
|
Accessory Module |
Module not responding |
The Clarity Node is unable to communicate with the accessory module |
100% of the readings in the last 3-hour period have no data from the module |
|
|
Accessory Module |
Unpaired module detected |
The Clarity Node has detected an accessory module is present, but no accessory module was paired to the Node. |
At least 25% of readings in the last 3 hour period have this error |
|
|
Accessory Module |
Module paired but not detected |
The Clarity Node was paired with an accessory module, but no accessory module has been detected by the Node. |
At least 25% of readings in the last 3-hour period have this error |
|
|
Accessory Module |
Module power error |
The Node is having issues in powering the accessory module |
At least 25% of readings in the last 3-hour period have this error |
If these steps are not resolving the issue or if you have questions, please contact our Support team and we will get back to you shortly.