> ## Documentation Index
> Fetch the complete documentation index at: https://docs.visualradioassist.live/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the names from the glossary at https://docs.visualradioassist.live/glossary: Audio Manager (two words), command (never commando), on air and off air (never live) for programs and studios, and server apps for the VRA apps installed in the studio.
> Say which app an answer applies to, like VRA Cloud, the Core or the Output Player, and the version when the page names one.
> Only give settings, values and steps that are in these docs. Never invent one. If the docs don't cover it, say so.
> When the docs don't answer the question, send the user to Visual Radio Assist support at https://cloud.visualradioassist.live/support.

# Signals

> Switch audio auto switching and camera automation on or off from outside VRA, and add your own signals for dashboards, automations and the Core API.

A signal is a named value that Visual Radio Assist and your own systems both read and write, like a tally or a GPI. Use it to take automation out for an item from a Stream Deck, a dashboard or your own system, and to give it back. Every studio comes with two signals, and with a Pro license you add your own.

Signals live in **Settings → Studio → Signals**.

## How signals work

1. A signal has a value: on or off, a number or a text.
2. Something sets that value: a [dashboard](https://docs.visualradioassist.live/dashboards.md) button, the Signals page, a control surface through the [Core API](https://docs.visualradioassist.live/develop-with-vra/core-control-api/routes.md), or a VRA product.
3. VRA reacts to it: the default signals switch automation on or off, and an [automation](https://docs.visualradioassist.live/automations.md) can check any signal in its conditions.

Each signal remembers what set it last and when, so you can see why automation stopped.

## The default signals in every studio

Every studio has two default signals. They come with every license, belong to their own studio and cannot be deleted.

| Signal | Identifier | When it is off |
| - | - | - |
| **Audio Director** | `audio-director` | The [Audio Manager](https://docs.visualradioassist.live/audio-manager.md) ignores audio auto switching. The fallback loop keeps running. |
| **Camera Assist** | `camera-assist` | [Camera Assist](https://docs.visualradioassist.live/cameras.md) angles run no automation and go straight to their override command. |

You can rename a default signal and turn it on or off, but its scope, identifier and value type are fixed, so one studio never switches off automation in another.

## Turn a signal on or off

To turn a signal on or off in VRA Cloud, open **Settings → Studio → Signals**, click the dots next to the signal and pick **Turn on** or **Turn off**. To set a number or a text, click the signal, enter the value under **Current value** and click **Set**.

Only input signals that are enabled can be set. An output signal is set by VRA, and its value is read only.

On air, a **Signal button** on a [dashboard](https://docs.visualradioassist.live/dashboards.md) or a key on a Stream Deck with [Bitfocus Companion](https://docs.visualradioassist.live/develop-with-vra/core-control-api/bitfocus-companion-module.md) is quicker than the settings page.

## Add your own signal

Your own signals need a Pro license. With a lower license, **Add signal** is unavailable and the two default signals still work.

To add a signal, open **Settings → Studio → Signals** and click **Add signal**. Fill in the settings and click **Create signal**.

| Setting | What it does | Values |
| - | - | - |
| **Scope** | **This studio**: only this studio sees the signal and it has its own value. **Station wide**: every studio of the station sees it and shares one value. | This studio, Station wide |
| **Label** | The name people see in VRA Cloud, on dashboards and on control surfaces. | Text |
| **Identifier** | How external systems address the signal, on MQTT and over the Core API. Filled in from the label. | Lowercase letters, digits, `-` and `_`, up to 64 characters |
| **Description** | What the signal is for. | Text |
| **Direction** | **Input, set from outside VRA**: your systems write it and VRA reads it. **Output, set by VRA modules**: VRA writes it and your systems read it. | Input, Output |
| **Value** | The type of value the signal holds. | On / off, Number, Text |
| **Default value** | The value the signal starts on. | Matches **Value** |

After you create a signal, its sheet also shows **Enabled**. When **Enabled** is off, the signal keeps its value, but nothing can write it.

## Use a signal in an automation

To run a command when a signal has a value, add the **Signal state** condition to an [automation](https://docs.visualradioassist.live/automations.md), pick the signal and the value. A station wide signal shows with `(station wide)` after its name.

Deleting a signal stops every condition that uses it. The Signals page shows how many conditions use a signal, and the delete confirmation says so again.

## Set a signal from outside VRA

The [Core API v2](https://docs.visualradioassist.live/develop-with-vra/core-control-api/routes.md) reads and writes signals from a control surface or a script on the studio network, by id or by identifier. For example, `/api/v2/signals/audio-director/off` switches off audio auto switching for the studio. The same routes work over [TCP and OSC](https://docs.visualradioassist.live/develop-with-vra/core-control-api/tcp-and-osc.md).

## Limitations

* Signals cannot be added below a Pro license. The two default signals work on every license.
* A default signal cannot be deleted, moved to another studio or changed to another value type.
* An output signal cannot be written from a dashboard, the Signals page or the Core API.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.