Step-by-step guide to using the Zalo Nave with funscripts in HaptiQ via Web Bluetooth or Intiface Central — plus how script motion maps to this nipple clamps.
As a nipple clamps, HaptiQ maps funscript position to vibration intensity — the rhythm of the script becomes the rhythm of the device.
This is expected. The device runs Bluetooth in host mode, meaning it waits to be driven by a controller rather than advertising itself to a browser, so it will never appear in the browser's device picker. Connect it in Intiface Central instead, and HaptiQ will reach it through Buttplug.io once Intiface reports it as connected.
Yes — Intiface Central, on a desktop machine. BT4LE (Host mode) cannot be reached from a browser, so Intiface acts as the bridge and HaptiQ talks to it over Buttplug.io. It is free and open source.
The connection and the script are separate steps, and this symptom means the script is fine but commands are not arriving. Confirm the device still shows as connected — Intiface can lose the device without HaptiQ noticing immediately — then check the device is charged and not simultaneously connected somewhere else. A funscript with a flat section will also produce genuine stillness, so scrub to a section with obvious motion before concluding it is broken.
Every command goes through Intiface before it reaches the device, which adds a hop. Keep Intiface on the same machine as your player rather than across the network, and make sure it is not competing for CPU with video decoding.
Yes. A funscript is a plain motion file and carries no device information, so any script plays on any supported hardware. HaptiQ can also generate one from your own video, which matters when an existing script was timed to a different cut — that mismatch causes drift no offset can fix.
Zalo Nave overview · Funscripts for nipple toys · Create a free HaptiQ account