Alarm clock not triggered at 00:00

Milan Šádek

Even more strange situation. My alarms are set to 0:00 and 6:30, both only workdays.

At midnight it was not trigerred, however at 00:08 there is still 0:00 given on my watchface as the next set alarm - this is wrong, since that time there should be 6:30 shown in the complication.

A few seconds after taking this photo the time shown in the complication changed to the following set alarm, which is expected behaviour.

Now there are no alarms on my watchface now, which is correct (TGIF).

@isazi What else can I do, please, so that this problem is officially reported and worked on?

Thank you for your support.
MIlan

isazi

@Milan-Šádek this is just refreshing, in do not disturb mode the MIP screen and complications are refreshed less often, so values can be wrong if you do not press a button and wake up the screen.

Milan Šádek

@isazi ok, complication not updated is perfectly understood, but the main point for me is the alarm which does not work at midnight. Can you please help me with this topic?

elbee

@Milan-Šádek

I can confirm that alarms set for 00:00 will not trigger. Definitely a bug.

isazi

@elbee Is it always the case? I will test tonight and report to Suunto

isazi

@Milan-Šádek give me all details: new alarm? Old alarm? Once, weekdays, weekend?

Milan Šádek

@isazi I’ve already tested all possible combinations with the same result, there’s no midnight alarm at all

isazi

@Milan-Šádek tested, and reported it to Suunto.

Milan Šádek

@isazi thank you for your support.

Milan Šádek

@isazi I tested the latest official V1 firmware last night and the alarm did not trigger at 00:00.

Is there an estimated timeline for correcting this bug?

While the sports features are important, a reliable alarm clock is a critical function for a watch, and essential at least for my use.

sartoric

@Milan-Šádek
Sure, but it’s not a blocking issue since it’s pretty easy to workaround it.

2b2bff

@Milan-Šádek my guess is, that 00:00 is the same or similar to “not set”.
Just use 23:59 or 00:01.

VoiGAS

@2b2bff But not everyone who uses a Suunto watch is in this forum. So if one doesn’t know and relies on the watches alarm clock it could result in a missed flight… that should be reason enough for a bugfix as it seems easy to fix

maszop

@2b2bff The alarm clock feature shouldn’t be such a programming challenge by the end of 2025 that we’d need to resort to such workarounds.

This whole Suunto alarm issue (and lack of basic improvement), which has been going on for years, is reminiscent of a cabaret show.

Milan Šádek

@sartoric correct, but you have to make the experience that it does not work - which means you do not get your pill, but you can also miss your flight. This may be very costy. Not to mention, what if it does not work also at 01:24 am? You lack confidence in the watch.
The behaviour has changed with the latest fw - if set to once with the previous fw, it was not triggered but was deactivated after midnight, whereas now it keeps midnight alarm active forever. So it has gon from bad to worse

Dimitrios Kanellopoulos

@Milan-Šádek fixed on next updates

sartoric

@Milan-Šádek said in Alarm clock not triggered at 00:00:

what if it does not work also at 01:24 am? You lack confidence in the watch.

This would be a different issue and a different situation.

The fact that the alarm will ring at 00:01 instead of 00:00 is that sensible for taking medications or waking up ? I don’t think so.

Not to mention that, as I said, this is JUST a workaround, for sure the alarm must work as expected.

Milan Šádek

@sartoric you however work with the wrong assumption you already know about this bug. The point is that having the alarm clock set to midnight is not standard for the vast majority of users. I dare say every single user will encounter this failure.

As soon as you know, you set 23:59 or 00:01, which works.

In all sincerity, would you use those awkward times if I had not brought this flaw to your attention in this forum?

sartoric

@sartoric said in Alarm clock not triggered at 00:00:

Not to mention that, as I said, this is JUST a workaround, for sure the alarm must work as expected.