Troubleshooting¶
Preliminary Document
This is a preliminary guide. Product images are rendered previews. Component selection is ongoing. Content is subject to change without notice.
LED Status Codes¶
Press the service button (short press through the pinhole on the side of the enclosure) or tap via NFC (CB Admin) to activate the LEDs for 5 minutes. LEDs are off by default (dormant mode) to keep the device discreet.
LED1 — System & Wirepas Status (all variants)¶
| LED Color | Pattern | Meaning | Action |
|---|---|---|---|
 Green |
Solid | Wirepas operational — sink connected | No action needed |
 Blue |
Solid | Wirepas network joined, no sink route | Check that a sink/gateway is online and reachable |
 Yellow |
Solid | Powered, no Wirepas network | Verify Wirepas config (network address, channel, keys) via NFC or Web UI |
 White |
Breathing | Device is booting | Wait 30–60 seconds for boot to complete |
 Red |
Counted blinks | Self-test error | Count the blinks — see Error Codes below |
 Amber |
Counted blinks | Self-test warning | Count the blinks — see Warning Codes below |
 Purple |
Variable | User-controlled pattern (commanded via Wirepas) | Normal — remote command in progress |
LED2 — Gateway Backhaul Status (232012, 232013 only)¶
| LED Color | Pattern | Meaning | Action |
|---|---|---|---|
| Green |
Solid | WiFi + MQTT fully connected | No action needed |
| Blue |
Solid | WiFi connected, MQTT not reached | Check MQTT broker URI, port, credentials, and TLS certificates |
| Blue |
Breathing | WiFi connecting | Verify SSID, password, and WiFi signal strength |
| Yellow |
Solid | No backhaul configured | Configure WiFi and MQTT via NFC or Web UI |
| White |
Breathing | ESP32 OTA update in progress | Wait for update to complete |
| Red |
Fast blink | Gateway fault | Reboot the device; contact support if fault persists |
For the complete LED state machine and priority rules, see the UI Behavior Specification.
Self-Test Error & Warning Codes¶
The device runs a self-test at every boot. If problems are detected, LED1 shows counted blink patterns during the 5-minute active window. Count the number of blinks and match the color (red or amber) to identify the issue.
Each error code blinks twice (for easy counting), pauses, then moves to the next code if multiple issues exist. The pattern repeats for the full 5-minute active window.
Error Codes (RED blinks -- action required)¶
| RED Blinks | Code | Meaning | What To Do |
|---|---|---|---|
| 1 long | E01 | Board not recognized | Contact support -- possible hardware defect |
| 2 long | E02 | Wrong firmware installed | Re-flash with the correct firmware for this variant |
| 3 long | E03 | Battery not connected | Open enclosure, verify the battery JST connector is fully seated |
| 4 long | E04 | Battery or charger fault | Replace battery; if fault persists, replace unit |
| 5 long | E05 | NFC chip not detected | Contact support -- soldering or component defect |
| 6 long | E06 | WiFi module not responding | Reboot the device; if fault persists, contact support |
| 1 short + 1 long | E07 | Clock failure | Contact support -- crystal defect |
Warning Codes (AMBER blinks -- device operates, investigate when possible)¶
| AMBER Blinks | Code | Meaning | What To Do |
|---|---|---|---|
| 1 long | W01 | Battery low | Device is functional; battery will charge when AC power is applied |
| 2 long | W02 | Battery deeply discharged | Leave device plugged in for 2+ hours to recover |
| 3 long | W03 | Unexpected extension board | Verify correct extension board is installed for this variant |
| 4 long | W04 | No AC power at boot | Verify device is plugged in to a powered outlet |
Counting Blinks
A long blink is approximately 250 ms ON / 250 ms OFF. A short blink is a quick 100 ms flash. Each error code is shown twice in a row, followed by a brief pause. If you see multiple groups of different blink counts, the device has multiple issues -- note each count and color.
Device Continues to Operate
The self-test is diagnostic only. Even if errors are detected, the device will attempt to join the Wirepas network and operate normally. Error codes help identify assembly issues or degraded hardware but do not prevent the device from functioning.
Service Button Actions¶
The service button is recessed inside the enclosure. Access it through the pinhole on the side of the enclosure using a SIM-eject tool or paperclip.
| Action | How | Result |
|---|---|---|
| Power on | Press and hold for 5 seconds (from off state) | Device powers on; LEDs active for 5 minutes |
| Status check | Short press (< 1 second) | LEDs show system status for 5 minutes |
| Reboot | Press and hold for ~3 seconds | Device reboots (LED blinks RED to confirm before reboot) |
| Factory reset | Hold button while plugging in power; keep holding for 10 seconds | All configuration erased, device returns to factory defaults |
Battery-Preserving Off State
The device ships powered off. On battery-backup variants (232011, 232013), the battery charges when plugged in but the device does not run until powered on via the button or NFC.
Factory Reset
Factory reset erases all stored configuration (Wirepas, WiFi, MQTT, NTP). The device will need to be reconfigured from scratch. Use this only as a last resort. Factory reset requires a physical power cycle while holding the button for 10 seconds, preventing accidental resets.
Common Issues¶
Device Does Not Power On¶
| Check | Resolution |
|---|---|
| Device not activated | The device ships powered off. Press and hold the service button (side pinhole) for 5 seconds, or activate via NFC using CB Admin. |
| Wall outlet has power | Try a different outlet or test with another device |
| Plug fully inserted | Ensure the prongs are fully seated in the outlet |
| Outlet is switched | Some outlets have a wall switch — verify it is on |
| Button not held long enough | Hold the service button for the full 5 seconds. LED1 blinks WHITE once to confirm power-on. |
| LED not visible | LEDs are off by default (dormant mode). Short-press the button to activate LEDs for 5 minutes. |
NFC Configuration Fails¶
| Check | Resolution |
|---|---|
| Phone NFC is enabled | Enable NFC in your phone's settings |
| Phone position | Hold the phone within 2 cm of the front face, centered on the upper half (Connectivity Module) |
| CB Admin version | Update to the latest version of CB Admin from the app store |
| Phone compatibility | Check the Supported Phones list |
Gateway Cannot Connect to WiFi (232012, 232013)¶
| Check | Resolution |
|---|---|
| Correct SSID and password | Re-enter via Web UI or NFC |
| WiFi in range | Move the gateway closer to the WiFi access point |
| 5 GHz compatibility | If using 5 GHz only, verify your AP supports 5 GHz |
| Country code | Ensure the country code matches your region (affects available channels) |
Gateway Cannot Connect to MQTT Broker (232012, 232013)¶
| Check | Resolution |
|---|---|
| Broker URI and port correct | Verify in Web UI → Configuration → MQTT |
| TLS certificates valid | Re-upload CA certificate; check expiration date |
| Credentials correct | Re-enter username and password |
| Internet access | Check Web UI → Device → "Check internet connection" button |
| Firewall rules | Ensure port 8883 (or your broker port) is open on your network |
Getting Help¶
If the issue persists, contact CargoBeacon support:
- Email: support@cargobeacon.com
- Web: cargobeacon.com/contact
When contacting support, include:
- Device article number (e.g. 232012)
- Device serial number (printed on the label)
- LED color/pattern observed
- Firmware version (if accessible via Web UI → Device tab)