OBS

What this page is

Connections → OBS holds a single card, OBS Studio — the link between the app and OBS on your machine. While that link is up, the rest of the app can drive OBS: scenarios get five actions — OBS: Switch scene, OBS: Source filter, OBS: Show or hide source, OBS: Mute or unmute audio and OBS: Audio input volume — the voice assistant can be told to change scene, and Stream Status counts OBS among the signals that say the broadcast is running.

The link is one-way in an important sense: the app sends commands to OBS and reads the list of scenes, sources and filters. It never sees your picture or your sound.

How to set it up

1. Switch the server on inside OBS

This is the step people miss, and nothing on our side can do it for you. In OBS Studio open Tools → WebSocket Server Settings and turn the server on. The same window holds the port — 4455 unless you change it — and, behind Show Connect Info, the password.

OBS has carried this window built in since version 28. On anything older the obs-websocket plugin has to be installed separately, and the app cannot connect until it is.

2. Fill in the three fields

Open Connections → OBS. A card that reads Disconnected means the module is off: press Connect OBS Studio and it turns on and opens its settings straight away. If it is already on, press Configure.

Under OBS Studio Connection Settings:

• OBS WebSocket Host — already filled in for OBS on this same computer. Change it only when OBS runs on another machine, and then it takes that machine's address on your local network.
• OBS WebSocket Port — filled in with the usual OBS value, 4455. It has to match what the OBS window showed.
• OBS WebSocket Password — the password from OBS. Once one is stored the field stays empty and shows Password saved — leave empty to keep it: an empty field keeps the stored password, so editing the port never wipes it.

3. Test it

Test Connection saves the fields first, then answers Successfully connected to OBS! or Failed to connect to OBS. Check parameters and password. Save Settings saves without testing.

Connection Status turns to Connected, and two testers appear below — they are shown in that state only:

• [DEBUG] OBS Scene Tester — Select Scene, then Switch Scene.
• [DEBUG] OBS Filter Tester — Select Scene, Select Source, Select Filter, then Enable Filter or Disable Filter.

Every command and its answer land in OBS command log, and Clear Logs empties it. The testers are there to prove the link works before you build a scenario on top of it.

What is normal here

With OBS closed, the settings page shows Disconnected while the card shows Connecting... Both are right: the module is running and retrying, and the connection is not up. There is nothing to press — start OBS and it connects on its own.

The scene list can be empty right after connecting. It is read from OBS once the link is established; reopen the page if it looks bare.

Wrong password and wrong port fail the same way, with the one message above. If the test fails, check the OBS window again rather than guessing — that window is the only place the right values exist.

What it cannot do

• The settings page has no connect or disconnect button. The connection follows the fields and the app's own retries.
• Neither card button drops the OBS link alone. Disconnect switches the whole module off; Remove connection wipes everything typed here, password included.
• Nothing here creates, renames or deletes anything in OBS. Scenes, sources and filters are only ever chosen from what already exists there.
• The testers act once and save nothing. They are not a scenario and not a schedule.
• There is no recording or streaming control on this page — no start, no stop, no pause.
• No picture and no sound from OBS reach the app. Nothing is captured, previewed or recorded on our side.
• The section holds OBS Studio and nothing else. Streamlabs Desktop, XSplit and other capture programs have no card here and no module.