Related
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

Weight can be recorded only on today

6771900

I am experiencing a problem about weight record.

When I try to record a weight data some days back and put weight and date which is not today, the weight data overwrites today's weight, not on the date I specified.

I logged out and deleted all the cookies and caches of my browser, and then tried again. The problem still exists.

Does anyone have the same problem?

  • +1

    I have the same problem, from the browser if you change the date to a previous date and enter weight data it just overwrites for the current day.

    Only workaround I could find is to use the garmin connect mobile app.

    When you open that you get the dashboard, and on that page you have a widget for entering weight manually. Selecting previous dates and entering weight works as expected, and it shows up immediately on garmin connect web.

  • +1

    Yep, same here. Tried Safari and Chrome browsers on my Mac (running OS X 10.11), as well as Safari on my iPad (iOS 10.3), and Garmin Connect Web just completely ignores the date I have carefully selected for the weight record entry each time.

  • +1 in reply to 2161667

    Thank you for confirmation and workaround tip.

    Unfortunately, I do not have a mobile. I think I have to wait till fix is done.

  • +1 in reply to ASmugDill

    I look into data exchange between the browser and garmin server.

    It seems my data sent to the server is just right.

    {"value":58.9,"unitKey":"kg","date":"2019-08-03","dateTimestamp":"2019-08-06T22:02:13.393","gmtTimestamp":"2019-08-06T13:02:13.393"}

    This is the data when I wanted to add an old weight. "date" key has 2019-08-03 value, which is quite right.

    {"value":58.4,"unitKey":"kg","date":"2019-08-06","dateTimestamp":"2019-08-06T22:04:09.268","gmtTimestamp":"2019-08-06T13:04:09.268"}

    And this is the data of today. "date" key has 2019-08-06, which is also right.

    However, server program must take both of them as today's value.

    This has never happened before, at least some weeks before. Some code change of the server program has to do with it.

  • 0

    I think it is now fixed! Hope it won't be screwed ever again.