> For the complete documentation index, see [llms.txt](https://docs.ocutrap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ocutrap.com/troubleshooting/trap-offline-or-wont-connect.md).

# Trap Offline or Won't Connect

If your trap shows **offline**, will not connect, or does not respond to commands, the most common causes are **low battery**, **hibernation**, a **loose battery connection**, **weak cellular signal**, or the trap **still trying to connect**.

OcuTrap connects primarily through **4G LTE cellular service**. The trap does **not** need local Wi-Fi for normal operation. Poor cellular coverage can prevent the trap from connecting or receiving commands.

The **LED light** is the fastest way to see what the trap is doing. Work through the steps below in order.

## Quick Checklist

1. Make sure the battery is charged.
2. Unplug and reconnect the yellow battery connector.
3. Press the **power button once** to wake the trap.
4. Check the **LED color or blink pattern**.
5. Move the trap to an area with better cellular signal if needed.
6. Refresh the app or dashboard and check the trap's **Last Activity**.
7. If still offline, send Support the **LED pattern**, **Trap ID**, and a **screenshot of the error**.

## Step 1: Check the Battery

A low or disconnected battery is one of the most common reasons a trap appears offline.

1. **Disconnect and reconnect** the yellow battery connector.
2. Make sure the connector is **fully seated** — it should click into place without forcing.
3. If the battery may be low, charge it using the **charger that came with your trap**.
   * The charger light turns **red** while charging and **green** when charged.
4. A very low battery can cause the trap to shut down or fail to connect.

After reconnecting the battery, **press the power button once** and watch the LED.

For more on battery care and charging, see the [Battery FAQ](/faqs/battery.md).

## Step 2: Wake the Trap From Hibernation

If the trap has been **unarmed and idle**, it may have entered **hibernation** to save power. In hibernation:

* There may be **no LED**.
* The trap **cannot send notifications** or **receive commands** from the app.

To wake the trap:

1. Press the **power button once**.
2. Wait a few minutes for the trap to reconnect.

> **Note:** If the trap is **armed**, it may use an **offline or sleep mode** and check in with the cloud periodically instead of staying connected all the time. Allow time for the next check-in before assuming the trap is fully offline.

{% hint style="warning" %}
If the trap **immediately powers down again** after you press the power button, the battery may be too low. Charge or replace the battery before trying again.
{% endhint %}

For a deeper explanation of power states, see [Power Modes](/faqs/power-modes.md).

## Step 3: Read the LED Status

Use the table below to interpret what the trap is doing. If the LED never turns on after a charged battery is connected and the power button is pressed, contact [OcuTrap Support](/support/support.md).

| LED Pattern           | What It Usually Means                                | What To Do                                |
| --------------------- | ---------------------------------------------------- | ----------------------------------------- |
| Breathing cyan        | Connected and online                                 | Refresh the app and try the command again |
| Fast blinking cyan    | Connecting to the cloud                              | Wait a few minutes                        |
| Blinking green        | Looking for cellular/internet connection             | Move to better cellular coverage          |
| Blinking magenta      | Firmware update or safe mode activity                | Leave powered on and wait                 |
| Rapid red blinks      | System error                                         | Count the blinks and contact Support      |
| Solid red during boot | Battery too low at startup                           | Charge or replace the battery             |
| No light              | Powered off, hibernating, no battery, or failed boot | Reconnect battery and press power button  |

For a full list of LED patterns — including door and arm/unarm indicators — see the [LED Guide](/getting-started/led-guide.md).

## Step 4: Check Cellular Coverage

OcuTrap depends on **cellular signal** to send and receive commands. Metal buildings, garages, basements, dense structures, and remote areas can weaken or block signal.

If the LED is **blinking green for a long time**, the trap may not have enough cellular coverage where it is placed.

1. Move the trap **outdoors** or to a more open area.
2. Give it a few minutes to search for signal and reconnect.
3. The trap may reconnect automatically once signal improves.

## Step 5: Check the App or Dashboard

1. Confirm the trap **appears in your account**.
2. Open the trap **settings** or **control panel**.
3. Check **Last Activity** or last heard time.
4. Tap **refresh** or **request latest data** if that option is available.
5. Confirm you are viewing the **correct Trap ID** (the serial number from the POD label, shown in the app after registration).

If the trap was recently added, make sure the **Trap ID** in the app matches the **serial number** on the label inside the POD. See [Adding a trap to your account](/getting-started/app/adding-a-trap-to-your-account.md).

## Step 6: Inspect Connections

1. Make sure the **yellow battery connector** is secure.
2. Make sure the **POD is closed and latched**.
3. If instructed by Support, check that the **antenna connections** are seated.
4. Do **not** force connectors or open internal components unless Support instructs you to.

## Step 7: When Commands Do Not Reach the Trap

If the trap is **offline**, **hibernating**, or **between check-ins**, commands from the app may fail or show an error message.

Recommended actions:

1. **Wake the trap** with the power button.
2. Wait for the LED to become **breathing cyan**.
3. **Retry the command**.
4. If the trap is **armed and offline**, allow time for the **next check-in** before trying again.

For more on command failures specifically, see [Trap Not Sending Commands](/troubleshooting/trap-not-sending-commands.md).

## What To Send OcuTrap Support

If the issue continues, email <support@ocutrap.com> with as much of the following as you can:

* **Trap ID**
* **Screenshot** of the app error message
* **LED color or pattern** (or note if there is **no LED at all**)
* Whether the battery was **recently charged**
* **Approximate location type** — for example: indoors, garage, field, metal building, wooded area
* **Last Activity** time shown in the app
* Any recent **weather**, **battery change**, or **impact/transport**

## Safety Note

Before handling the trap, keep hands and fingers **clear of the door path**. The door can close quickly when the trap reconnects or receives a command.

## Still Offline?

If the trap remains offline after checking the battery, waking the device, and confirming cellular coverage, contact [OcuTrap Support](/support/support.md) with the details above so we can review the device status and help determine the next step.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ocutrap.com/troubleshooting/trap-offline-or-wont-connect.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.