> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/win-gateway-installation-manual/node-information/battery.md).

# Battery

The battery field presents the summary voltage of the batteries (or external power supply).

<figure><img src="https://2429681196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0vLm0km8knyJJgcLOzxB%2Fuploads%2FwPK8jPJoRsKlAgZtFeEo%2Fimage.png?alt=media&amp;token=f9099d2a-44e1-4bd8-85e7-16d250e66343" alt=""><figcaption></figcaption></figure>

The battery is only measured every 8th logging interval, so when replacing batteries, it may take some time before this value is updated. This field is also shown as a technical measurement point in Boomerang.

<mark style="background-color:red;">**The node works normally for battery voltage down to 2.70V, at which point it turns off its radio and just continues to measure and buffer values down to 2.50V.**</mark>&#x20;

This means that if no one has noticed that the battery voltage is getting low, the node will stop reporting values to Boomerang but still buffer them internally. If the batteries are replaced before the buffer is full, then all the values will be sent to Boomerang without any gaps in the readings.


---

# 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.boomerang3.com/win-gateway-installation-manual/node-information/battery.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.