> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/academy/einen-zahlerwechsel-konfigurieren.md).
# Configure a meter change
## **Configure meter replacement**
A **Meter may fail** or be replaced by a **new one** . If only the new meter reading were adopted, already recorded values could **be lost**, which would lead to **data gaps and calculation errors** lead.
To prevent this, Eliona offers the option to **configure an offset** — either **manually** or through an **automatic detection**.
## **Set an offset for a meter**
1. **Open the asset details** of the affected asset.
2. **Click on the attribute**, for which the offset is to be configured **\[A]**.
3. **Enable the offset function \[B].**
4. **Select one of the following methods:**
* **Enter value manually:** The offset value is permanently added to **all new measured values**.
* **Enable automatic calculation:** Eliona automatically detects when a meter replacement has occurred.
* If the new value drops by **more than 10 %**, an offset is automatically set.
* Instead of continuing to count with the new value, the previous value remains as **base** retained.
---
# 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.buildings.ability.abb/collection/english-v14/academy/einen-zahlerwechsel-konfigurieren.md?ask=&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.
