David Lechner
David Lechner
I would just make the timeout shorter or add an advertisement filter to avoid trying to connect to the problematic device in the first place. You could try to put...
It was too long between the scan and the connect and the device went to sleep or something like that.
Is this still a problem with Bleak v0.22.0?
Which version of Bleak are you using? Is it still a problem if you use the `develop` branch? Can you share any logs?
Tip: `details` is an internal OS-specific implementation and may change without notice. Use `BleakScanner.discover(..., return_adv=True)` instead. Without logs, we can't see if the device is just not sending the UUID...
Right, `BleakScanner` only received advertisement data which may or may not include any services UUIDs depending on how the device is configured. You have to actually connect to the device...
Again, without logs, we cannot know what is actually happening.
The OS Bluetooth stacks handle this on the central side so Bleak can't really do anything about it. So if you have control over the peripheral firmware, you will need...
No, this is not possible with BlueZ. Since it doesn't conform to the Bluetooth specifications, it is not going to work universally.
Without seeing the actual data, I can't say for sure, but manufacturer data should always have a valid manufacturer id as the first two bytes.