OBS/vMix commands not working
Debug OBS and vMix command execution failures, for both Direct and Helmo Middleware connections.
TroubleshootingIntermediateUpdated
If OBS or vMix commands aren't executing when you press buttons or run elements, here's how to troubleshoot.
Using Direct connection
OBS not responding
- Check OBS is running and the WebSocket Server is enabled (Tools > WebSocket Server Settings).
- Verify port and password match your integration config in Connect.
- Test locally: open a browser on the OBS machine and try connecting to
ws://localhost:4455. - Firewall: if connecting from another machine, make sure the port is open.
vMix not responding
- Check vMix is running and the Web Controller is enabled (Settings > Web Controller).
- Verify IP and port. The default port is 8088.
- Test locally: open
http://localhost:8088in a browser on the vMix machine. You should see the vMix Web Controller.
Using Middleware connection
- Check Helmo Middleware: is it running and showing Online in the Middleware tab?
- Verify Helmo Middleware is on the same machine as OBS/vMix (or on the same network).
- Check Helmo Middleware logs: the app shows a log of received and forwarded commands.
- Restart Helmo Middleware if commands are stuck.
Common issues
- Scene/source name mismatch: names are case-sensitive. "Game Scene" is different from "game scene".
- Source not in active scene: show/hide source commands target sources in a specific scene. Make sure the source exists in the scene you're targeting.
- Multiple OBS instances: if you have multiple OBS installations, make sure you're connected to the right one.