[GH-ISSUE #1458] Dates and times all muddled #1028

New issue

Closed

opened 2026-05-07 00:29:42 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:29:42 +02:00

Owner

Originally created by @tarmacalastair on GitHub (Oct 4, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1458

Hello
🐞 Describe the bug

I'm still getting a problem with dates and times. I think the US is pretty much the only country in the world where dates are formatted mm/dd/yyyy. We in the UK use dd/mm/yyy as do most other countries. I would also personally prefer to use times in 24 hour format rather than AM/PM.

I first tried using the ntfy.sh website and got the results shown in the screenshot (in both the Android app and the website). But I can't see any option in the app or website to modify date or time formats. As you can see the header shows the date as dd/mm/yyy and the time in 24 hour format but later within the message the date is in American format and the time is in AM/PM format and is now showing 1 hour behind in GMT.

When I found this issue and https://github.com/binwiederhier/ntfy/issues/475 I thought I'd try setting up ntfy in Docker so I could specify the TZ variable but I get exactly the same issues.

ntfy does now seem to honour the TZ variable in the header of each message but now the date and time formats don't seem to be consistent within the same message - see screenshot and notes above.

Thanks.

💻 Components impacted

So it seems that there is a problem in both the web and app version, using a self-hosted server or https://ntfy.sh

💡 Screenshots and/or logs

🔮 Additional context

I am using ntfy to get messages from my duplistatus docker stack. I have set the TZ variable in both stacks to Europe/London.

Originally created by @tarmacalastair on GitHub (Oct 4, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1458 Hello :lady_beetle: **Describe the bug**  I'm still getting a problem with dates and times. I think the US is pretty much the only country in the world where dates are formatted mm/dd/yyyy. We in the UK use dd/mm/yyy as do most other countries. I would also personally prefer to use times in 24 hour format rather than AM/PM. I first tried using the ntfy.sh website and got the results shown in the screenshot (in both the Android app and the website). But I can't see any option in the app or website to modify date or time formats. As you can see the header shows the date as dd/mm/yyy and the time in 24 hour format but later within the message the date is in American format and the time is in AM/PM format and is now showing 1 hour behind in GMT. When I found this [issue](https://github.com/binwiederhier/ntfy/issues/700) and https://github.com/binwiederhier/ntfy/issues/475 I thought I'd try setting up ntfy in Docker so I could specify the TZ variable but I get exactly the same issues. ntfy does now seem to honour the TZ variable in the header of each message but now the date and time formats don't seem to be consistent within the same message - see screenshot and notes above. Thanks. :computer: **Components impacted**  So it seems that there is a problem in both the web and app version, using a self-hosted server or https://ntfy.sh :bulb: **Screenshots and/or logs**  <img width="720" height="1600" alt="Image" src="https://github.com/user-attachments/assets/2cc878ee-452d-4f6a-a13c-421ebb1808ee" /> :crystal_ball: **Additional context**  I am using ntfy to get messages from my duplistatus docker stack. I have set the TZ variable in both stacks to Europe/London.

BreizhHardware

2026-05-07 00:29:42 +02:00

closed this issue
added the
🪲 bug
label

BreizhHardware commented

2026-05-07 00:29:43 +02:00

Author

Owner

@luneth commented on GitHub (Oct 5, 2025):

Ntfy is using the correct local, as shown in the top left corner of each notification.
Your issue is in the messages themselves, which is probably a configuration issue the software your running (duplistatus) or the host running it?
Are you positive duplistatus has the tz environment correctly set up?

@luneth commented on GitHub (Oct 5, 2025): Ntfy is using the correct local, as shown in the top left corner of each notification. Your issue is in the messages themselves, which is probably a configuration issue the software your running (duplistatus) or the host running it? Are you positive duplistatus has the tz environment correctly set up?

BreizhHardware commented

2026-05-07 00:29:43 +02:00

Author

Owner

@tarmacalastair commented on GitHub (Oct 6, 2025):

Ah thanks. I had used quotes around Europe/London in my compose file which I confirmed by execing into the container, was not working. I have now corrected this and the time within ntfy messages now shows in the correct TZ (GMT+!) but is still showing as AM/PM and the date is still showing in US mm/dd/yyy format.

I'll post an issue with the other project as I notice the screenshots there seem to show the dates in European format and the times in 24 format.

Many thanks

@tarmacalastair commented on GitHub (Oct 6, 2025): Ah thanks. I had used quotes around Europe/London in my compose file which I confirmed by execing into the container, was not working. I have now corrected this and the time within ntfy messages now shows in the correct TZ (GMT+!) but is still showing as AM/PM and the date is still showing in US mm/dd/yyy format. I'll post an issue with the other project as I notice [the screenshots](https://github.com/wsj-br/duplistatus/blob/master/docs/img/screen-overdue-notification.png) there seem to show the dates in European format and the times in 24 format. Many thanks