> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/cg1018-relay-box-installation-manual/installation/config-file/practical_examples/connection_failure_indicator.md).

# Connection failure indicator

The [Status LEDs](/cg1018-relay-box-installation-manual/overview/status-leds.md) indicate whether the unit has Internet connection which is checked by pinging the adress at PING\_URL, and if there is connection to the server. 

The ETH LED is blinking green if the ping is successful and the CON LED is steady green if we have a successful reply from the server.

If you want to get an indication on a relay, when the connection to the server fails, you can do so by using the following options: \
\
and/or \
**TURN\_ON\_CH2\_IF\_CONNECTION\_FAILS=1**

```sh
TURN_ON_CH1_IF_CONNECTION_FAILS=1 
```

**The relay can still be used as normal and be controlled by the server, as the connection fail status is OR’ed together with the status from the server.** 

Using this method, the relay can indicate both sensor alarm and connection fail on the same channel. 

This can be a useful feature as you will get a clear indication in case the CG1018 cannot contact the server. 

You may also invert the channels to setup an additional indication of failures.


---

# 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.boomerang3.com/cg1018-relay-box-installation-manual/installation/config-file/practical_examples/connection_failure_indicator.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.