> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/fr/level-meter-manuel-de-lappareil/level-meter-manuel-dinformation-sur-la-gestion/level-meter-conseils-de-securite.md).

# Level Meter - Conseils de sécurité

## **Chargement de la batterie**

\
La batterie ne peut pas être rechargée : le dispositif comprend deux batteries lithium faisant partie d'un même ensemble de batterie.\
Manipuler incorrectement la batterie peut provoquer un incendie. Ne pas endommager ni couper le dispositif.

## **Utilisation du Level Meter**

\
Utilisez le dispositif uniquement si vous pouvez garantir qu'aucune blessure corporelle ou dommage matériel ne peut survenir en raison du type d'installation.

## **Recyclage du Level Meter**

\
En tant que fabricant, Virtue Intelligence GmbH est responsable de la collecte, du prétraitement et de l'élimination correcte du Level Meter.\
Le numéro d'enregistrement WEEE pour le Level Meter est le DE16378411. Processus de mise au rebut étape par étape :

1. Un agent vous contactera.
2. Les équipements électriques usagés seront emmenés à l'endroit convenu.
3. Le fabricant s'occupe du reste.


---

# 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.g-iot.io/fr/level-meter-manuel-de-lappareil/level-meter-manuel-dinformation-sur-la-gestion/level-meter-conseils-de-securite.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.