Common Issues


OBS Connection #

To connect to and control OBS, SAMMI uses an add-on called the OBS WebSocket.

You can find a link to the latest compatible version of the WebSocket in the Step-by-step Tutorial.

Try these steps to troubleshoot the connection between SAMMI and OBS WebSockets:

  • OBS Studio 28 and OBS Websockets
    If you have just downloaded OBS Studio 28, it comes bundled with OBS Websocket 5.0. This means that if you are running SAMMI using the OBS Websocket 4.9.1 protocol, you will not be able to connect to OBS.

Instead, you will either have to:

  1. Switch to the OBS Websocket 5.0 protocol in SAMMI and make the necessary changes to your Fetch OBS Data, Custom Packet and Send OBS Requests to reflect the correct OBS Websocket 5.0 protocol syntax and change your OBS Triggers, OR
  2. Download the OBS Websocket 4.9.1-compat plugin HERE, and create a new OBS instance in SAMMI to run the OBS Websocket 4.9.1 protocol. All your commands will have to specify which OBS Websocket protocol you want SAMMI to use.
  • Run as administrator
    Try running SAMMI as an administrator. Right click on the SAMMI launch file and select Run as administrator.

  • Check your firewall and antivirus
    Make sure your firewall is not blocking SAMMI.
    You can try temporarily disabling your antivirus/firewall or adding an exception to allow the app through.

  • Verify password settings
    The password you enter in OBS > Tools > OBS Websocket Settings must match the password you enter in SAMMI > OBS Connections. If you do not use a password, uncheck Enable authentication.

  • Verify ports settings
    The port entered in OBS > Tools > OBS Websocket Settings must match the port in SAMMI > OBS Connections.
    The default port for WebSockets 4.x.x is 4444. The default for WebSockets 5.x.x is 4455.
    Note that this port MUST be different from the port number used in your Bridge settings.

  • Try Non-Blocking Connection
    In SAMMI, go to OBS Connections and check/uncheck “Non-Blocking”.

  • Change IP connection
    Normally you will use to connect to OBS, but you can try local IP as well:
    1. Launch command line (cmd.exe) and run ipconfig command.
    2. Note down your IPv4 address (it will start with 192.168).
    3. Go to SAMMI > OBS Connections and change the IP address.
  • Try connecting using other means
    You can try a chrome extension Simple Websocket Client to check if you can make a connection in the first place.


SAMMI Deck #

If you press ‘Connect’ in your SAMMI Deck and nothing happens (you only see the progress icon), it means it hasn’t established a successful connection to SAMMI Core.

  • Outdated SAMMI Deck
    Make sure you’re using the latest version of SAMMI Deck.

  • Mismatched port/password settings
    Confirm that the Port and Password entered there match the Port and Password in your SAMMI Deck connection settings. The default port is 9425.
    Please note that these settings are separate from those used by OBS WebSockets, and must use a different port number.

  • Blocked by firewall
    Make sure your firewall is not blocking SAMMI.
    You can try temporarily disabling your antivirus/firewall or adding an exception to allow the app through.

  • Unable to connect to the Android App
    Make sure your firewalls/antivirus has whitelisted the app.
    Make sure both your PC and your mobile device is on the same network.
    VPNs do not work well with the mobile app, so make sure you have disabled your VPN settings.\


Twitch Connection #

Getting an ERR_BADAUTH error #

Your auth token probably expired.

  1. In SAMMI Core, go to Twitch Connections. Click “Revoke Token” for the problem account.
  2. Link your Twitch account again by pressing Link Streamer Account or Link Bot Account button.

Twitch Alerts don’t work #

Check your Twitch Pubsub/Chat connection
Make sure your Twitch Pubsub and Chat is connected (the light indicator must be green for both) and you’re listening to the right topics (you can check them under Twitch Connections).

Twitch Connected
Twitch Connected

Try triggering a test alert from your Bridge In your Bridge, go to Twitch Triggers tab and press any of the test buttons.
A small yellow notification message should pop up in the bottom-left corner of SAMMI Core.

  • I do not see the message at all - your Bridge is not connected to SAMMI. You might be running a wrong version or duplicate instance of your Bridge.
  • I see the message, but buttons do not trigger at all - your button triggers are set up wrong. Follow the guide in our Triggers section.
  • I see the message, buttons trigger, but nothing happens in OBS - You’re either not connected to OBS, or your button commands are wrong.

Twitch: Send message doesn’t work #

Check you’re connected to Twitch Chat
In SAMMI > Twitch Connections, press “Connect Twitch Chat”, then enable Auto connect to Twitch Chat, otherwise you will need to press this button every time you launch SAMMI.

Check you’re sending the message to the right channel

  • If you have only a single Twitch account linked, leave the channel name empty.
    Chat Message command with single Twitch account linked
    Chat Message command with single Twitch account linked
  • If you have multiple Twitch accounts linked, correctly fill out the field with your Twitch channel name (all lowercase characters)
    Chat Message command with multiple Twitch accounts linked
    Chat Message command with multiple Twitch accounts linked

Check you’re not sending too many messages
If you send too many messages in a short period of time, Twitch might temporarily block you from sending more.

Twitch Chat Whispers do not work #

Using /w username in a Send Chat Message command
This method for sending whispers is unreliable, as Twitch can prevent accounts from sending whispers using this method without warning or any visible indication it has.
Instead, try the Send Whispers command.


Crashes On Launch/SAMMI Core Doesn't Start #

You can try temporarily disabling your antivirus/firewall or adding an exception to allow the app through.

Corrupted Deck Files
If the decks_data.json file in the ‘json’ folder within your default SAMMI folder is 0kb in size, this means your deck has somehow been corrupted. Check and make sure that decks_data_old.json and decks_data_very_old.json are NOT 0kb in size.
Make a backup of your decks_data.json file, then rename decks_data_old.json to decks_data.json. Restart SAMMI.

Faulty sound drivers
You can try reinstalling your sound drivers.

Incompatible versions between SAMMI Core and SAMMI Deck
You may have a newer version of the SAMMI Deck compared to SAMMI. Close all connections to SAMMI (OBS, SAMMI Deck) and restart SAMMI, then update it to the latest version.
If the crash persists, you can also save the ‘json’ folder in your SAMMI folder to a different location, then delete the folder. Restart (or download a new copy of) SAMMI, then update your SAMMI to the latest version. After doing so and verifying that it no longer crashes, copy the json back into your SAMMI folder.

Run SAMMI Core in Compatibility Mode
You can try right-clicking the Sammi Core.exe file and selecting ‘Troubleshoot’. You can also select the option to run SAMMI Core.exe in Windows 8 Compatibilty mode.

Unplug USB controllers
Some USB controllers (GameCube controller via a USB adapter) may cause driver related conflicts. Unplug them, and then restart SAMMI. You should be able to plug the controller back in once SAMMI has started.