> 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/s2gw-installation-manual/s2gw-operation/sensors-initialisation.md).

# Sensors initialisation

After receiving the configuration:

1. If it is the same as the current configuration, S2GW does not perform the sensor initialisation and continues to operate.
2. If it is different from the current configuration, S2GW performs the initialisation for the sensors for which the configuration did change.

In case any sensor fails initialisation, S2GW sends information about fail immediately after the check using [S2GW No answer from a node](/s2gw-installation-manual/troubleshooting/xml_examples/s2gw-no-answer-from-a-node.md) or [S2GW No sensor detected](/s2gw-installation-manual/troubleshooting/xml_examples/s2gw-no-sensor-detected.md)messages.

It presents the reason of failure which can be node not answering on radio ("No communication with node") or node answering but having no sensor with a given index ("No sensor detected (node sends 0xAA)").

If the node/sensor will come online, then it will be discovered by the S2GW after next configuration update. This will happen no more than 15 minutes later assuming default Refresh Config period of 15 minutes, is set in the GW config file.

The initialisation of a single sensor is shown in the flowchart below.

<figure><img src="https://623241058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3O2JmRv8Cq2LTrIfpgxe%2Fuploads%2FnLypDbIzl4BHoxTD0lfC%2Fimage.png?alt=media&amp;token=ffa9698b-8ace-47c2-865e-0232f6de0e79" alt=""><figcaption></figcaption></figure>

It can be found in S2GW log


---

# 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/s2gw-installation-manual/s2gw-operation/sensors-initialisation.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.