Intiface Central Setup: Getting Your Device Talking to the Browser

A step-by-step guide to installing and configuring Intiface Central as a bridge between your haptic device and browser-based apps like HaptiQ. Covers installation, server startup, device scanning, and common troubleshooting for Lovense, Kiiroo, WeVibe, Satisfyer, and more.

Why Intiface Central Exists

Web Bluetooth is convenient when it works, but it does not work everywhere. Firefox and Safari block it entirely. Even in Chrome or Edge, some devices—particularly those from Lovense, Kiiroo, WeVibe, Satisfyer, and Svakom—require protocols that browsers cannot speak directly. This is where Intiface Central comes in.

Intiface Central is the official desktop application for Buttplug.io, the open-source haptics control library. It runs a local WebSocket server that translates between your browser and devices that need native Bluetooth stacks, proprietary protocols, or additional radio hardware. If you have ever clicked "Connect" in HaptiQ and seen your device refuse to appear, Intiface Central is likely the missing link.

What You Need Before Starting

Intiface Central does not run on phones or tablets. It is a desktop bridge application only.

Step 1: Download and Install Intiface Central

Windows

  1. Visit intiface.com/central
  2. Download the Windows x64 installer (or x86 if you are on older hardware)
  3. Run the installer. Windows Defender SmartScreen may warn you; click "More info" then "Run anyway"
  4. The installer places Intiface Central in your Start menu and optionally creates a desktop shortcut

macOS

  1. Download the macOS .dmg from the same page
  2. Open the DMG and drag Intiface Central to Applications
  3. On first launch, macOS will block the app as unverified. Go to System Settings → Privacy & Security, scroll to Security, and click "Open Anyway"
  4. You may need to grant Bluetooth permissions when prompted

Linux

  1. Download the AppImage for your architecture
  2. Make it executable: chmod +x IntifaceCentral-x86_64.AppImage
  3. Run it directly or integrate with appimaged for desktop entry creation
  4. Ensure your user has access to the Bluetooth daemon (usually automatic on Ubuntu/Fedora, may need configuration on Arch)

Step 2: Start the Server

Launch Intiface Central. You will see a control panel with a large start/stop button and several configuration sections.

Critical: Do not change the default WebSocket server settings unless you know why you are changing them. The defaults are:

Click the Start Server button. The status indicator should turn green and display "Server Running." The application must remain open; closing it terminates the bridge.

Step 3: Configure Device Support

In the Device Managers section, ensure the relevant protocols are enabled:

Leave unchecked any protocols you do not need. Extra protocols can slightly increase scan time.

Step 4: Put Your Device in Pairing Mode

Each brand differs:

The device should be blinking or pulsing, not solid. Keep it within 1 meter of your computer during initial pairing.

Step 5: Scan and Connect in Intiface Central

  1. In Intiface Central, click Start Scanning
  2. Wait 10–30 seconds. Found devices appear in the Devices list with their names and battery levels
  3. Click the device name to connect. The status changes to "Connected"
  4. Test with the built-in sliders: expand your device entry and move the position slider. The device should respond

If the device does not appear, see the troubleshooting section below.

Step 6: Connect HaptiQ to Intiface Central

With Intiface Central running and your device connected:

  1. Open haptiq.app in Chrome or Edge
  2. Click the device connection icon in the top toolbar
  3. Select Buttplug.io (Intiface) as the connection method
  4. The default server address ws://localhost:12345 should populate automatically
  5. Click Connect. HaptiQ will handshake with Intiface Central and display your connected device

You can now generate funscripts from video and they will stream to your device through the Intiface bridge. The connection persists across page reloads as long as Intiface Central remains running.

Troubleshooting Common Failures

"No compatible devices found" in Intiface Central

Bluetooth disabled or no adapter: Verify Bluetooth is on in system settings. Desktop PCs without built-in Bluetooth need a USB adapter—any Bluetooth 4.0+ dongle works, but avoid the cheapest unbranded units which have poor LE support.

Device not in pairing mode: Some devices exit pairing mode after 60 seconds. Restart the device and scan again immediately.

Previously paired to phone: If your device was connected to your phone, it may still be bonded. Turn off Bluetooth on your phone or remove the device from your phone's Bluetooth settings, then power-cycle the device.

