> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/alarms/base-station-offline-alarm.md).

# Base Station Offline Alarm

The **Base Station Offline** alarm alerts users when a base station stops communicating with Aranet Cloud for a defined period of time. This alarm helps quickly identify connectivity issues that may affect data collection from associated sensors.

When the alarm is triggered, sensor data transmission is interrupted until the base station reconnects. Early notification allows users to investigate potential causes such as power loss, network connectivity problems, or hardware issues.

<div data-with-frame="true"><figure><img src="https://2831658296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKwQxnS51pLI9fOl4xXp%2Fuploads%2FtxylcnaeK3qox7BLE9hK%2Fimage.png?alt=media&amp;token=5477aa0b-e4bd-4c0e-a793-4ed30f99af1f" alt=""><figcaption></figcaption></figure></div>

Please note that this rule cannot be deleted, but you can change Warning and Critical thresholds anytime.

The Base Station Offline alarm can be used to:

* Detect loss of communication between a base station and the cloud
* Minimize data gaps caused by connectivity interruptions
* Identify infrastructure or network-related issues
* Ensure reliable operation of the sensor network

This alarm is critical for maintaining continuous monitoring, especially in environments where real-time data availability is essential.


---

# 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://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/alarms/base-station-offline-alarm.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.