Skip to main content

Understanding IoT Health Statuses

Updated this week

Prerequisites

We highly recommend reading the ״Introduction to IoT Health Information״ article to learn about the different alert sources in the platform, when how to view them, how to access assistance, and more.

Introduction

in this article, you will learn how to read, understand, and respond to IoT alerts.
You can access and handle various alerts on the four different types of network devices: EP, Node, Routers, and Access Points.

Our IoT monitoring system detects issues affecting the connectivity status and the functionality of the IoT devices or issues that might affect them soon.

The status of the installed IoT devices is visible across various relevant areas in the Augury platform and provides an indication of the device connectivity status:

  • Is the device online and functioning properly

  • If the device has an issue that needs to be addressed to restore proper connectivity

  • If the device's connectivity is affected by issues from other devices.

When we detect an issue, we will provide you with the relevant information to solve it.

Router and Access Point statuses

Alert

Description

Required actions

Router Not sending data (1)

A problem with the router is blocking the connection with the node.

No data from this Router was received within more than 12 hours

Check for issues on the relevant router to restore connectivity.

If the router is provided by Augury (the information is available under the “Information” tab (2))

The following article can be of assistance:

image.png

Access Point Not sending data

No data was received from this Access Point within more than 12 hours

Inspect the access point and verify it is connected to the power source.

Node statuses

Status

Description

Required actions

Not sending data

  • If no data was received from the node for more than 12 hours, but we did receive data through the router, then it’s assumed there is a problem with the node.

  • This status also covers cases when the Node Never Communicated after activation - no data samples or status from the Node until now.

  • Inspect the node.

  • Check this node to find out why it isn’t sending data and restore its connectivity.
    Use the Troubleshooting guide to assist you.

  • If the basic troubleshooting steps indicate that the Node needs to be replaced.

image.png

Registered without mapped endpoints:

The Node has no linked machine to it

Nodes with this status can be:

  1. Online and available for linking machines and endpoints to them.
    This can be done automatically by our system auto-recovery mechanism (see here how),
    or manually by Augury personnel.

  2. Not sending data (offline) - needs to be inspected to restore connectivity and to maintain the system resilience.

  3. Using the Basic Node Troubleshooting guide to try and solve the issue.

image.png

Offline - Router issue

Data from this node cannot be accessed due to a router issue.

Address the linked Router issue.

image.png

image.png

Endpoint and battery statuses:

Note: If a node or endpoint replacement is required, ensure you verify the correct device type matches the machine and environment characteristics based on the “HW compatibility diagram.”

Status

Description

Required actions

Not sending data

No data samples were received from this endpoint in more than 12 hours.

Inspect endpoint:

  • Check this endpoint to discover why it isn’t sending data and restore its connectivity.

  • This Endpoint Troubleshooting guide will help you.

  • If the problem is that the endpoint isn’t mapped, you can map it with the EP mapping tool.

  • You can also contact Augury support to restore connectivity.

image.png

Invalid data

Data from this endpoint has an issue that affects monitoring capabilities.

  • Replace the battery for alerts labeled “invalid data” on an EP with a low battery.

  • Replace the EP: If the invalid alert isn’t battery-related, consider replacing the endpoint.

image.png

Out of position

The endpoint may have moved, rotated, or fallen.

Tip:
Locate the endpoint by serial number, and ensure it is either on the machine or next to it.

Locate the EP if found fallen or loosely mounted -

  • Remount or Tighten the EP: Reattach it to the machine and ensure it is adequately secured.

    For more details, refer to the Halo Endpoint Installation Guide.

  • Clear the Alert in the platform: Click the blue banner on the EP alert to clear it. This action signals to Augury that the data is valid and can be trusted.


Note: For non-standard machine configurations or specific orientation questions, consult your Augury contact or Augury support.

image.png

Endpoint and battery statuses- continue:

Offline - Router issue

Data from this EP cannot be accessed due to a router issue.

Address the issue on the linked Router.

image.png

Offline - Node issue

Data from this EP cannot be accessed due to a node issue.

Address the issue on the linked Node.

image.png

"Low Battery"

Plan battery replacement

Make sure you have an available battery for replacement".

image.png

Drained battery

The battery level is critically low – a new battery is needed.

"Low battery”

  • If the battery is critically low, it must be changed ASAP.

  • Warning: if you have an HZ/EX endpoint type, do not open it; replace the whole sensor.

Note: The new battery status may take up to 30 minutes to appear on the Augury platform.

Change battery

Replace the drained battery of this endpoint to avoid connectivity issues.

For 2nd generation battery replacement kit (KT00019), click here.

For 1st generation battery replacement kit (KT00020), click here.

image.png

Power Cycle the Endpoint:
After battery replacement, perform a power cycle on the endpoint and verify that the self-test is successful.
The light should blink blue during this process, indicating a successful operation.

Note: After a while, the light will stop blinking to conserve battery.

Recommendation

Please refer to the “Required actions” field in the IoT Health tab and on the machine's IoT status page for each device's recommended action.

image.png

Did this answer your question?