> 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/locks/supported-locks/omni-ring-lock/omni-ring-lock-debugging.md).

# OMNI Ring Lock Debugging

We've put together a list of simple steps to go through when it comes to debugging what might be going on with your OMNI Ring Lock.

1. Is the OMNI Ring Lock showing as connected on the Movatic dashboard? If yes, try do an unlock/lock. If not, go to the next step.
2. Is the OMNI Ring Lock showing as connected on your SIM card dashboard? This might be Hologram, Twilio, etc. (for more information about SIM Cards [click here](/admin-site/modes/sim-cards.md)). 
   1. If yes, go to step 3.
   2. If no, hit reset on your SIM card dashboard. 
   3. Move to step 3 if this doesn't resolve it.
3. Did you add it to the Admin site with the IMEI?
   1. Please verify all information is entered correctly.
4. On the [OMNI BLE app](https://documentation.movatic.co/general-setup/hardware-setup/hardware-acton-setup), double-check that the port and IP are set as follows:
   1. IP: tcp.movatic.co
   2. Port: 8000
      1. If these are set, take a screenshot to send to us later. 
      2. If it is not set, update it. We can only provide support for ones that have been connected to our server and are showing the IP/Port correctly.
5. If you run through these steps and are still having issues, please reach out to <support@movatic.co>.


---

# 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/locks/supported-locks/omni-ring-lock/omni-ring-lock-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.