Connect
Pair your device with the operating system, then grant PairPanel access through the browser-owned hardware prompt.
Open source · browser based · local first
Your devices.
One control panel.
Configure supported Bluetooth headphones and peripherals directly from a compatible browser. No vendor account. No companion app. PairPanel only exposes controls verified for your model.
Runs locally in your browser
No account
No cloud sync required
Hardware access: Chromium desktop
Detect
PairPanel identifies the model adapter and loads only the settings that protocol and hardware are known to support.
Control
Review changes before they are written. Unknown devices stay write-disabled instead of receiving guessed commands.
Supported device work starts here.
Compatibility is tracked by exact model, not by broad brand claims.
Headphones & earbuds
Soundcore Liberty Air 2 Pro
Product code A3951 · Bluetooth Classic RFCOMM/SPP
A3951 support is implemented and protocol-tested. Physical-device validation is still required before it is marked fully verified.
One workflow. Device-specific capabilities.
The interface stays consistent while the available controls come from the connected model.
- Pair normallyUse your operating system's Bluetooth settings first. PairPanel does not replace the base Bluetooth pairing stack.
- Grant explicit accessThe browser asks you to choose the device or exposed service. PairPanel never requests hardware permission silently.
- Read current stateBattery, firmware and configurable settings are read from the known device adapter before controls are enabled.
- Apply deliberatelyEditable settings use a staged Revert / Apply flow so you can review changes before writing them to hardware.
Built for hardware you own.
Local first
Device communication happens in the browser. PairPanel does not need an application backend for normal control.
Capability honest
Unsupported features are omitted. A model is not treated as compatible just because another device from the same brand works.
Reversible first
Normal runtime settings are prioritized. Firmware, bootloader and calibration workflows require a separate safety bar.
Questions before you connect.
Does PairPanel send my device data to a server?
Normal device communication and saved PairPanel state stay in your browser. The current static site does not require a PairPanel application backend.
Does PairPanel work with every Bluetooth device?
No. Vendor control protocols differ by model. Browse the device directory for adapters that have actually been added.
Which browsers can access hardware?
The dashboard can render in modern browsers, but current hardware control depends on APIs such as Web Serial. Desktop Chromium browsers are the primary target today.
Can PairPanel update firmware?
PairPanel can read supported firmware versions, but firmware installation is not shipped yet. Firmware flashing needs a separately verified update protocol, trusted firmware source, recovery strategy and physical-device validation.