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

[Rare minor bug] Fr255 can display wrong time in sleep monitoring during time reference change

StreetLight

During the passage between summer time and daylight saving time the watch monitored my sleep.

When I woke up the time of my awakening was correct, but the time of me falling asleep was still displayed using the old time reference. The asleep time was correctly calculated though. On garmin connect even the time of me falling asleep was correctly shifted.

So to be clearer the time went one hour back (eg from 3 am to 2 am) and the time of me falling asleep was 3.05 (which would have been 4.05 with the old reference) and was not shifted to 3.05 on the watch, but kept to 4.05. The awakening time was 8.58 (9.58 with old reference) and was correctly displayed on the watch. The sleep time was 5.39 and it is strangely correct. Garmin Connect displays 3.05, 8.58, 5.39, so all the data is correct there.

Just wanted to report this bug to the Garmin team, being this an hard to reproduce bug.

  • 0

    Not a bug to me, but how it is supposed to be.

  • 0 in reply to urednik

    But if Connect shows one time for the start of the sleep and the watch shows a different one, but they show the same time for the end of the sleep, one of the two has to be wrong XD.

    And the time reference change happened before the start of the sleep, so both the start and end times should be shown using the new reference time, so the right one is Garmin Connect, and the watch is showing wrong data.

  • 0 in reply to StreetLight

    So the watch did not update time shift at 3 but sometime later. Which is not a bug but rather a timezone exception.

    Watch dont get its time from software but from a center, which can be several hours delayed in a timezone (for example living in the EU, center being in NY).

    Does not really make sense to make them deal with that IMHO

  • 0 in reply to urednik

    The watch did use the garmin connect app to get the time (see https://support.garmin.com/en-US/?faq=z9ue29cdcD8SHu28Lo8VY5). In order to use the gps the watch has to connect to the satellites and it does this only if you either manually do it through the settings or if you start an activity, but not by itself, and I for sure did not do any of the two while I was sleeping (plus I was inside a building, so the watch could not connect to the satellites).

    Anyways how the time is acquired is not important in this situation because the watch, as you can see in the photos, calculated the sleep time in the correct way. That means the problem is not in the time acquiring process, because that one succeded perfectly. It knows that I slept from 3:05 to 8:58, it is just wrong in displaying the sleep start time.

    I think the problem is in how the watch manages the data in this situation through software. So it is not that difficult to fix this issue that has caused more than one problem, as you can find another post from today in this forum discussing a similar situation.

    By the way I'm not forcing them to deal with anything, I'm just making a bug report that they can use to improve their products in the future, if they want.

  • 0 in reply to StreetLight

    My Forerunner 255 Music changed to winter time without using GPS or connecting to WiFi or my phone. These were all disabled. It must be in the software of the watch.

  • 0 in reply to ovekvam

    Oh ok, even better.

    So, as I said in the previous post, the bug is in the handling of the time inside the watch.

    And it seems, in my case, that the problem is only in displaying the time because the sleep period was correctly calculated and this wouldn't happen if the watch really had not updated the sleep start time correctly.

    Instead, in the case of the other post in this forum, it seems that the problem there is a bit more convoluted, but we now  know that the watch changes the time internally without external inputs, so even there it should not be complicated to fix it.

    Probably, being a not so frequent event, Garmin hasn't done tests on this and the bug went unnoticed.

    Hopefully they will fix this in the future.

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries