Troubleshooting: Kinesis Advantage 360 Pro Bluetooth

Quick Reference

Field Value

Device

Kinesis Advantage 360 Pro (KB360-PRO)

MAC Address

FF:E9:28:2C:ED:FD (Adv360 Pro)

Connection Types

Bluetooth (3 profiles) + USB-C

Environment

Arch Linux, BlueZ 5.x, PipeWire

Common Symptoms

Random disconnects, reconnect failures, lag

Success Criteria

Stable connection for 8+ hours without drops

What Fixed It (2026-02-27)

Root Cause: Stale Bluetooth pairing cache after system changes.

Solution: Re-pair keyboard (Solution 2: Re-pair Keyboard)

bluetoothctl
remove FF:E9:28:2C:ED:FD  # Clear old pairing
scan on                   # Find device
pair FF:E9:28:2C:ED:FD     # Pairing successful
trust FF:E9:28:2C:ED:FD    # Trust succeeded
connect FF:E9:28:2C:ED:FD  # Connection successful

Time to resolve: ~5 minutes

Symptom → Solution Matrix

Symptom Likely Cause Solution

Keyboard disconnects randomly

Bluetooth interference / power management

Solution 1: Disable Bluetooth Power Management

Won’t reconnect after sleep

BlueZ pairing cache stale

Solution 2: Re-pair Keyboard

Lag/delay in keystrokes

Bluetooth coexistence with WiFi

Solution 3: WiFi/Bluetooth Coexistence

Only one half connects

Split keyboard sync issue

Solution 4: Split Keyboard Sync

Connects but no input

HID profile not loaded

Solution 5: HID Profile Issues

Solutions

Solution 1: Disable Bluetooth Power Management

When to use: Random disconnects, especially after idle periods

Steps:

  1. Check current power management status:

    cat /sys/module/bluetooth/parameters/disable_ertm
bluetoothctl show | grep -i power

  2. Disable USB autosuspend for Bluetooth adapter:

    # Find Bluetooth adapter
lsusb | grep -i bluetooth

# Disable autosuspend (replace X-Y with your device)
echo 'on' | sudo tee /sys/bus/usb/devices/X-Y/power/control

  3. Make persistent via udev rule:

    sudo tee /etc/udev/rules.d/50-bluetooth-power.rules << 'EOF'
# Disable autosuspend for Bluetooth adapters
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="XXXX", ATTR{idProduct}=="YYYY", ATTR{power/control}="on"
EOF

  4. Verify:

    cat /sys/bus/usb/devices/X-Y/power/control
# Expected: on

Solution 2: Re-pair Keyboard

When to use: Won’t reconnect after sleep/reboot

Steps:

  1. Remove existing pairing:

    bluetoothctl
# In bluetoothctl:
devices
remove FF:E9:28:2C:ED:FD  # Kinesis MAC

  2. Put Kinesis in pairing mode:

    Hold Fn + Profile key (1/2/3) for 3 seconds
LED should blink rapidly

  3. Pair fresh:

    bluetoothctl
scan on
# Wait for "Kinesis KB360" to appear
pair FF:E9:28:2C:ED:FD
trust FF:E9:28:2C:ED:FD
connect FF:E9:28:2C:ED:FD

  4. Verify persistent:

    bluetoothctl info FF:E9:28:2C:ED:FD | grep -E "(Paired|Trusted|Connected)"
# All should show: yes

Solution 3: WiFi/Bluetooth Coexistence

When to use: Lag, dropped keystrokes, interference

Steps:

  1. Check if WiFi and Bluetooth share antenna:

    lspci -k | grep -A3 -i wireless
lsusb | grep -i bluetooth
# If same chip (Intel AX200, etc.), coexistence applies

  2. Move to 5GHz WiFi (reduces 2.4GHz interference):

    nmcli connection show
nmcli connection modify "WiFi-SSID" 802-11-wireless.band a
nmcli connection up "WiFi-SSID"

  3. If still problematic, use USB-C:

    Connect USB-C cable to right half
Keyboard switches to wired mode automatically

Solution 4: Split Keyboard Sync

When to use: Only left or right half works

Steps:

  1. Power cycle both halves:

    Turn off both halves (switches on bottom)
Wait 10 seconds
Turn on RIGHT half first
Wait 5 seconds
Turn on LEFT half

  2. Check wireless sync between halves:

    Left LED should mirror right LED after power on
If not synced, halves can't communicate

  3. Re-sync via USB:

    Connect BOTH halves via USB-C
Wait 30 seconds
Disconnect and test Bluetooth

Solution 5: HID Profile Issues

When to use: Connects but no keyboard input

Steps:

  1. Check Bluetooth profiles:

    bluetoothctl info FF:E9:28:2C:ED:FD | grep -i uuid
# Should show: Human Interface Device

  2. Restart Bluetooth service:

    sudo systemctl restart bluetooth
sleep 3
bluetoothctl connect FF:E9:28:2C:ED:FD

  3. Check input devices:

    cat /proc/bus/input/devices | grep -A5 -i kinesis
# Should show keyboard handlers

  4. Test input:

    sudo libinput debug-events
# Type on Kinesis, should show key events

Diagnostic Commands

Check Bluetooth Status

# Adapter status
bluetoothctl show

# Connected devices
bluetoothctl devices Connected

# Device info
bluetoothctl info FF:E9:28:2C:ED:FD

View Logs

# Real-time Bluetooth logs
journalctl -f -u bluetooth

# Recent disconnect events
journalctl -u bluetooth --since "1 hour ago" | grep -i disconnect

Test Connectivity

# Signal strength (if available)
hcitool rssi FF:E9:28:2C:ED:FD

# Connection quality
btmon &
# Connect keyboard, watch for errors

Prevention

  • Keep keyboard firmware updated (Kinesis SmartSet app)

  • Avoid placing keyboard near WiFi router

  • Use wired mode for critical work (USB-C always works)

  • Monitor /var/log/messages for Bluetooth errors

Related

Changelog

Date Change Reason

2026-02-27

Initial creation + resolution documented

INC-2026-02-27-kinesis-bt - Re-pair fixed disconnect issue