# Time Display Trigger

**URL:** <https://forum.hamalert.org/t/time-display-trigger/1580>\
**Category:** Support\
**Tags:** done\
**Created:** [July 7, 2025, 1:00pm UTC](https://forum.hamalert.org/t/time-display-trigger/1580 "2025-07-07T13:00:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![KD5SMF](https://forum.hamalert.org/user_avatar/forum.hamalert.org/kd5smf/32/324_2.png) [@KD5SMF](https://forum.hamalert.org/u/KD5SMF)\
**Post date:** [July 7, 2025, 1:00pm UTC](https://forum.hamalert.org/t/time-display-trigger/1580/1 "2025-07-07T13:00:33Z")

</div>

UCT Time format is, and always has been 24 hour format. Why then does the “triggers” time clock only display 00:00 to 12:00 when setting up for alerts?  
The app properly displays it however, when setting up the time triggers it does not here on the web site. This is confusing especially when your trying to catch a special event station, or DX entity.

---

<div class="post-metadata">

**Author:** ![HB9DQM](https://forum.hamalert.org/user_avatar/forum.hamalert.org/hb9dqm/32/5_2.png) [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)\
**Post date:** [July 8, 2025, 8:01am UTC](https://forum.hamalert.org/t/time-display-trigger/1580/2 "2025-07-08T08:01:40Z")

</div>

> [@KD5SMF](#):
>
> The app properly displays it however, when setting up the time triggers it does not here on the web site.

That is because HTML time input fields depend on the system locale – on my systems set to use a 24 hour clock, it works properly. Guess I should replace them with plain text fields so they work the same regardless of how the user’s computer is configured.

I’ve created an issue on GitHub:

> <https://github.com/hamalert/hamalert-web/issues/5>
>
> Time input fields are problematic when entering UTC times, as they may appear as… AM/PM if the browser's locale is set to use 12-hour mode, and there is no way to override that in the application. So it is probably better to replace them with plain text fields (with input validation) so they work the same regardless of browser locale.

See also:

> [@Time inconsistencies](https://forum.hamalert.org/t/time-inconsistencies/498):
>
> Tried to set up a certain time to monitor some specific calls or areas. It seemed to promote “AM” and “PM”, but yet specifies Zulu time. Only when I exited out did it show Zulu. Might it be better to keep Zulu consistent throughout as the AM/ PM is confusing and not correlating with Zulu anyway?

> [@TIme and Day of the week filters](https://forum.hamalert.org/t/time-and-day-of-the-week-filters/1304):
>
> Hi. Time filter set form 2200 - 0700 (should ditch the AM / PM thing when setting the time and make it 24 hour for UTC) Day of the week set to Saturday and Sunday. What I’d like to know is - does the day of the week activate on the start of the filter time or the end of the filter time? Or will this get ugly crossing over 0000 UTC?

---

<div class="post-metadata">

**Author:** ![OH2BUA](https://forum.hamalert.org/letter_avatar_proxy/v4/letter/o/bcef8e/32.png) [@OH2BUA](https://forum.hamalert.org/u/OH2BUA)\
**Post date:** [July 10, 2025, 7:06am UTC](https://forum.hamalert.org/t/time-display-trigger/1580/3 "2025-07-10T07:06:39Z")

</div>

Hi,

my system locale in Win11 is 24-hours time. All regional things are set to Finland / metric.

Win OS language is english, as well as my Firefox is in english.

I very rarely face that AM/PM-thing. In HamAlert, yes.

73, Jukka

---

<div class="post-metadata">

**Author:** ![HB9DQM](https://forum.hamalert.org/user_avatar/forum.hamalert.org/hb9dqm/32/5_2.png) [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)\
**Post date:** [July 13, 2025, 8:01am UTC](https://forum.hamalert.org/t/time-display-trigger/1580/4 "2025-07-13T08:01:18Z")

</div>

This has now been fixed.