> 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/operation/logger-status.md).

# Logger status

Efento loggers collect information about their current operating and network status. This information is useful for diagnostics and troubleshooting connectivity issues.

## **Network status**

The current cellular network status can be checked in the Efento mobile application. Connect to the logger, tap the gear icon, open the **Diagnostics** section, and select **Network status**.

The following information is available:

* **Supported technologies** - indicates the communication technologies supported by the device. The logger can send data directly over NB-IoT or, when supported, via BLE – Shared Cellular Modem, using the cellular modem of another device connected over Bluetooth.
* **Current technology** - indicates which communication technology is currently being used. For loggers that support only NB-IoT communication, this value will always be **NB-IoT**.
* **Registration status** - indicates the current cellular network registration status:
  * **REGISTERED** - the device is successfully registered with the network. This is the normal operating state.
  * **NOT\_REGISTERED\_SEARCHING** - the device is not registered and is currently searching for a network. This status may appear during startup before network registration is completed.
  * **NOT\_REGISTERED\_NOT\_SEARCHING** - the device is not registered and is not currently searching for a network. This may occur when no supported network is available.
  * **REGISTERED\_ROAMING** - the device is successfully registered with a network while roaming.
  * **REGISTRATION\_DENIED** - the network has rejected the device registration attempt.
  * **REGISTERED\_EMERGENCY\_ONLY** - the modem reports registration for emergency services only.
  * **UNKNOWN** - the modem is unable to determine or report the current registration status.
* **Registration reject cause** - if the device is not able to register to the network, the cause is displayed in this field. Reject causes are described in [3GPP TS 24.301 Annex A](https://www.etsi.org/deliver/etsi_ts/124300_124399/124301/17.11.00_60/ts_124301v171100p.pdf?utm_source=chatgpt.com) at 558 page. The value 0 means that no reject cause has been reported. When the device sends data via another device's cellular modem (BLE – Shared Cellular Modem), this field always shows 0.<br>

  The following reject causes are among those most commonly encountered:

  * **11 – PLMN not allowed** - the SIM/device is not allowed to operate in the selected mobile network. This may be caused by SIM subscription restrictions, incorrect operator selection, or the network blocking access. Check the configured PLMN, SIM subscription, and whether the SIM is authorized to use the selected network.
  * **13 – Roaming not allowed in this tracking area** - the SIM supports roaming in the network, but roaming is not permitted in the current tracking area. Check the SIM roaming settings and operator coverage or contact the SIM/network provider.
  * **19 – ESM failure** - an error occurred during the establishment of the packet data connection. This may be related to the APN or other data-session settings. Check the configured APN and confirm the correct settings with the mobile operator.

  If the problem persists, contact the SIM card or mobile network provider and provide them with the displayed reject cause code.
* **Server communication status** - current status of communication with the server. Possible statuses:
  * **OK** - The last communication with the server was successful. No action needed.
  * **Unknown (no communication yet)** - The logger hasn't communicated with the server yet, which is normal after power-up. If it doesn't change, check the network registration status.
  * **No data to send** - There was no new data to send, and the last communication was successful. No action needed.
  * **Payload building error** - An internal error occurred while preparing the data. Restart the logger. If the problem persists, check the firmware version and update the logger if a newer version is available. If the error still occurs after the update, contact Efento Support.
  * **CoAP encoding error** - An internal error occurred while encoding the message. Restart the logger, and if it happens again, contact Efento support.
  * **Socket error** - The modem couldn't open or use the network connection. Check the signal strength, the APN settings and whether the SIM card is active.
  * **Unexpected error** - An unexpected error occurred during communication. Trigger the transmission again, and if it continues, contact Efento support.
  * **Not registered on the network** - The logger isn't connected to the cellular network. Check the network coverage, the SIM card and the network settings.
  * **No SIM card** - No SIM card was detected. Make sure the SIM card is inserted correctly and isn't damaged.
  * **Server response timeout** - The server didn't respond in time. Check the signal strength, the server address and port, and whether the server is running.
  * **Server bad request** - The server rejected the data as invalid. Check the server configuration and the endpoint.
  * **Server unauthorized** - The server rejected the data due to missing authorization. Check that the logger is assigned to the correct account and that the token is correct.
  * **Server error** - The server returned an error. Check the server's status or contact its administrator.
  * **DNS error** - The server address couldn't be resolved. Check the server URL or use the IP address instead.
  * **IMEI reading error** - The modem's IMEI couldn't be read. The logger will retry automatically, and if the error continues, contact Efento support.
* **IMEI** - IMEI number of the cellular module
* **ICCID** - ICCID of the SIM card in the device
* **IP address** - current IP address of the device
* **ECL** - ECL level: Indicates cellular signal quality and can take one of three values: 0 - good, 1 - moderate, 2 - poor. The lower the value, the better the connection. ECL 1 or 2 may significantly reduce battery life.
* **Cell ID** - ID of the cell in to which the device is connected
* **Server communication timestamp** - timestamp of the last successful communication. All the information on this card is refreshed during the communication / self check.
* **Last status check timestamp** - timestamp of the last self check. Self checks are performed on the startup or may be performed on server’s demand. All the information on this card is refreshed during the communication / self check.
* **Successful registration timestamp** – timestamp of the last successful registration to the cellular network. All the information on this card is refreshed during the communication / self check.

## **Battery status**

Efento loggers will notify you about a low battery level both in the server site and the Efento mobile application. Once the “low battery” status appears, the battery should be replaced as soon as reasonably possible. The remaining operating time may vary significantly depending on the measurement type, transmission frequency, network conditions, and overall power consumption of the device.


---

# 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/operation/logger-status.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.
