No bluetooth sink in pulseaudio

I try to connect my bluetooth headset via pulseaudio. I have followed the Bluetooth Speakers/Headphones guide.
I can connect the headset with bluetooth.

[Jabra CLIPPER]# info 70:F1:A1:62:59:D1
Device 70:F1:A1:62:59:D1 (public)
        Name: Jabra CLIPPER
        Alias: Jabra CLIPPER
        Class: 0x00240404
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)

But there is no sink available in pulseaudio. What have I missed?

root@OpenWrt:/# pactl list sinks
Sink #0
        State: SUSPENDED
        Name: auto_null
        Description: Dummy Output
        Driver: module-null-sink.c
        Sample Specification: s16le 2ch 44100Hz
        Channel Map: front-left,front-right
        Owner Module: 10
        Mute: no
        Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
                balance 0.00
        Base Volume: 65536 / 100% / 0.00 dB
        Monitor Source: auto_null.monitor
        Latency: 0 usec, configured 0 usec
                device.description = "Dummy Output"
                device.class = "abstract"
                device.icon_name = "audio-card"

System log:

Sat Feb 27 01:17:10 2021 bluetoothd[2929]: Endpoint registered: sender=:1.2 path=/MediaEndpoint/A2DPSource
Sat Feb 27 01:17:10 2021 bluetoothd[2929]: Endpoint registered: sender=:1.2 path=/MediaEndpoint/A2DPSink
Sat Feb 27 01:19:21 2021 daemon.err bluetoothd[2929]: Control: Refusing unexpected connect
Sat Feb 27 01:19:22 2021 kernel: [  172.856727] input: 70:F1:A1:62:59:D1 as /devices/virtual/input/input2

Not sure exactly how related this is but I notice that someone using Linux [not openwrt] indicated success even when that message is present, see

Also very strange, when I pair using bluetoothctl, bluetoothctl says pairing successful and "paired:yes", but about two seconds later, the bluetooth device (not bluetoothctl) says "ready to pair" again and bluetoothctl says "connected:no". If I connect before the said two seconds, the connection WORKS, but if I do it too late, it fails.
I have no idea why this is the case. Anyways journalctl shows this new line after the connection is successful, EVEN WHEN it is successful