> 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/configuration/configuration-with-a-custom-server.md).

# Configuration with a custom server

Efento NB-IoT loggers send data using the CoAP protocol ([RFC 7252](https://tools.ietf.org/html/rfc7252) Constrained Application Protocol). CoAP is a lightweight, UDP-based communication protocol commonly used in IoT applications. The data is encoded in **Protocol Buffers (Protobuf)** format, which provides low communication overhead and is well suited for resource-constrained IoT devices.

Efento loggers can be integrated with any server application. The integration can provide access to the full range of logger functionality, including receiving measurement data and remotely configuring device settings.

There are two ways to integrate Efento loggers with your cloud platform:

1. [Efento CoAP Loader](https://docs.efento.io/nb-iot-loggers/integrations/efento-coap-loader.md) - Efento CoAP Loader is a CoAP server that receives data from Efento loggers, converts the messages to JSON, and forwards them to the customer’s application using REST. Its API can also be used to remotely change logger settings. This is the quickest way to integrate Efento loggers with an existing platform.
2. Direct integration - if your platform supports the CoAP protocol, Efento loggers can send data directly to it. The application needs to deserialize the payload received from the devices. New configuration can also be sent to the loggers using Protobuf messages. For implementation details, refer to our [demo code](https://github.com/efento/NB-IoT-sensors-integration) and [messages payload documentation](https://github.com/efento/Proto-files).

If you have any questions about the integration, please contact the [Efento Support team](http://help.efento.io/).

## **Logger configuration**

Initial setup of Efento NB-IoT loggers is performed locally via Bluetooth Low Energy (BLE) using the Efento mobile application, available for download on [Google Play](https://play.google.com/store/apps/details?id=pl.efento.cloud) and the [App Store](https://apps.apple.com/pl/app/efento/id6479740909). Once initial connectivity is established, subsequent configuration changes can be managed either locally via the app or remotely through server commands.

{% hint style="warning" %}
Before beginning configuration, ensure the following requirements are met:

* Functional destination server: The endpoint server must be active, reachable, and configured to return standard response codes as specified in the Efento integration documentation.
* Powered device with active SIM: The logger must be powered on with an inserted, activated SIM card provisioned for NB-IoT service.
  {% endhint %}

{% stepper %}
{% step %}

### **Connect to the logger**

1. Launch the Efento mobile application on your smartphone or tablet.
2. Select **Nearby devices** to view all detected Efento devices within Bluetooth range.
3. Select the required logger to establish a connection.
4. Tap the gear icon (Settings) in the upper-right corner to open the device configuration menu.
   {% endstep %}

{% step %}

### **Verify network registration**

1. In the device settings, under **Diagnostics**, select **Network status**.
2. Verify the **Registration** **status** field:
   * REGISTERED or REGISTERED ROAMING: The logger has successfully attached to the cellular carrier. Proceed to Step 3.
   * Other status: If registration fails, verify your cellular credentials. Certain network providers require manual entry of the [**APN**](https://docs.efento.io/nb-iot-loggers/configuration/device-settings/apn.md) (Access Point Name) and [**PLMN**](https://docs.efento.io/nb-iot-loggers/configuration/device-settings/plmn.md) (Public Land Mobile Network) values supplied with your SIM card. For persistent connection failures, consult the [**Network Status**](https://docs.efento.io/nb-iot-loggers/operation/logger-status.md#network-status) and [**Troubleshooting**](https://docs.efento.io/nb-iot-loggers/troubleshooting.md) chapters of this manual.
     {% endstep %}

{% step %}

### **Configure server and communication parameters**

1. In the device settings, under **Cellular**, select **Server settings**.
2. Open **Server settings** to configure the mandatory destination parameters:
   * **Server Address** and **Port**: Specify the target server IP address or domain name along with the active listening port.
   * **Authentication**: Select the authentication method and enter the required credentials.
3. Configure optional network parameters if required by your deployment:
   * **DNS** **server** *(Optional)*: Define the DNS server addresses. This is required only if connecting via a domain hostname instead of a static IP address.
   * **CoAP endpoints** *(Optional)*: Specify custom URI paths for data transmission, time synchronization, remote configuration, and device status..
4. Save the configuration to write the parameters to the device.
   {% endstep %}

{% step %}

### **Verify server communication**

1. Trigger a manual transmission test (settigns menu → **Trigger transmission**).
2. Return to **Diagnostics** → **Network** **status** and inspect the **Server** c**ommunication** **status** field:
   * **OK**: The logger connected to the remote server, uploaded data, and received a valid acknowledgment.
   * **Any other status:** Indicates a delivery failure (e.g., DNS resolution failure, network timeout, or invalid server response code). Refer to the [**Logger Status**](https://docs.efento.io/nb-iot-loggers/operation/logger-status.md#network-status) chapter for error code definitions and corrective actions.
     {% endstep %}
     {% endstepper %}


---

# 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/configuration/configuration-with-a-custom-server.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.
