question about the bluez AcquireNotify code

[Raupinger]

I'm using @vovagorodok's ArduinoBleOTA Library, and I'm having issues with the upload script stalling on its start_notify call. Quick question as I try to figure out if this is an upstream or downstream bug:
stepping to line 946 here:

bleak/bleak/backends/bluezdbus/client.py

Lines 938 to 948 in 78d5699

	use_notify_acquire = (
	not force_use_start_notify and "NotifyAcquired" in characteristic.obj[1]
	)
	logger.debug(
	'using "%s" for notifications on characteristic %d',
	"AcquireNotify" if use_notify_acquire else "StartNotify",
	characteristic.handle,
	)
	if use_notify_acquire:
	reply = await self._bus.call(
	Message(

I get this for characteristic.obj[1]:

{'Handle': 96,
 'UUID': 'dac89266-35a1-11ef-aba2-0f0127bce478',
 'Service': '/org/bluez/hci0/dev_F8_B3_B7_47_75_CA/service005d',
 'Value': b'',
 'Notifying': False,
 'Flags': ['read', 'notify'],
 'NotifyAcquired': False,
 'MTU': 242}

but use_notify_acquire ends up being True.
Is that intentional?

[dlech]

It would be helpful to see a Bluetooth packet capture to see if this is similar to some recent issues reported.

If it is, I think we may want to reconsider the default behavior in Bleak. And also fix it in BlueZ.