-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wait notification functionality feature #1501
Comments
As a workaround, you could use an await event.wait()
await client.read_gatt_char(tx_char)
event.clear() |
As I see callback has |
Based on your example, I thought that maybe you had a case where the value was too large to fit in a notification and you had to do a read to get the full value. But if you just want to use the value from the notification and not read again, then you can use |
Thanks! I will use |
No concrete plans. But having something that could be used in an |
Should we close this issue or hold in order to track progress? |
I don't see any duplicate issues, so let's leave this one open. |
Will be nice to have functionality like
client.wait_for_notify()
in order to have possibility to write simple scripts of serial communication that works like:I have this issue in my ArduinoBleOTA library for firmware uploading over ble:
https://github.com/vovagorodok/ArduinoBleOTA/blob/7fb9e079cf54e02b0701d117754e14ebe5db34cf/tools/uploader.py#L144
The text was updated successfully, but these errors were encountered: