BlueZ: 5.55
Kernel: 5.10.100
While reading the services and characteristics of a BLE device, if there is a connection abort error or services could not be resolved, the device is removed for cache as per the application.
But during the next scan, the device is not at all seen in the device list.
When checked the btmon logs, the device seems to be present.
So, the BlueZ layer picks up the device but not node-bluez.
Request your inputs here.
BlueZ: 5.55
Kernel: 5.10.100
While reading the services and characteristics of a BLE device, if there is a connection abort error or services could not be resolved, the device is removed for cache as per the application.
But during the next scan, the device is not at all seen in the device list.
When checked the btmon logs, the device seems to be present.
So, the BlueZ layer picks up the device but not node-bluez.
Request your inputs here.