> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cloud-services/onelink/cloud-assisted-controller-addressing.md).

# Cloud-assisted controller addressing

Assign a OneLink controller an IP address through its local network.

Cloud Assisted Controller Addressing assists assigning a controller's IP address on a LAN.

## Requirements

* The controller must be able to connect to the internet via its local network connection.
* The controller must have 9.30 firmware with Application **9.30.360+** installed.
* The Command Centre server must be connected to the cloud.

## In Command Centre

1. Configure the controller (MAC and Serial).
2. Switch to **Automatic (DHCP)**.
3. Click **Cloud Setup**.
4. Click OK to register the controller.

## On the controller

1. Turn on **DIP switches 2 and 7**.
2. Connect the controller to the network.
3. Power on the controller.

The controller then connects to the Controller Gateway, pulls config from the OneLink Controller Registration Service, applies the IP configuration, and comes online to the local Command Centre server. Once online, turn the DIP switches off.


---

# 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.security.gallagher.com/knowledge-hub/products/cloud-services/onelink/cloud-assisted-controller-addressing.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.