> 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/efento-ble-loggers/installation/powering-on-the-loggers.md).

# Powering on the loggers

## IP30 enclosure

To power on an Efento BLE logger in an IP30 enclosure, simply remove the battery-isolating foil that prevents the battery from making contact with the holder. The foil protrudes from the back of the device, so there is no need to open the enclosure.

<figure><img src="https://2281799165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMmZlbWwFvjXyDA4JhEUP%2Fuploads%2FXRtvFz1qL3rA1oAZbccs%2F3_1.png?alt=media&amp;token=8509e4b0-4366-4e4d-9d2a-f654e7794bef" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
If you ordered a logger with a calibration certificate, the battery-isolating foil was removed by the laboratory during the calibration process. This means the device is already powered on and operating.
{% endhint %}

## IP67 enclosure

IP67 logger provide waterproof and dustproof protection. Because the enclosure is fully sealed, extra care is required when opening and closing the device to maintain its environmental rating.

{% stepper %}
{% step %}

### Open the enclosure

Using a cruciform screwdriver (PZ1 / PH1), remove all screws from the enclosure.

<figure><img src="https://2281799165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMmZlbWwFvjXyDA4JhEUP%2Fuploads%2F7Ctp1eiNOGFKU75S6dTK%2F4_1.png?alt=media&amp;token=6f377bde-ddc6-434f-a922-8c0ddb91ba1f" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Remove the battery-isolating foil

Take out the battery-isolating foil that prevents the battery from making contact with the holder.

<figure><img src="https://2281799165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMmZlbWwFvjXyDA4JhEUP%2Fuploads%2FXRtvFz1qL3rA1oAZbccs%2F3_1.png?alt=media&amp;token=8509e4b0-4366-4e4d-9d2a-f654e7794bef" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Close the enclosure

Align the cover so the gasket sits evenly. Close the enclosure and reinstall all screws.

{% hint style="danger" %}
**Ensure every screw is tightened securely** -loose screws may allow water to enter the enclosure and damage the internal electronics.
{% endhint %}

<figure><img src="https://2281799165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMmZlbWwFvjXyDA4JhEUP%2Fuploads%2FYowougPtUJAf2idZHECM%2F4_4.png?alt=media&amp;token=c6a39c91-c3b4-4012-bd75-35ad11c9fac0" alt="" width="375"><figcaption></figcaption></figure>
{% 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/efento-ble-loggers/installation/powering-on-the-loggers.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.
