This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New Zealand Timezone Weight Upload Issue from Index

Former Member
Former Member
I am in New Zealand and using Index Smart Scale and weigh myself in the mornings. However, when my weight uploads from the Index it shows in Garmin Connect and the app as relating to the day before. If I weigh myself after 1pm in the afternoon it uploads to the correct date. I have 2 watches and have re-set both of them and all settings are correct for my timezone (Auckland) except for daylight saving which is not accounted for.

There is a similar issue with my Forerunner 235 in that I have a Training Plan in my calendar which looks fine in Garmin Connect but in my watch the Training Calemdar has Sunday's long run under 'today' and my next relative day in my calendar is Wednesday 8 March 2017 with the Intervals I need to do on Tuesday, I am always missing a day?

Someone else who is in Australia has the same problem with their weights (see Timezone Funkiness post)
  • I have the same issue with my weight ins. I only weigh in in the AM so can not confirm if I did this later in the day if it would work ok.
    I also noticed that with my run this morning I set a PR. when I logged into GC it said I did the PR 'yesterday' although when I clicked on it to look at it, it went to this mornings run.
    As you suggest there seems to be some wider TZ issues in the Garmin system currently.
    I did log a ticket yesterday with support around weigh in TZ issue. No response as yet
  • Timezone issues with custom workouts go way back to Garmin Training Centre. Workouts would always be offset by a day, likely because Garmin is America centric. It has been fixed and broken and fixed and broken...over time.
  • Same Issue here in Perth, WA Australia. (+8 GMT)

    I found if I put a dummy weight in for the actual day via garmin connect and then delete it, the correct weight from the day before will re-appear.
    Then if I weigh myself sometimes after doing the above the correct weight and other body metrics will go to the correct date.

    Not sure if this is because of the timezone or that it creates an entry for 'today' which is then overwritten with the correct data.
  • <Q#:1000109> << Reference ID: 9411186K0 >>

    Same issue being experienced here in South Australia +9:30

    I contacted Garmin Support (Reference ID 9411186K0) and they were no real help after I had already exhausted all possible troubleshooting that I could think of which included:

    1. Confirmed firmware is the latest version from February 23rd (when I actually thought the issue may have started)
    2. Reset scale twice back to factory settings
    3. Confirmed that timezone settings were correct for both my profile and my wife
    4. De-linked the scale from both of our profiles, and re-connected
    5. Rebooted Router (as our scale connects via Wi-Fi)
    6. Created a brand new Garmin Connect Account (to rule out any issue with my existing account - I've seen in the past sometimes where an upload is dodgy it will throw out other days)

    My scenario - if I weigh myself in the morning (around 6:30am CST) it will display on both the Garmin Connect site and Web app as the previous day. If I weigh myself again in the afternoon (around 14:00 CST) the weight will appear for the current day. When I weigh myself the next morning it would overwrite the data that was recorded from the afternoon (14:00 CST) and think that it is the previous day again.

    After advising the Garmin person of all of that they advised that there was nothing they could do and that the issue is most likely with the scale itself, they've suggested I request an RMA and then send the product back to Garmin (at my own cost) for repair or replacement. I was considering doing that given the scale is < 5 months old and purchased from Garmin directly, but now that there are other people impacted...maybe Gamin might actually investigate properly rather than fob me off?
  • Index Smart Scales

    I have the same problem. I live in Melbourne.

    It is so frustrating. I believe it happened when the latest update happened.
  • Per my previous comment I had logged a ticket and am still awaiting a clear response
    But here is a subsequent email I sent in noticing some further interesting discrepancies

    I just found some details that you may find interesting and hopefully helpful in troubleshooting this issue

    On the GCM app the weight displays out by 1 day as reported
    The same on the GC dashboard web page weight report I have configured on GC dashboard
    Interestingly when I have the calendar displaying full page in GC webpage view the weight icon shows a reading that is correct for the weigh in. From there you have no access to the other metrics (that would be handy . Perhaps in the future?) to confirm if it is fully valid but on surface it looks correct.
    So there seems like the calendar picks the weight input up ok but the app (GCM) and the report (GC dashboard) pick source info up differently.
  • Latest response to my ticket logged with Garmin Support given my above mail (in previous post) with some screen shots

    Thank you for your reply and all the information provided, this will definitely help our tier 2 who are liaising with our headquarters team in the US, we have had a few reports on this issue so they are working hard towards getting this resolved.
  • I'm in Melbourne and have the same issue.

    Also used to have it when my Withings scale data used to sync with GC via MFP. So this leads me to beleive this is aGC issue, not an Index Scale issue.
  • Hi
    Latest response to my above mentioned ticket open for a few weeks

    Below is today's response from Garmin support (I am in Australia) so will see in the morning

    There was a new version of Garmin Connect Web last night and HQ believe that this update will resolve the issue. It would be appreciated if you could please test this with the next weigh in and please let us know how you go.
  • hi
    following my previous post I have feedback that I have seen no change to "TZ error" since the reported update. they have fed this back to development team with the supporting screen shots