> 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/power-saving-features.md).

# Power saving features

## **Power saving mode**

To minimize energy consumption, the logger uses **PSM = 0** and **eDRX disabled**. After transmitting data to the server and, if applicable, receiving a configuration response, the logger finishes the communication session and does not remain active waiting for additional downlink data.

As a result, the server cannot initiate communication with the logger at any time. Data or configuration can be sent from the server only in response to a packet initiated by the logger.

* **PSM (Power Saving Mode)** is a cellular power-saving mechanism that allows an NB-IoT device to enter a very low-power state between communication sessions while remaining registered in the mobile network.
* **eDRX (extended Discontinuous Reception)** is another power-saving mechanism that allows the device to periodically wake up and listen for incoming data from the network without remaining continuously active.

## **Coverage Enhancement Level (ECL)**

The **Coverage Enhancement Level (ECL)** indicates the level of coverage enhancement required for communication with the NB-IoT network. Higher ECL values are generally associated with poorer radio conditions and require additional transmission repetitions, increasing energy consumption.

The logger determines the required transmission repetitions automatically based on network conditions. This behavior is not configurable by the user.

In practice:

* **ECL0** – good network conditions and the lowest transmission energy consumption
* **ECL1** – weaker network conditions and increased energy consumption
* **ECL2** – poor network conditions, requiring more repetitions and significantly higher energy consumption

Because network quality has a major impact on battery life, it is recommended to check the ECL value at the intended installation location. ECL and other cellular network parameters can be checked in the *Network status* section in the Efento mobile app.

## **Bluetooth power saving**

The Bluetooth Low Energy interface can be configured to switch off automatically after a defined period. The configured time is counted from the moment the logger is powered on or, if the setting is received remotely from the server, from the moment the new configuration is received.

Disabling Bluetooth when local access is not required can reduce power consumption. For configuration details, see [**Bluetooth turn-off time**](https://docs.efento.io/nb-iot-loggers/configuration/device-settings/bluetooth-turn-off-time.md).

## **Optimizing measurement and transmission intervals**

The logger does not need to transmit data after every measurement. The [**Measurement interval**](https://docs.efento.io/nb-iot-loggers/configuration/device-settings/measurement-interval.md) determines how often measurements are taken, while the [**Transmission interval**](https://docs.efento.io/nb-iot-loggers/configuration/device-settings/transmission-interval.md) determines how often the collected data is sent to the server.

Using a transmission interval longer than the measurement interval can significantly reduce the number of cellular communication sessions and therefore reduce energy consumption.

For applications where immediate transmission is required only under specific conditions, [**Rules** ](https://docs.efento.io/nb-iot-loggers/configuration/device-settings/rules.md#conditions)can be used to trigger a transmission when a defined event occurs, for example when a measurement exceeds a configured threshold. This makes it possible to use longer regular transmission intervals while still sending important data immediately when required.


---

# 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/power-saving-features.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.
