Skip to main content

Troubleshooting a Late Reading Alarm

A Late Reading alarm means your Node is behind schedule reporting its next reading, so it's been marked offline. This article walks through the common causes and how to fix each one.

A Late Reading alarm can be caused by:

  • The device being powered off
  • Poor cellular reception
  • A cellular network outage
  • Low battery

The device is powered off​

If the device was powered off and you didn't stop recording data on the Dashboard, it's marked offline and raises this alarm. Inspect the device to confirm it's correctly deployed and powered on. If it's been removed from the field, stop recording data on the Dashboard.

Poor cellular reception​

If the device has had poor cellular reception, this alarm may be related — see troubleshooting a Weak Signal alarm.

A cellular network outage​

During a cellular outage, multiple devices usually go offline at once. If that's what you're seeing, check our connectivity partner's status page for reported issues. Clarity often emails you when outages start and end.

Low battery​

If the device has a low battery alongside this alarm, see troubleshooting Power, Battery, and Charging alarms.

None of the above​

If none of those explain it, power cycle the Node-S:

  1. Unplug the solar panel or power adapter from the Node-S power connector.
  2. Wait 30 seconds, then plug it back in, screwing the connector's ring firmly in place.
  3. Listen for the Node-S Power On sound and Connection Successful sound.

Then:

  • If you hear a Low Battery sound instead, charge the device for at least 24 hours.
  • If you hear the Power On sound but not the Connection Successful sound:
    • Check that the antenna is securely attached.
    • If possible, move the device to an area with stronger cell reception. It often helps to test whether the Node connects successfully in your office or somewhere you know has good reception.

If these steps don't resolve the issue, 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.

Last updated on