> 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/special-settings-by-sensor-type/water-leak-sensor.md).

# Water leak sensor

Water leak detection is based on monitoring a voltage drop. When the external probe (water rope) is completely dry, the measured voltage remains within the defined minimum and maximum thresholds. When the rope becomes wet, the voltage decreases. If the measured value falls below the minimum threshold, the device switches its state to **ALARM**. Efento water leak sensors are pre-calibrated at the factory, so initial calibration is not required. If the sensor does not react sensitively enough when the probe is flooded, you may increase the minimum threshold. If the device triggers an alarm despite a dry probe, first check the probe for damage, then consider increasing the maximum threshold.

The acceptable voltage range, during which the sensor reports **OK**, is defined as a percentage of the maximum measured voltage using two calibration parameters: **Minimum threshold**\
(defines the lowest voltage considered normal (no alarm). Default: 75%) and **Maximum threshold**\
(defines the highest voltage considered normal (no alarm). Default: 100%).

## Calibration parameters

| Logic Type        | Defines whether a leak is detected when the measurement (voltage percentage) is inside or outside the defined threshold range. | <ul><li>Normal logic (NO leak if Minimum Threshold ≤ measurement ≤ Maximum Threshold).</li><li>Reverse logic (LEAK detected if Minimum Threshold ≤ measurement ≤ Maximum Threshold).</li></ul> |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Minimum Threshold | The lower boundary (in percentage of supply voltage) for the condition check.                                                  | Range: 0 to 100 % (must not be greater than Maximum Threshold).                                                                                                                                |
| Maximum Threshold | The upper boundary (in percentage of supply voltage) for the condition check.                                                  | Range: 0 to 100 % (must not be less than Minimum Threshold).                                                                                                                                   |


---

# 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/special-settings-by-sensor-type/water-leak-sensor.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.
