Troubleshooting a Late Reading Alarm

A late reading alarm indicates that the Node is behind schedule in reporting its next reading and is therefore marked as offline. This anticipated reading is calculated based on the sampling frequency set on the device. The default is ~15min. If you’d like to change this sampling frequency, please see how to do so here

This alarm could be caused by a number of issues including:

  • Poor cellular reception
  • A cellular network outage or other related communications outage
  • Low battery

If the device has had poor cellular reception in the past, this alarm could be related and the Troubleshooting a Weak Signal alarm article should be consulted.

If there is a cellular outage, usually multiple devices will go offline at the same time. If this is the case, you may want to check our connectivity partners’ status page to see if there are any reported issues. 

If your device has low battery and you are also seeing this alarm, please refer to the Troubleshooting device Power, Battery, and Charging alarms.

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.