> 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/using-loggers/standalone-mode/batch-actions.md).

# Batch actions

The Efento mobile application allows performing certain actions on multiple sensors simultaneously. Three batch actions are available:

1. **Set device time / synchronize time on multiple devices** – Synchronize the time on the selected loggers so they measure and record data simultaneously. This is useful, for example, in temperature mapping, as all loggers’ values will be aligned in the reports.
2. **Generate a report from multiple sensors** – The app downloads data from the selected sensors one by one and generates a single report containing data from all devices. The report can be configured and shared in the same way as a regular [report from a single logger](/efento-ble-loggers/using-loggers/standalone-mode.md#exporting-the-data).
3. **Change measurement period** – Set a new measurement interval for the selected device(s). Optionally, you can clear the devices’ memory and synchronize their time by selecting the corresponding checkboxes.

To enter **batch action mode**, go to the list of nearby devices and:

{% stepper %}
{% step %}

#### Select the first device

Tap and hold the first sensor you want to include. It will be **highlighted in blue**.
{% endstep %}

{% step %}

#### Select other devices

Tap the other devices you wish to add.

<figure><img src="https://2281799165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMmZlbWwFvjXyDA4JhEUP%2Fuploads%2FRzUlzRpi6e4CW5kq7PM1%2Fimage.png?alt=media&amp;token=94dbc6cc-f65e-415c-af76-ca79cbfa0d3f" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Select the batch action

Tap the three dots in the upper-left corner and choose from the available batch actions.

<figure><img src="https://2281799165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMmZlbWwFvjXyDA4JhEUP%2Fuploads%2FiSYIoaIQY4a2OQCx5fKc%2Fimage.png?alt=media&amp;token=27f269a8-67c5-4f3c-b0f0-24d18b2cac9e" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Enter PIN codes

Enter the PIN code for each device. The PIN codes are printed on the devices’ enclosures. Once entered, the app will remember the code and will not ask for it again on the same mobile device.
{% 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/using-loggers/standalone-mode/batch-actions.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.
