> 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/example-of-a-config-file.md).

# Example of a config file

The example of a strobe\_config.ini is shown below. In the example file the unit is set to work with the B3 system at <https://boomerang3.com>.

{% code overflow="wrap" %}

```sh
#Version 5.0 (strobe.sh located in /boot/ICU)
#Configuration for ICU-RaspFlash (aka. Blixtljus)

PING_URL="http://www.google.com"
PING_REATTEMPTS=5
PING_TIMEOUT=20

#How many seconds to wait for server to respond before aborting, and how many tries
SERVER_TIMEOUT=1
SERVER_TRIES=8

#How many retries of getting data from Service-URL before it reboots
MAXIMUM_RETRIES_BEFORE_REBOOT=100

#Update interval of the URL's (how many seconds between each URL-poll)
UPDATE=20

#INVERT_OUTPUTx=0 -> Default behaviour, a "1" from server turns on the relay
#INVERT_OUTPUTx=1 -> Inverts the output, so a "0" from server turns on the relay 
INVERT_CH1=0
INVERT_CH2=0
INVERT_CH3=0

#TURN_ON_CHx_IF_CONNECTION_FAILS=0 -> doesn't change relay output if connection to server goes down
#TURN_ON_CHx_IF_CONNECTION_FAILS=1 -> Turns on relay output if connection to server goes down. Note that this is OR'ed together with the normal relay status, so both can be used together (is also affected by INVERT_OUTPUT)
TURN_ON_CH1_IF_CONNECTION_FAILS=0
TURN_ON_CH2_IF_CONNECTION_FAILS=0
TURN_ON_CH3_IF_CONNECTION_FAILS=0

# B3:
#URL_MAC=0 -> Uses the SERVICE_URL to get status from server (older behaviour of Blixtljus)
#URL_MAC=1 -> Default behaviour, uses the URL_MAC_BASE + the MAC-adress to generate a unique URL only used by this unit, for example: http://www.boomerang3.com/bl/MAC/?id=B827EB29CA0D
URL_MAC=1
URL_MAC_BASE="https://boomerang3.com/api/relaybox"

# B2 or RQS (only reads temperature-alarms of two URL's)
#URL_DUAL=0 -> Uses the SERVICE_URL to get status from server (older behaviour of Blixtljus where a single URL controls both relays)
#URL_DUAL=1 -> Uses the two URL's SERVICE_URL_CH1 and SERVICE_URL_CH2 to control the two relay outputs individually, only temperature-alarms (ie. 1x) from URL will control the outputs (server's communication alarm status is ignored).
URL_DUAL=0
SERVICE_URL_CH1="http://81.91.10.237/strobelight.aspx?User=HUS_CH1"
SERVICE_URL_CH2="http://81.91.10.237/strobelight.aspx?User=HUS_CH2"

# B2 or RQS (old standard URL)
#Use either URL_MAC or URL_DUAL solution (above), OR, SERVICE_URL (don't try to use both)
#SERVICE_URL="http://81.91.10.237/strobelight.aspx?User=HUS_CH1"
SERVICE_URL="http://192.168.61.156/rasp.html"
#SERVICE_URL="http://www.rqs.se/bl/?id=ICU_MANKAN_INTERNAL_TEST_CGNS_GW"
```

{% endcode %}


---

# 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/example-of-a-config-file.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.