Skip to content
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

Open
DG12 opened this issue Jul 18, 2024 · 10 comments
Open

Synchronisation gets stuck - rare occurance defect 240704 1706 #2087

DG12 opened this issue Jul 18, 2024 · 10 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@DG12
Copy link
Contributor

DG12 commented Jul 18, 2024

Seems to have connected but got stuck before first synchronization

image

@markoaamunkajo
Copy link
Collaborator

@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.

@markoaamunkajo markoaamunkajo self-assigned this Jul 30, 2024
@laurijamsa
Copy link
Member

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.

@DG12
Copy link
Contributor Author

DG12 commented Aug 1, 2024

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.

@DG12
Copy link
Contributor Author

DG12 commented Aug 1, 2024

Currently the tag syncs without problem.'
I just deleted ruuvi station and data. Installed version 240730 20219. Added ONLY sensor 3B86.
by the time I did the export there are 30 entries averaging 3seconds apart.
Now sync,without problems something like 2,8xx entries?

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.
Sync again no problem.
dBm -60.
Relocate sensor, dBm -63 sync no problem.
Sensor has not been reset!

@markoaamunkajo
Copy link
Collaborator

markoaamunkajo commented Aug 15, 2024

I am somehow able to get the sync to fail on this specific sensor.
The memory is being read slowly in certain area around 200-500, then it begins to read fast, but ends up with Download Failed message at the end.

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.
After syncing RSSI is -72 dBm.

Measurement sequence number is 61955
I am signed in and this specific sensor is claimed to my account
Disable Bluetooth is set to enabled

Tested with 2 iPhones
iPhone 14 Pro
iPhone SE

Sensor FW is 3.31.1 default

sync_bluetooth.MP4

Edit: I can see this issue of slowing down to read measurements from memory is similar on Android device, but sync never fails.

@markoaamunkajo
Copy link
Collaborator

markoaamunkajo commented Aug 15, 2024

Hmmm now I think I got this issue replicated BUT it started on Android.

Steps on Android:

  1. Right after sync is finished try to sync again
  2. Syncronizing... text is shown
  3. After a while Download failed popup is shown

Steps on iOS:

After Android test is completed, try to sync on iOS:

  1. Press sync button
  2. Synchronizing... text is shown
    3.After a while Download failed popup is shown

This issue is not consistent, sometimes it appears to get stuck, sometimes it continues to download.

@markoaamunkajo markoaamunkajo added the bug Something isn't working label Aug 15, 2024
@markoaamunkajo
Copy link
Collaborator

markoaamunkajo commented Aug 15, 2024

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

@markoaamunkajo
Copy link
Collaborator

I will have to wait until Bluetooth tests are completed on another card before returning to this.

@markoaamunkajo
Copy link
Collaborator

markoaamunkajo commented Sep 4, 2024

Reproduced this scenario.
User has signed in to Cloud and not disabled receiving Bluetooth messages.

He starts sync by going to history view page, rejects connecting to sensor.
His sensor is on the edge of Bluetooth signal range, first attempt results in an error.
Second time he moves closer to sensor and the process gets stuck at synchronizing status, timeout is missed.

RPReplay_Final1725419119.mov

The synchronizing status is still displayed even user minimised app and then brought it back to foreground.

RPReplay_Final1725419491.mov

@markoaamunkajo markoaamunkajo added this to the 2.13 milestone Sep 5, 2024
@DG12
Copy link
Contributor Author

DG12 commented Sep 6, 2024

All these eventually timed-out.
Just tried sync on 230E. Started very fast got to 244 and stopped.Eventually "Download failed" RSSI to iPhone is -93,-87,-907,,-89,-97,-91,-86... history has data every 4-5 seconds since 10:34:43. PS not show on station web. Average change in seq number 3.1 . No data 11:23:28 - 20:26:04 iPhone battery death :-) average RSSI -92.
Attempt #2 fast up to 334, stop, still receiving data as per 1,0,2,7 seconds ago.
Try again slow stop at 86 !
Last try fast, stop at 355.


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,-

@markoaamunkajo markoaamunkajo modified the milestones: 2.13, 2.14 Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants