> For the complete documentation index, see [llms.txt](https://docs.efento.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.efento.io/nb-iot-loggers/troubleshooting.md).

# Troubleshooting

If measurements from the logger do not reach the server, you can identify and resolve the issue using several diagnostic tools provided by the device.

## **Diagnostic options**

### **LED status**

For a quick on-site diagnostic check without opening the mobile application, the logger uses built-in LED indicators. The LED blink sequences and colours signal current device activity, network attachment status, and hardware states. A detailed breakdown of all LED patterns and what they mean can be found in the [**LED status Indicators**](#led-status-indicators-1) section below.

### **Server-side diagnostic data (device info)**

Whenever troubleshooting is triggered or the device registers connectivity events, the logger compiles and transmits extended diagnostic parameters directly to the server. These payloads include network parameters (such as signal strength, cellular band, PLMN, and cell ID), modem status, and runtime error logs. For full details on the payload structure and available parameters, see the [**Device Info API Reference**](https://docs.efento.io/nb-iot-loggers/integrations/efento-coap-loader/api-reference/device-info.md).

### **Efento mobile application**

You can run the automated troubleshooting procedure in the Efento mobile application. The app connects to the logger via Bluetooth, verifies cellular network registration, tests communication with the server, and attempts to resolve detected connectivity issues automatically. During the process, the app compiles detailed diagnostic logs that you can export and forward directly to Efento Support for analysis.

## **Troubleshooting with mobile application**

To enter Troubleshooting mode, connect to the device and tap the gear icon. In the **Diagnostics** section, select **Troubleshooting**.

### **Before you start**

* Keep your phone screen on and the application open. Bluetooth must stay active throughout the process.
* Stay within 1–2 meters of the logger.
* Allow the procedure to run for up to 15 minutes.

### **Troubleshooting procedure**

During the procedure, the application shows the time remaining until the checks are finished and the progress of each step:

* **Initial fix attempt** – the logger attempts to restore communication by forcing data transmission and checking the cellular network
* **Modem restart** – if the first attempt is unsuccessful, the logger restarts the cellular modem to clear possible communication issues
* **Final fix attempt** – after the modem restart, the logger repeats the same recovery actions as in the initial attempt and continues trying to restore communication until the end of the 15-minute troubleshooting period.

In the Network section, you can check:

* **NB-IoT registration** – whether the logger is registered to the NB-IoT network (e.g. *Waiting for network*, *Registered*)
* **Server connection** – whether the logger is able to connect to the Server (e.g. *Waiting for server*)

You can stop the procedure at any time by tapping **Exit**.

<figure><img src="https://740246929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGPFUI36OraG706yJS7dJ%2Fuploads%2FgL4WYjALvuKKYV4GdJSn%2Ftroubleshooting_process.png?alt=media&amp;token=aa1de516-5065-49a8-b2c6-aafaf349018b" alt="" width="375"><figcaption></figcaption></figure>

### **Resolutions**

The troubleshooting procedure can end in one of two ways. If the logger successfully connects to the server, no further action is required. If the connection cannot be established, additional diagnostics based on the modem logs is required.

#### **Logger is online**

If the logger connects to the server, the procedure finishes early and the application shows "**Logger is online"**. The logger will then send data according to its configuration and no further action is needed.

#### **Further diagnosis is needed**

If the logger is still unable to connect to the server after all the steps, the application shows **"We checked your logger, further diagnosis is needed"**. In this case, further diagnositcs based on the modem logs is required. The application prepares diagnostic logs containing the full network trace and error codes. To send them to Efento Support team:

{% stepper %}
{% step %}
Tap **Send logs**. The application opens an email with the logs attached. The email also includes your phone model, operating system version and application version.
{% endstep %}

{% step %}
Add a brief description of the installation environment (e.g. location of the logger, building type, whether it is installed underground or in a metal cabinet). This helps the Efento Support Team find a solution faster.
{% endstep %}

{% step %}
Send the email.
{% endstep %}
{% endstepper %}

If you do not want to send the logs, tap **Exit without sending logs**.

## **Device operating states**

### **Power-on and startup**

The initialization phase that occurs immediately after inserting fresh batteries, connecting external power, or rebooting the device. During this state, the logger powers on its microcontroller, performs an automatic internal hardware self-test (verifying internal memory, system buses, and connected sensor probes), and starts acquiring time and registering to the cellular network. Once network registration is established, it attempts its first data transmission to the remote server. After this initial cycle completes, the device automatically transitions to the Normal Operation state.

### **Normal operation**

The standard, continuous operational mode of the logger. In this state, the device operates autonomously according to its configured schedule: taking periodic measurements from connected sensors, storing readings in non-volatile flash memory, and waking up the cellular modem at designated intervals to transmit accumulated measurement batches to the server. Between measurement and transmission cycles, the logger stays in an ultra-low-power sleep mode to maximize battery longevity, waking only for scheduled tasks or when an external button press / Bluetooth connection occurs.

### **Shutdown (Storage / Off mode)**

A deep-sleep, ultra-low-power standby state used for transport, long-term storage, or decommissioning. When shutdown is triggered (by pressing and holding the physical button for 6 seconds), the logger saves all pending measurements and current configuration to non-volatile memory, cleanly terminates any ongoing network session, and powers off the modem and connected sensors. In this state, regular logging and scheduled transmissions are paused, reducing current draw to near zero to preserve battery capacity until the device is explicitly turned back on.

### **Firmware update / bootloader mode**

A dedicated maintenance state used exclusively for updating the logger's internal system software (firmware over Bluetooth Low Energy). In this mode, regular measurement routines and cellular transmissions are suspended. The device executes a specialized bootloader program that verifies data integrity, receives new firmware image packages uploaded from the Efento mobile application, flashes them into internal memory, and reboots the logger once the update is successfully completed or safely aborted.

## **LED status indicators**

Efento loggers are equipped with two built-in LED indicators – <mark style="color:$success;">**green**</mark> and <mark style="color:red;">**red**</mark> – that provide visual information about the current device status, network connectivity, measurements, data transmission, and detected errors.

<figure><img src="https://740246929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGPFUI36OraG706yJS7dJ%2Fuploads%2FUu5yBU6lleKD1tgbym0y%2Fled_diodes.png?alt=media&amp;token=dab14b64-c440-424c-8294-9694f110863a" alt="" width="265"><figcaption></figcaption></figure>

The meaning of the LED pattern depends on the current operating state of the logger.

The startup indication automatically changes to the normal operating indication **5 minutes after the first transmission attempt** or **30 minutes after power-on**, whichever occurs first.

#### **Power-on and startup**

After the logger is powered on, the LEDs indicate the progress of the startup sequence, hardware self-test, and initial cellular connection.

| LED behavior                             | Status                        | Meaning                                                                                                             |
| ---------------------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Both LEDs solid on for 1–2 s             | Boot initialization           | The logger has powered on and is starting the internal system.                                                      |
| Both LEDs blink simultaneously every 1 s | Hardware self-test            | The logger is performing internal hardware diagnostics.                                                             |
| Green LED solid on for 3 s               | Self-test successful          | The hardware self-test completed successfully.                                                                      |
| Red LED solid on for 3 s                 | Self-test failed              | A hardware diagnostic check failed. Check the connected probes and power supply.                                    |
| Green and red LEDs blink alternately     | Network registration          | The logger is attempting to register to the cellular network and establish communication with the server.           |
| Green LED blinks every 4 s               | Initial connection successful | The first transmission to the server was successful.                                                                |
| Red LED blinks every 4 s                 | Initial connection failed     | The logger could not connect to the server or transmit data successfully. Check cellular coverage and APN settings. |

#### **Normal operation**

During normal operation, the LEDs indicate the current device status and selected events.

| LED behavior                 | Status / event    | Meaning                                                                                        |
| ---------------------------- | ----------------- | ---------------------------------------------------------------------------------------------- |
| Green LED periodic blink     | Normal operation  | The logger is operating normally and no active error is detected.                              |
| Red LED periodic blink       | Active error      | An error is active, for example a transmission failure, probe error, or low battery condition. |
| Green LED blinks twice       | Measurement       | The logger has performed a measurement cycle.                                                  |
| Green LED blinks three times | Data transmission | The logger is transmitting data to the server through the cellular network.                    |

#### **Shutdown**

When the logger is switched off, the LEDs indicate the progress of the shutdown procedure.

| LED behavior                                      | Meaning                                                                                                                   |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Green LED solid on for 1.5 s                      | The logger has recognized the shutdown command.                                                                           |
| Green LED blinks once, followed by two red blinks | Shutdown is in progress. The logger saves its configuration, performs the final transmission, and switches off the modem. |
| Red LED solid on for 1.5 s                        | The shutdown procedure has completed and the logger has entered a low-power state.                                        |

#### **Firmware update / bootloader mode**

During a firmware update, the LED indicators show the status of the bootloader and update process.

| LED behavior                 | Meaning                                                      |
| ---------------------------- | ------------------------------------------------------------ |
| Both LEDs off                | The bootloader is idle and waiting for instructions.         |
| Green LED blinks slowly      | The firmware is being uploaded to the logger.                |
| Green LED solid on for 1.5 s | Firmware update completed successfully.                      |
| Red LED solid on for 1.5 s   | Firmware update failed.                                      |
| Red LED blinks every 0.5 s   | Critical bootloader error – the firmware image is corrupted. |

## **Need more help?**

If you are still experiencing problems or have any questions, feel free to contact [**Efento Support Team**](http://help.efento.io/). Our team will be happy to help you find the cause of the issue and assist you with the next steps.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.efento.io/nb-iot-loggers/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
