Device Information
Full refresh takes ~30 seconds. Values appear as they load.
Cursor
Sip & Puff
Red markers show trigger values. Use Live view while adjusting thresholds.
Joystick
Range 0.01–1.0. Inner < outer. Rings update when set.
- Push to corner 1 (top-left)
- Push to corner 2 (top-right)
- Push to corner 3 (bottom-right)
- Push to corner 4 (bottom-left)
- Hold still — re-center
- Verify stored calibration
Captures 4 corners. Follow Hub display prompts; progress shown above. If a step fails, re-center and retry.
Stored calibration values
Feedback
0–10, applies immediately. Hub LEDs blink to preview each change.
Bluetooth
Switching to Bluetooth restarts the LipSync. It then advertises as the BLE device name above. Open your computer’s Bluetooth settings and pair with it. USB remains available for settings.
Pairing instructions
1. Click Switch to Bluetooth. The device saves the setting, restarts, and begins advertising.
2. On your computer, open Bluetooth settings and look for the device name shown above.
3. Select it to pair. The LipSync appears as a mouse (HID).
4. To return to USB mode, reconnect via USB, open this panel, and select a USB mode from the operating mode dropdown in the Device section.
Device diagnostics
Health check
Self-tests
Live diagnostic stream
Select a stream to view live sensor data in the panel below.
Remote Hub menu
The mirror follows the Next/Select presses you send — the device never reports its menu state, so physical button presses, joystick-driven steps, or the Hub’s inactivity timeout can make it drift. Select Open again to resync (the Hub always reopens at the main menu).
Maintenance
Restores all settings to defaults (confirmation required).
Help & troubleshooting
Device does not appear in the browser prompt
Wrong cable. Many USB cables are charge-only. Use a data cable and connect directly to your computer, not through a hub or dock.
Another app is using the port. Close the Arduino IDE, CuteCom, PuTTY, or any other serial monitor. Only one app can open the port at a time.
Browser not supported. Web Serial works in Chrome, Edge, and Opera on desktop. Chrome on Android works with a USB-C / OTG cable. iOS, Firefox, and Safari are not supported.
Device needs a reboot. After a mode change or reset, wait ~30 seconds for the LipSync to finish restarting before trying to connect.
If using the Android WebUSB fallback, the browser will only see the device when it is plugged in and awake. Try unplugging and replugging, then click Connect again.
Commands time out or return errors
Commands run one at a time over a serial queue. If a previous command did not finish, everything backs up. Disconnect, wait 5 seconds, then reconnect to reset the queue.
Do not press the physical Hub buttons or use the Hub on-screen menu while a web command is pending. The device can only handle one settings interaction at a time, and the physical menu does not send a response — the web app will wait until it times out.
If a single command repeatedly fails, run Health check in the Diagnostics section to verify the device is responding correctly.
Settings won’t load — values show ERR or stay stuck on …
Values load one at a time in sequence (17 total, ~30 seconds). If one command times out, it shows ERR and loading continues. Click Refresh all settings to retry only the failed items.
If the overall load takes longer than 2 minutes, the app gives up and shows whatever loaded so far. This usually means the connection is unreliable — disconnect and reconnect with a shorter cable or different USB port.
The Device section shows a progress bar during loading. Watch it to see how far along the process gets.
Calibration fails or gets stuck
Keep the mouthpiece perfectly still for the neutral-position capture (the first step and the last re-centering step). Any movement during these steps produces a bad calibration.
Push firmly to each corner when prompted and hold until the status updates. If a corner reads below minimum strength, calibration finishes but marks it as weak — re-run and push more firmly.
If calibration disconnects mid-procedure, the LipSync’s built-in calibration was not completed. Just re-center the mouthpiece and start again. The previous calibration values remain in place until a new one finishes.
Mode switch (Mouse / Bluetooth / Gamepad) seems stuck
The setting was saved but the restart did not confirm. This is common. The new mode is stored on the device. Unplug the LipSync and plug it back in, or wait ~30 seconds for its watchdog timer to trigger the restart.
After the restart, reconnect. The Device section will show the new operating mode. If it reconnected in the old mode, open the Device card and verify the dropdown matches what you selected.
Gamepad mode forces a specific command order (Communication mode first, then Operating mode). The app handles this automatically. Gamepad mode is USB-only.
Bluetooth does not pair or connect
Click Switch to Bluetooth in the Bluetooth section. The device saves the setting, restarts, and begins advertising as LS_<device ID>. Open your computer’s Bluetooth settings and pair with it.
If the device does not appear in Bluetooth settings, wait 30 seconds for it to finish restarting after the switch, then scan again. If it still does not appear, reconnect via USB, open the Bluetooth section, and verify the device name and status.
While in Bluetooth mode, the USB serial port remains available for settings changes. To return to USB HID mode, reconnect via USB and select Mouse from the operating mode dropdown in the Device section.
Connection keeps dropping or “No data received for 30s”
The app has a built-in watchdog: if no serial data arrives for 30 seconds, it warns you. If the connection is actually lost, the read loop attempts to recover — it cancels the reader, waits 2 seconds, and opens a new reader on the same port.
If recovery fails, the app disconnects. This can happen with long USB cables, hubs with power management, or Android devices that put the USB bus to sleep. Try a shorter cable, connect directly, and disable USB power saving if possible.
Health check finds problems
The diagnostics test checks: pressure sensors return plausible values (300–1200 hPa, not both zero), the joystick reports valid X/Y, the neutral position is stored, and all four calibration corners exist.
Pressure sensors read zero or out of range — the mouthpiece may be blocked, or the sensor may need recalibration on the device itself. Joystick or calibration issues — run a full calibration from the Joystick section.
Appearance settings or dark mode won’t save
Theme settings (colors, dark mode) are saved in your browser’s localStorage. If you clear your browser data or use private/incognito mode, they reset to defaults. Click Reset to defaults in the Appearance popup to start fresh.
Remote Hub menu controls
Open starts the Hub’s on-screen menu and shows a mirrored copy of the Hub screen in the app; Close stops the menu and hides the mirror. Next and Select correspond to short presses of S1 and S2 — use them to move through the menu and activate items.
The device never reports its menu state over serial, so the mirror is driven locally by the presses you send. Physical button presses, joystick-driven calibration prompts, and the Hub’s inactivity timeout can make it drift from the real display — select Open again to resync (the Hub always reopens at the main menu).
Settings changed through the Hub menu do not update the app’s displayed values — click Refresh all settings afterwards.
General tips
Changes apply instantly. Sip/puff thresholds, deadzones, speed, scroll, sound, light, and LED brightness all take effect on the device immediately after you click Set.
Physical menu changes do not send a response back to the web app. If you change a setting on the Hub itself, the displayed value in the web app will be wrong until you click Refresh all settings.
Soft reset restarts the device (same as unplugging and plugging it back in). Factory reset restores ALL settings to defaults, including calibration — you will need to recalibrate after a factory reset.
Use the Download log button in the Log section to save a timestamped log file before contacting support. It captures every command sent and every response received.