Hello, I observe a strange behaviour of bluez dbus interface. I'm using Cinolink BT 4.0 USB Adapter (CSR BC8510 chipset), Bluez 5.43 on debian and/or on fedora. When I first pair a BLE device, the services are correctly discovered and the GATT endpoints are created (a lot). Then I can use it as expected and it is nice. But when I turn off the computer and restart it, things become different. Because the devices are paired with LT key, they are still paired but the GATT services are not availables. I can connect to the device but it doesn't declares the GATT properties/attributes that I need. Also, the service advertises itself without effect. To be able to restore the attributes, I need to first remove the device using bluetoothctl (CancelPair doesn't seems to work) and to pair a new time. Can you reproduce it? Is it the intended behaviour? How can I setup the system to have GATT properties+attributes present after an advertising? What dbus method should I call (ConnectService doesn't works)? Best regards José Bollo - Senior Software Engineer www.iot.bzh -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
