-
Notifications
You must be signed in to change notification settings - Fork 21
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
Synchronisation gets stuck - rare occurance defect 240704 1706 #2087
Comments
@DG12 is your measurement sequence number high on this particular sensor? There is a known situation where sync may get stuck when there is a significant number of measurements in memory, and this is handled on firmware side. |
Measurement sequence number is not directly related to amount of history data stored in the sensor. The number counter rotates every ~2 days back to zero. |
Measurement sequence number now 24651,2,3... (What Lauri meant was the the MSN wraps after 65,535. The number of days depends on the sensor update frequency. Since the app only permits 10 days worth, I expect that the app only attempts to retrieve 10 days worth regardless of how much is in the sensor. |
Currently the tag syncs without problem.' Export , oldest entry is from 2024-07-21 22:59:16 (exactly 10 days ago) containing only temp, hum, pressure(as expected) every 5minutes 2,870 entries. Then entries from recent advertisements. Sync did not get stuck this time. |
I am somehow able to get the sync to fail on this specific sensor. The experience is different fro DG though, because mine is always able to start. My sensor is somehow exactly -63 dBm now during sync and seems responsive and perfectly readable. Measurement sequence number is 61955 Tested with 2 iPhones Sensor FW is 3.31.1 default sync_bluetooth.MP4Edit: I can see this issue of slowing down to read measurements from memory is similar on Android device, but sync never fails. |
Hmmm now I think I got this issue replicated BUT it started on Android. Steps on Android:
Steps on iOS: After Android test is completed, try to sync on iOS:
This issue is not consistent, sometimes it appears to get stuck, sometimes it continues to download. |
I think this is not major issue and it's considered rare occurrence. I am however thinking... is this a library issue or actually a firmware issue? @priyonto |
I will have to wait until Bluetooth tests are completed on another card before returning to this. |
Reproduced this scenario. He starts sync by going to history view page, rejects connecting to sensor. RPReplay_Final1725419119.movThe synchronizing status is still displayed even user minimised app and then brought it back to foreground. RPReplay_Final1725419491.mov |
All these eventually timed-out. 3B86 nearby. fast to 330, thern slow the very fast. Completed RSSI -65 E6E0 slow, fast, slow, veryfast complete 2,044. RSSI -79,-,-76,-,-92,-,-84,- |
Seems to have connected but got stuck before first synchronization
The text was updated successfully, but these errors were encountered: