David Lechner

> You could also research the "Unreachable" error in relation to Windows Bluetooth Low Energy and see if that gives any hints. Not sure if it is helpful, but this...

I'm not sure it will fix the issues here, but could you please try #680 to see if it makes a difference?

> 2022-07-13 15:53:26.377 14122-14150/org.test.tesi4 I/python: bleak.exc.BleakError: Characteristic with UUID 00002a9d-0000-1000-8000-00805f9b34fb could not be found! Either there is a bug with characteristic discovery, the android os hides this characteristic or the...

You could try `print(client.services.characteristics)` just before `await client.start_notify(...)` to see what characteristics have been discovered.

> 2022-07-13 18:12:41.390 21906-21935/org.test.tesi6 I/python: {0: } This shows there is only one characteristic with handle `0` which doesn't seem right. I think we assumed that `getInstanceId()` returned the handle,...

The bug in Bleak needs to be fixed. All characteristics in the dictionary are using the same key which writes over the previous key, so only the last discovered characteristic...

In #888, we discussed relaxing the `int` requirement on the handle property. I think it would be more straight-forward to make the "handle" on Android a tuple of the UUID...

I have pushed a new commit to the `dbus-next-2` branch that should improve the logging to see how we get here in the first place - or it may avoid...

Can you enable debug logging so that we can see the sequence of events that lead up to this?

@stuartlynne do you have a minimal reproducible test case? Is it possible that the D-Bus server or BlueZ (bluetoothd) was restarted while your Python program was running?