> 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/hardware-debugging.md).

# Hardware Debugging

This section will include steps to debug any common issues that may arise at some point after your hardware is set up. Before you reach out to Movatic for any bug issues, please ensure you have tried the following steps below:

### For Bluetooth Low Energy Issue

1. Check that the unit has power.
2. Check that the unit is broadcasting. This can be done via the Maintenance app or a separate BLE scanning app.
3. Check if other units are working. For isolated incidents, contact your hardware manufacturer. Most broad-based incidents are related to software, while most isolated events are related to hardware.

### For Cellular Connection Issue

1. Check that the unit has power.
2. Check the sim card configuration and verify that it's configured correctly via the sim card provider dashboard.
3. Check that the device is properly pointed to Movatic's server.
4. From the Movatic admin site, verify that the information is entered correctly (i.e. IMEI, Vendor ID)
5. Contact Movatic at <support@movatic.co> for additional support once the above steps have been performed.


---

# 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/hardware-debugging.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.