Clock timezone bug
Hey guys!
I've been using Homarr for a few months now and everything is going well.
However, I was trying to add a small area with different clock timezones and their weather.
As you can see, the weather widget appears to be working properly. Displaying the the information for the correct timezone.
But for the clocks, they are only displaying the local time no matter how I try to change it.
I tried looking for "homarr clock timezone" bugs but couldnt find anything.
Is there anything I can do to fix this?
14 Replies
Hi, thanks for the report. Can you create an issue for this on GitHub and we'll take care and fix it. Thanks 👍
FYI @Tag
Alright
GitHub
Clock timezone bug · Issue #1514 · ajnart/homarr
Environment Docker Version 0.13.4 Describe the problem Hey guys! I was trying to add a small area with different clock timezones and their weather. As you can see, the weather widget appears to be ...
Yes, thank you
There already are some changes on it in dev iirc, would be good to know if that issue persists there
@Lu Xi Phơ Could you show me the settings of one of the clocks?
here ya go
I'm trying real hard to replicate but the only time it happens to me, is when I leave the page open for 5h or more and a quick refresh makes it all go away
(I did find how to fix the timezone named offset showing as "z" though, that was also a bug)
Have you tried clearing homarr's cache?
yep i did its still hapening
im on the latest version:0.13.4 if it helps
Like I said earlier, there might be some changes brought in the dev version and what will be 0.14, like switching API to a lightweight version and switching to dayjs instead of moment. Those 2 changes might fix it for you.
As of right now I'd suggest, either you try homarr:dev of wait for 0.14, just to check if the issue persists
alright thanks for your help. ill just wait for the next update. looks like its a major one. looking forward to it
I also saw the error on dev @Tag , check out the public version it still happens
Can you try to replicate on the public demo I posted in #🦞・general ?
tried to replicate on the demo
it's working though
I just added an
await in the tRPC procedure, it should be better now