After 2 great weeks with Sailfish on the Pro¹ the only inconvenience left for me is bluetooth support.

Connection to all my devices succeeds. But most are not fully working.

I do not really want to bother the porters team until i have some conclusion or at least checked the obvious.

Attached are the bluetoothctl output when connecting from cli and via settings UI to a pebble.

Output of the bluetoothctl -"show" -"list" -"find" commands and "rfkill list".

A zip of the HCI log during the failed connection attempt.

The pebble pairs correctly and connects for some seconds. Then gets disconnect with "Failed to connect: org.bluez.Error.NotAvailable" message in bluetoothctl.
During the short time of connection, rockpool can "see" the pebble. But regardless if rockpool runs or not, pebble gets disconnected.

The Sailfish UI shows the pebble is using DID protocol.

Any advice how to tackle this further?