#Bluetooth Keyboard is connecting but not pairing with HAOS - Legacy Pairing suspected as unsupported

1 messages · Page 1 of 1 (latest)

astral thicket
#

Goal - to connect a bluetooth keyboard to HA OS. Previous keyboards I've used worked using the pair method explained below but I suspect this the "legacy pairing" method

HA OS - 2025.6.1
VM running on Synology NAS

I've used a few Bluetooth keyboards in the past along with the "Keyboard Remote" integration.

The usual process I take is using the terminal to pair/connect/trust the device and then it appears as an Event ID which can then be set up using Keyboard Remote.

This new keypad/keyboard just will not **pair **though.

From SSH I ran

pair xx:xx:xx:xx:xx:xx 
trust xx:xx:xx:xx:xx:xx 
connect xx:xx:xx:xx:xx:xx ```

I ran all three of these, but the pairing command doesn't come up with the pin entry I was expecting, I suspect that's the "Legacy Pairing" but I'm not 100% sure.

it just says -

```Attempting to pair with 53:93:4E:XX:XX:XX
AdvertisementMonitor path registered```

And nothing else, it just goes back to the command line.

If I then run info xx:xx:xx:xx:xx:xx it shows it as trusted, connected but not paired....

```Device XX:XX:XX:XX:XX:XX (public)
        Name: MINI-KEYBOARD
        Alias: MINI-KEYBOARD
        Appearance: 0x03c1 (961)
        Icon: input-keyboard
        Paired: no
        Bonded: no
        Trusted: yes
        Blocked: no
        Connected: yes
        WakeAllowed: yes
        LegacyPairing: no

When I try and pair the keyboard to my Windows and Android devices, it connects immediately with no pin required.

It says "LegacyPairing: no" - so, maybe this approach is entirely the wrong...

Thanks so much in advance, and if I can provide any more info just ask!

hope you all have a great day 🙂

#

When I look in All Hardware there were 3 unknown EventX IDs but none are labelled like the other connected devices.

I added an entry to my configuration.yaml for each one but nothing triggers an event, even when the keyboard is showing as connected when you run the "info" command.