Replies: 1 comment
-
The Android Bluetooth stack seems to be a bit more forgiving of misbehaving devices. Logging Bluetooth packets (see troubleshooting page in Bleak docs) is generally helpful in diagnosing these types of issues. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
bluetoothctl -v
) in case of Linux: unsureDescription
Using the example service_explorer.py does show the readable characteristics:
This is how I'm setting up my service/characteristics on the peripheral side:
and on the central side:
... and trying to read centrally using:
My custom script allows my central device (Mac) to originally establish a connection with the peripheral (nRF52DK), but it gets disconnected in about 2 seconds, after the await line above fails to run successfully.
Using the example uart_service.py also yields a momentary connection and disconnection within a couple seconds.
What I Did
Someone on the forum suggested that the Descriptor having a null value could be the issue. I'm very new to BLE, and I'm not sure how to set up the Descriptor on the code that I'm flashing to my peripheral, so right now I don't have any code related to that.
I did try to connect to my peripheral using the nRF Connect app on my iPhone. Doing this, I'm able to fully connect to my peripheral and continuously get the data sent over! I just want to replicate this on my computer using my bleak script.
Any advice would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions