> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/your-data-flow/device-connector/coap/efento.md).

# Efento

Efento devices transmit data using the [Protobuf](https://protobuf.dev/) format. To simplify integration, Akenza provides native handling for Efento within the **CoAP Device Connector**. This built-in logic automatically processes uplink authentication (uplink secret) and device identifiers directly from the encoded payload.

## Set up an Efento device to send data to akenza

### Create a Data Flow

Before configuring your hardware, establish the cloud infrastructure:

* Log in to Akenza.
* Create a new **Data Flow**.
* Select the **CoAP Device Connector** as the entry point.
* Note the **Uplink Secret** generated by the connector; you will need this for the device configuration.

### Create a Device

* Create a new Device
* Select the previously created Data Flow.
* Use the Efento Device Identifier as Device ID, but remove the colons
  * Example: `28:2C:02:40:AB:CD` -> `282C0240ABCD`

### Configure the Efento Device

To configure the device, you must use the Efento mobile application.

1. **Enable Power User Mode:** Open the app menu and quickly tap the Efento Logo five times.
2. **Access Settings:** Navigate to the device configuration section.
3. **Endpoint Configuration:** Apply the following settings to ensure compatibility with the Akenza CoAP endpoint:
   * Set the Authentication to custom token, use the `uplinkSecret` from the CoAP device connector (Enable sending the token in the payload)
   * Endpoint configuration
     * Data: `efento/m`
     * Configuration `efento/c`
     * Device Info `efento/i`
     * Timestamp `efento/t`
   * Set the IP address to `coap.akenza.io:5683`

### Transport Security & Optimization

Data transmission over NB-IoT is inherently encrypted within the cellular network. However, once the data leaves the carrier network for the public internet, additional measures are required to maintain security without draining the device battery.

> The Challenge: Standard encryption (like DTLS) increases UDP frame size, which significantly raises power consumption and shortens the device's battery life.

**Recommended Architecture: Secure Tunnel**

To balance security and energy efficiency, Akenza recommends the following setup:

1. **Private APN:** Use a private APN configured by your network operator.
2. **VPN Tunnel:** Establish a secure VPN tunnel between the operator's APN and akenza.
3. **Result:** Data remains in its lightweight UDP format for the device, while the "hop" over the public internet is protected from eavesdropping by the tunnel.

{% hint style="info" %}
Contact akenza for more information regarding transport security.
{% endhint %}

### Links

* <https://getefento.com/library/iot-protocols-coap-and-protocol-buffer-protbuf/>
* <https://docs.efento.io/nb-iot-loggers/security>


---

# 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.akenza.io/device-management/your-data-flow/device-connector/coap/efento.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.