It looks like there is a bug in how Amazfit/Intervals.icu handle HRV data syncing. While sleep score and resting heart rate are correctly assigned to their respective days, the HRV values are consistently written to the previous day. If you have not synced for multiple days, all HRV entries are incorrectly written to Day-1, overwriting the original data.
I am using the Amazfit T-Rex 3 and Zepp app. In the first image, the calendar shows two unsynced days. After syncing today (as shown in the second image), the HRV value for 18 September is missing because it was logged under September 17. Similarly, the HRV data for 17 September was pushed to 16 September, replacing the original value. The original value for 16 September is lost unless you manually rewrite everything using data from your Zepp app.
I am also experiencing issues or inconsistencies with the synchronization of HRV values from Amazfit/Zepp. Most days are transferred correctly, but recently, on some days, an HRV value that is far too low was transferred. When I try to overwrite this value manually, it gets overwritten again by the app/system.
That can be avoided by ‘locking’ the wellness data.
Is that low value also on Amazfit? If not, there must be some other connection sending spurious HRV results.
Well, I thought locking just Day-1 and Day-2 would be enough to keep things sane. Turns out, unless you lock every single day, the sync gods get angry. I did a partial lock, synced, and voilà—my unlocked HRV data for July, August, and September got generously shuffled by one day.
I messaged Amazfit last week, but apparently silence is their preferred response format. But who does not love randomized health metrics, after all?
Thanks for the advice about locking the wellness-data. I have no other connection sending wellness-data.
As you can see ther are differences between Intervals and Zepp, some days are right, other not…:
Easiest way to resolve your situation is by downloading a wellness.csv, correcting it within a spreadsheet app and reupload.
Thanks for the suggestion, but it seems the issue runs deeper. Even after manually correcting an HRV value, it gets scrambled again the moment you hit refresh on your browser—unless every single day is fully locked. I am not entirely sure whether intervals.icu pulls fresh data each time the browser page is refreshed. If it does not, that might indicate an internal glitch rather than a syncing issue. @david
Yesterdays value (42ms), which was correctly synced, today shows (incorrect) 30ms while in Zepp there is still the correct value of 42ms.
This is basically how it works:
Manually corrected HRV values in unlocked days
You hit refresh button on your browser:
The values immediately got shifted by one day. To me it looks like an array indexing problem.
