Troubleshooting

Make sure you're using a USB-C data cable (not charge-only). Try a different USB port. Restart Mixlar Control. If using Bluetooth, ensure your device is powered on and within range.

Check that the correct COM port is selected in Settings. Try disconnecting and reconnecting the USB cable. If the issue persists, restart both the device and Mixlar Control.

Your device must be connected via USB for the initial Bluetooth pairing. Open the setup wizard and complete the Bluetooth step. Make sure Bluetooth is enabled on your PC and no other device is connected to your Mixlar.

If using USB, try a different cable or port. If using Bluetooth, make sure your device is within range and the battery (if applicable) is charged. Check for USB power saving in Windows Device Manager — disable “Allow the computer to turn off this device to save power”.

Try running as administrator. If you see a “single instance” error, check Task Manager for an existing Mixlar process and end it. Reinstall from mixlar.net/download if the issue persists.

Apps only appear in the slider config after they've played audio at least once. Open the app and play some audio, then refresh the list in Mixlar Control.

Open the slider config and verify the correct app is selected. If an app has multiple processes (e.g. browsers), you may need to select the specific subprocess. Try the “Active Window” option under the System tab for dynamic control.

Do not unplug your device during a firmware update. If it failed, try again — the device should still be in update mode. If your device appears unresponsive, hold the reset button for 10 seconds, then retry the update.

Double-check your Client ID. Make sure the redirect URI is exactly http://127.0.0.1:8721/callback in your Spotify app settings. Your browser must be able to reach localhost. See the full Spotify setup guide.

Ensure OBS is running and the WebSocket server is enabled (Tools → WebSocket Server Settings). Verify the port (default 4455) and password match what's in Mixlar Control. OBS 28+ has WebSocket built in — no plugin needed. See the full OBS setup guide.

Verify your HA URL is correct and accessible from your PC. Make sure the long-lived access token hasn't expired or been deleted. Test the URL in your browser first. See the full Home Assistant setup guide.

The Discord desktop app must be running (not just the browser version). Make sure the redirect URL is exactly http://127.0.0.1 in your Discord app's OAuth2 settings. Check that both Client ID and Client Secret are correct. See the full Discord setup guide.

Make sure Auto-Switch is toggled on in the App Profiles section. Verify that the correct app is linked to the profile. The app must be the focused (foreground) window for the switch to trigger.

Check that a macro is actually assigned to the button (not just labeled). Open the macro dialog and verify it has at least one step. If using a service action (OBS, Spotify, etc.), make sure that service is connected.