You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 21, 2020. It is now read-only.
To repeat: I'm using a Primo and I'm transmitting temperature measurement characteristic values as indications. Consistently however, the first few calls to setValue return true, the client receives and ACKs the indication and I see the packets in flight. After a few successes (7 in my most recent test) however, setValue starts to return false and does not return to true responses unless I disconnect and reconnect.
Examples:
Protocol analyser showing 7 indications sent and ACKed
Serial monitor tracing indication values and API responses:
What could be causing indications to stop and is there a recommended way of getting to the root cause?
I wasn't sure which repo to log this against. I've logged the same issue against the BLEPeripheral API here:
sandeepmistry/arduino-BLEPeripheral#204
To repeat: I'm using a Primo and I'm transmitting temperature measurement characteristic values as indications. Consistently however, the first few calls to setValue return true, the client receives and ACKs the indication and I see the packets in flight. After a few successes (7 in my most recent test) however, setValue starts to return false and does not return to true responses unless I disconnect and reconnect.
Examples:
Protocol analyser showing 7 indications sent and ACKed
Serial monitor tracing indication values and API responses:
What could be causing indications to stop and is there a recommended way of getting to the root cause?