Device appears but will not connect

Windows Bluetooth stack conflicts: Some motherboard Bluetooth implementations conflict with the Windows default stack. Try a dedicated USB Bluetooth dongle and disable the internal adapter in Device Manager.

macOS permission issues: Go to System Settings → Privacy & Security → Bluetooth, ensure Intiface Central is listed and enabled. Restart the app after changing permissions.

HaptiQ cannot reach Intiface Central

Wrong server address: Verify Intiface Central shows ws://127.0.0.1:12345 and HaptiQ matches exactly. Do not use localhost vs 127.0.0.1 interchangeably if your system has unusual hosts file entries.

Firewall blocking: Windows Defender Firewall may block the WebSocket port. Add an exception for Intiface Central or temporarily disable the firewall to test.

Browser restrictions: Ensure you are in Chrome, Edge, or another Chromium derivative. Firefox and Safari cannot connect to local WebSocket servers from web content.

Connection drops during use

Bluetooth range: Stay within 3 meters with clear line of sight. 2.4 GHz interference from WiFi routers, microwaves, or USB 3.0 ports can disrupt LE connections.

USB power saving: Windows may power down your Bluetooth adapter. In Device Manager, find your Bluetooth adapter → Properties → Power Management, and uncheck "Allow the computer to turn off this device."

Advanced: Running Intiface Central Headless

For users who prefer command-line operation or want to run the bridge on a Raspberry Pi near their play space, Intiface Central supports headless mode:

./IntifaceCentral-x86_64.AppImage --server-mode --wsinsecureport 12345

This starts only the WebSocket server without the GUI. Useful for remote machines or automation.

When You Do Not Need Intiface Central

Some devices connect directly through HaptiQ without any bridge:

If your device works with Web Bluetooth directly, you may skip Intiface Central. However, most users with Lovense, Kiiroo, WeVibe, Satisfyer, or Svakom devices will need the bridge for reliable operation.

Keeping Everything Updated

Buttplug.io and Intiface Central update regularly to support new devices and fix protocol bugs. Check for updates monthly. HaptiQ's device detection improves alongside these updates, so keeping both applications current ensures the broadest compatibility.

Try HaptiQ

Once Intiface Central is running, generate your first synchronized funscript at haptiq.app. The free tier includes full device connectivity and script generation. Founding members can lock in lifetime Pro access for a one-time $99 (normally $199.99), limited to the first 100 members, via the pricing page.

Frequently asked questions

Do I need Intiface Central for every Buttplug-compatible device?

No. Some devices work with Web Bluetooth directly in Chrome or Edge, and others like The Handy use their own WiFi protocols. However, most Lovense, Kiiroo, WeVibe, Satisfyer, and Svakom devices require Intiface Central because browsers cannot speak their proprietary Bluetooth protocols natively.

Can I run Intiface Central on the same machine as HaptiQ?

Yes, and this is the recommended setup. Intiface Central runs a local WebSocket server on 127.0.0.1:12345 by default, which HaptiQ in your browser can reach directly. No network configuration or separate hardware is needed.

Why does my device show in Intiface Central but not respond to commands?

This usually indicates a partial pairing or protocol mismatch. Try removing the device from Intiface Central's device list, power-cycling the device to re-enter pairing mode, and scanning again. Also verify you have the correct device manager enabled—Lovense devices over Bluetooth LE need the BLE manager, not the Lovense Dongle manager.

Is Intiface Central safe to install?

Intiface Central is open-source software developed by the nonprofit Buttplug.io project and audited by the community. Windows Defender and macOS Gatekeeper may warn about it because the developers do not pay for code signing certificates. The source code is available on GitHub for review, and the application only communicates locally unless you explicitly configure external access.

Can I use Intiface Central with other funscript players besides HaptiQ?

Yes. Any application that speaks the Buttplug.io protocol can connect to Intiface Central, including ScriptPlayer, SyncPlayer, and custom applications. HaptiQ specifically uses the raw WebSocket interface to Intiface Central, which is the standard Buttplug.io v3 protocol.

Create a free HaptiQ account to generate a funscript from your own video.