> For the complete documentation index, see [llms.txt](https://docs.simplebooth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplebooth.com/hardware-and-gear/lighting/lighting-integrations/mobibooth-light-control.md).

# Mobibooth Light Control

The steps below walk you through connecting your Mobibooth lighting to HALO.

#### Setup Steps

1. Power on your Mobibooth device.
2. Open the HALO app and launch to the [PreFlight Check](https://docs.simplebooth.com/running-your-event/preparing-for-events/launching-your-booth/preflight-check) and locate the 'Devices' section
3. Tap the 'Connect Light' button on the 'Light' card. The app will automatically scan for your Mobibooth device.
4. When your device appears in the list, tap 'Connect.'
5. Use the model picker to select your specific Mobibooth model.

Once connected, your light will automatically transition between an eye-catching animation, bright white light during capture, and a softer dim white while editing and sharing.

#### Lighting Adjustments

Change the brightness and color temperature during capture by opening [Mission Control](https://docs.simplebooth.com/running-your-event/monitor-booth-status), tapping the 'Light' tab at the bottom, and selecting 'Lighting' on the left side


---

# 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://docs.simplebooth.com/hardware-and-gear/lighting/lighting-integrations/mobibooth-light-control.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.