> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/general-help/stations/station-troubleshooting.md).

# Station troubleshooting

If your station shows as offline, has stopped sending data or isn't earning, start here. These checks work for any station and only need the dashboard. For hardware checks (lights, firmware, network, power), go to the page for your device afterwards:

* [HYFIX troubleshooting](https://docs.wingbits.com/hyfix/hyfix-troubleshooting.md)
* [BYOD troubleshooting](https://docs.wingbits.com/byod/grandfathered-byod-diy-info/byod-troubleshooting.md)

### How "Online" works

Your station sends a heartbeat when it starts up and then every 10 minutes. It shows "Online" (green) when a heartbeat carries aircraft data from a GPS verified position inside the hex you claimed. All three have to be true.

The status only changes when a heartbeat arrives. After a restart, green usually shows on the second or third heartbeat, so allow about 20 minutes before deciding a fix didn't work.

### 1. Check the Statistics tab

Open your station from the [My Stations](https://wingbits.com/dashboard/stations) page and go to the "Statistics" tab.

{% hint style="warning" %}
Check the "Last update" line at the top first. If it is hours old, your station has stopped reporting and the tiles show how it was before it went quiet. Skip to the hardware page for your device.
{% endhint %}

If any tile is red, start there.

| Tile                                  | Healthy         | If not                                                                                 |
| ------------------------------------- | --------------- | -------------------------------------------------------------------------------------- |
| "Wingbits Ingestion"                  | Yes             | Your station can't reach Wingbits. Usually a network problem.                          |
| "Data Input Connected"                | Yes             | Your receiver isn't feeding the station.                                               |
| "Input Messages/s"                    | Well above zero | Zero means it isn't hearing aircraft. Check the antenna, not the network.              |
| "Location (1h avg.)"                  | In location     | Your station is outside its claimed hex and won't earn. Common after moving a station. |
| "GPS Satellites (1h avg.)"            | 20 or more      | The GPS antenna needs a clearer view of the sky.                                       |
| "System Clock Offset"                 | Milliseconds    | An offset of minutes or hours points to a problem.                                     |
| "Client Uptime"                       | Going up        | If it keeps resetting and you aren't restarting it, contact us.                        |
| "Input Dropped/s", "Output Dropped/s" | 0.00%           | Data is being lost on the way in or out.                                               |

### 2. Check the Heartbeats tab

The "Heartbeats" tab has one row per heartbeat, newest at the top, for the last 4 days.

* Red rows ("Connectivity Issue") are missing heartbeats. The station lost internet or power during that time.
* Yellow rows ("Other Anomaly") mean something in that heartbeat looks off.
* A ↻ symbol by the time means the station restarted there. Handy for checking that a power cycle worked.

What the common patterns mean:

* "Input Sources" at 0, or "Input Messages" not changing: the antenna or receiver isn't feeding data.
* "Ingestion" at No, or "Output Dropped" going up: the station has data but can't reach Wingbits. Check your network.
* Low "GPS Sats" or a large "Dist to Hex": a GPS or placement problem, not a data problem.
* "Buffered" at 500: data is backing up because it can't be sent.

### Heartbeats arrive but the station never goes Online

If heartbeats are coming in but it still isn't green after 20 minutes, one of the three things above is missing. The "Statistics" tab will show which:

* "Input Messages/s" at zero: the station isn't hearing aircraft. Check the antenna is connected at both ends and has a clear view of the sky.
* "Location (1h avg.)" not "In location": the station is outside its claimed hex. If you moved it, [change its location](https://docs.wingbits.com/general-help/stations/change-location.md). If you didn't, contact us.
* "GPS Satellites" at zero: without a GPS position the data won't count. Check the GPS antenna.

### Still stuck?

Contact support with the chat icon at the bottom right of any page, and include:

* Your station ID and which hardware you have
* When it last reported, and anything that changed around then
* Which "Statistics" tiles are red
* What you have already tried

{% hint style="danger" %}
We will never ask for your password, wallet seed phrase or private key. Don't share them with anyone who asks.
{% endhint %}

If we confirm a hardware fault, see [Station Replacement](https://docs.wingbits.com/general-help/stations/station-replacement.md).


---

# 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://docs.wingbits.com/general-help/stations/station-troubleshooting.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.
