Before you start
- VRA Core runs for your studio. See Machine specs.
- The RCS Zetta machine can reach the VRA Core machine on the Core API port, 3002 by default.
Add the RCS Zetta connection in VRA Cloud
- Go to Settings → Studio → Automations in VRA Cloud.
- Click Add Automation and pick Rcs Zetta.
- Turn on Enabled. A new connection starts switched off.
- Copy the URL under API endpoint. RCS Zetta sends its data to this URL.
- Click Add connection.
0.0.0.0, replace it with the IP address of the VRA Core machine, for example 192.168.1.20.
Set up RCS Zetta to send now playing data
- In Zetta, create a new Live Metadata entry and set it to Device Method → Device → HTTP.
-
Paste the URL from VRA Cloud into Device Method → URL.

- Leave the Advanced → Output field empty. Zetta then sends its full format, which is what VRA reads.
Check that VRA receives RCS Zetta data
Start an item in RCS Zetta, then check two places:- Settings → Studio → Automations: the RCS Zetta connection shows a green status dot, the title and artist of the playing item, and the time of the last update.
- AutomationLink in the main menu: the item shows under On air, and the upcoming items under Next and Rundown.
Troubleshoot RCS Zetta
The RCS Zetta connection stays idle
VRA Core receives nothing from RCS Zetta. Check, in this order:- Enabled is on in the connection, and AutomationLink Enabled is on at the top of Settings → Studio → Automations.
- The URL in RCS Zetta uses the IP address of the VRA Core machine, not
0.0.0.0. - A firewall on the VRA Core machine allows incoming connections on the Core API port, 3002 by default.
The RCS Zetta connection is active but shows no title or artist
The Advanced → Output field in Zetta contains a template. Empty it, so Zetta sends its full format.Related
- Link Radio Automation
- Radio Automation Data: music track meta and item groups