Use this guide when several assets stop updating in the same area, a gateway has raised an offline alert, or assets expected to be near a gateway are not being detected.
First, identify the pattern
Record the affected site, zone, gateway and approximate time the issue began.
Then compare the impact:
- If one asset is affected, start with its hardware assignment, battery or power, and its expected range.
- If several assets in the same zone are affected, the gateway, its coverage or its connection is the more likely cause.
- If data appears less often than expected but still arrives, check the gateway reporting interval before treating it as an outage.
See Troubleshoot missing or stale asset data for asset-specific checks.
Check the gateway in Command
- Open the site and select the relevant zone.
- Select the gateway and confirm it is linked to the correct zone.
- Check whether it is positioned correctly on the map. A fixed gateway's map position is used as the inherited location for assets it sees.
- Check whether Offline alerting is enabled. When enabled, Command sends an alert if the gateway does not report for five minutes.
- Check the configured reporting interval. This limits how often the gateway reports nearby sensors. A longer interval can make otherwise healthy assets appear to update less frequently.
See Configure gateways in a zone.
Check the physical setup
Where it is safe and permitted to do so:
- Confirm the gateway has power and that any normal power indicators are present.
- Confirm its network or cellular connection is available, as applicable to that gateway.
- Confirm it has not been moved, obstructed, or placed outside the coverage needed for the assets it should see.
- If your operational procedure permits it, restart the gateway and allow it time to reconnect.
- Check whether nearby assets begin reporting again.
Do not change gateway credentials or configuration unless you are authorised to do so.
Escalate with the right detail
If the gateway remains offline or coverage is still affected, contact your reseller if you have one; otherwise contact OnSight directly.
Include the gateway identifier, site and zone, when it was last known to be working, affected asset names or hardware identifiers, the connectivity and power checks completed, and screenshots of any offline alert.