> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/modes/batteries.md).
# Batteries
The **Batteries** hardware type is designed to help system administrators keep track of the batteries assigned to locks or other hardware. This tracking aids in understanding the lifespan of each battery.
{% hint style="info" %}
Currently, this hardware type is for administrative purposes only and does not impact rentals or the behavior of other hardware.
{% endhint %}
\
To view the **Batteries** list, click on "Hardware" on the left side of the dashboard. This will display a list of all your hardware, including batteries. To filter and view only the batteries, click on the "Batteries" filter.
In the upper right-hand corner, you can add a **new battery** by clicking the "+ Add" button. If you need to add batteries in bulk, click on "Import" from the three-dot menu next to the "Buy" button to upload a CSV file.
When adding a new battery to the system, you can assign a label for easy identification and select its hardware state, both of which can be updated at any time.
---
# 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://documentation.movatic.co/admin-site/modes/batteries.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.
