> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/alarms/low-battery-alarm.md).
# Low Battery Alarm
The **Low Battery** alarm notifies users when a sensor’s battery level drops below a defined threshold. This alarm helps ensure uninterrupted sensor operation by providing early warning before a device becomes unavailable due to battery depletion.
When the Battery Low alarm is triggered, users can take timely action to replace or recharge the battery, preventing data gaps and loss of monitoring continuity. The alarm status is recorded and visible in the Alarms and Alarm History sections.
Please note that this is a built-in rule that controls sensor battery levels. Battery level thresholds depend on the sensor type. This rule cannot be deleted or copied.
The Battery Low alarm can be used to:
* Monitor the battery status of wireless sensors
* Prevent unexpected sensor downtime
* Plan maintenance and battery replacement in advance
* Maintain reliable and continuous data collection
This alarm is especially useful in installations with a large number of sensors or sensors located in hard-to-access areas, ensuring proactive device maintenance and system reliability.
---
# 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://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/alarms/low-battery-alarm.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.
