> For the complete documentation index, see [llms.txt](https://enless.gitbook.io/centre-aide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enless.gitbook.io/centre-aide/guides-installation/capteurs/editor-23/utilisation/installation-du-capteur.md).
# Installation du capteur
TX CO2 T\&H AMB (ancienne génération) : installation du capteur
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
Le TX CO2 T\&H AMB (ancienne génération) propose une solutions de montage mural intégré à l'intérieur du capteur.
{% endcolumn %}
{% endcolumns %}
## Fixation Murale
Le boîtier dispose de quatre points de fixation internes, accessibles après ouverture du capot :
* Accès : Retirer la vis retenant le capot du capteur puis retirer le capot.
* Emplacements : Les trous se situent au quatre coins du boitier.
* Méthode : Utilisez des vis et chevilles adaptées à la nature de votre support (mur plein, cloison sèche, etc.).
{% hint style="info" %}
La visserie n'est pas fournie ; veillez à utiliser des vis et chevilles adaptées à la nature de votre support (placo, béton, bois) pour garantir la tenue du capteur.
{% endhint %}
Il est également possible de fixer le capteur avec de l'adhésif double-face.
---
# 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://enless.gitbook.io/centre-aide/guides-installation/capteurs/editor-23/utilisation/installation-du-capteur.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.
