Overview
Wireless tracking relies on Bluetooth tags, gateways, and cellular connectivity. When any component experiences an issue, scan data may be delayed, missing, or inaccurate.
This guide provides clear, actionable steps for resolving the most common wireless tracking issues found in the Wireless Tracking Setup Guide.
Troubleshooting Overview Table
Issue | Cause | Details | How to Fix It |
No beacon readings | Reading delay | Gateways may take up to 10 minutes (plug-in) or several hours (battery-powered) to report. | Wait for the update interval to pass; do not assume the item is missing immediately. |
Gateway has no power (no light on device) | Gateway unplugged or not powered | Gateways must have power to scan and transmit. | Check power cord, USB plug, and outlet; ensure the power source is active. |
Tag is not reading | Beacon not powered on | Tag is not broadcasting a Bluetooth signal. | Press the center button on the tag and check for a green light. |
Gateway flashing red | Configuration issue | Indicates a system configuration problem. | Contact ToolWatch support for assistance. |
RSSI set too high | Signal threshold too strict | Gateway cannot detect weak tag signals if RSSI filter is too aggressive. | Lower RSSI value (ex: from –50 to –75). Minimum recommended: –70. |
Readings only showing on some gateways | Gateway overlap or clustering | Gateways placed too close together may create overlapping ranges. | Spread gateways apart or adjust RSSI settings to reduce overlap. |
Delayed or infrequent scans | Gateway update frequency | Battery-powered gateways update every 4 hours; plug-in gateways update every ~10 minutes. | Confirm gateway type and expected interval; do not rely on minute-by-minute updates. |
Detailed Troubleshooting Steps
No Beacon Readings
If an item shows no recent scans:
Wait at least 10 minutes for plug-in gateways
Wait up to 4 hours for battery-powered gateways
Verify tag is assigned to the correct item
Ensure the tag is attached to the tool
Longer delays are normal depending on gateway type.
Gateway Power Issues
Signs:
No light on the gateway
Gateway has stopped reporting scans
Fix:
Confirm the power cord is securely plugged in
Try a different outlet
Check the USB wall plug for damage
Verify that the antenna connection is tight
Tag Is Not Powering On
If the beacon is not broadcasting:
Press the center button
Look for a green light
If no light appears, the tag may be damaged or depleted (BLE battery article coming soon)
Gateway Flashing Red
A flashing red LED indicates a configuration problem.
Fix:
Contact your ToolWatch support representative.
Do not attempt to reconfigure the gateway on your own.
RSSI Settings Too High
RSSI (signal strength threshold) controls which tag signals the gateway accepts.
A higher (less negative) RSSI value filters out weaker signals
A lower (more negative) RSSI value allows more signals to be received
Fix:
Lower the RSSI setting:
Example: Reduce from –50 to –75
Minimum recommended setting: –70
This increases the gateway’s sensitivity to tags.
Gateway Overlap
When gateways are too close together:
Some gateways may pick up tags while others do not
Data may look inconsistent or duplicated
Fix Options:
Move gateways farther apart
Reduce RSSI sensitivity
Review the physical layout for obstructions or interference
Scan Delays
Different gateway types report at different intervals:
Plug-in gateways: approx. every 10 minutes
Battery-powered gateways: approx. every 4 hours
This is normal behavior.
Review scan timestamps before assuming an issue.
Battery-Powered vs Plug-In Gateway Behavior
Plug-In Gateways:
Update every 10 minutes
Provide more consistent scans
Ideal for indoor environments and high-movement areas
Battery-Powered Gateways:
Update every 4 hours
Designed for areas without power access
Expected to report less frequently
Understanding scan frequency helps prevent misinterpretation of missing data.
When to Contact Support
Contact ToolWatch support if:
A gateway continues flashing red
Multiple gateways stop reporting
Scan data is consistently missing or incorrect
You suspect a configuration issue
Tools with attached tags are never scanning
A location’s scan coverage unexpectedly drops