Hello,
I'm currently using C-8 version 2.3.9.158, and I've noticed that the hub date format is now locked to the US-centric MM/DD/YY date format, not adjusting to my timezone or browser date format settings.
Could you please add this defect to your backlog?
Thank you.
This seems to be crazy...surely we should be able to SIMPLY change the date format in Hubitat?
I'm not sure if that last one is actually a date format thing.... That doesn't really with any kind of variation I could think of to arrive at that time displayed in the rule...
Is there somewhere you are seeing the same issue?
Yes, not being able to change the date format is slightly annoying.
Hubitat devs are lazy - easy enough to auto format based on location setting or to provide a date format adjustment setting.
Now we wait ...
…patiently😔. Is seems such a fundamental requirement. There is so much power in a small box, but we have problems defining the system date. Hey Ho.
You guys have an odd way of asking for something to be fixed, particularly something so small. The date format isn't something that normally bothers me as much...
That's probably because you American - 10/05/25 and 05/10/25 means very different things outside the US.
It means something different to me as well. Being just North of Sydney...
You get used to it after a while working with IT systems....
But I've probably been a bit too negative myself in my responses... I get that it is something worth fixing... I just think we could be a little more diplomatic in asking for something to be fixed.
Thanks, Simon.
As an IT Architect, I find the use of non-localised date formats to be a poor user experience—it comes across as careless and unrefined.
If you refer back to my original post nearly a year ago, you'll see it received no response, no acknowledgement, and no action was taken.
While I don't find it quite as annoying, I am with you in hoping to see it fixed sometime soon. I am willing to cut the small dev team some slack given what they have delivered in the period since your original post (matter? and the updated UI in particular).
I'll also acknowledge I have taken this conversation away from the original intent, on a less useful tangent, apologies.
No stress mate - I love Hubitat and I have supported them for many years. Their product and community support is great, but they seem to be losing contact with their users. I used to see founders like Bruce Ravenel @bravenel directly engaged in customer feedback.
Now we wait ...
The issue, as near as I can tell, is that there isn’t a global location currently to store a preferred date format. Given that, no allowance was made in the base code to provide date format as a consideration and to retrofit it now would be a large undertaking, and thus the reason many developers add the option to format the displayed date inside their code.
Might I ask where you find this display to be personally egregious?
I raised the issue a year ago because every system and app I use does this by default, except for Hubitat.
Adapting time zone display to regional settings is straightforward - Java Intl.DateTimeFormat or Groovey "java.time.format.DateTimeFormatter", etc provides this as a simple call - no large undertaking required.
Oh it's easy enough, just a lot of places to apply it and then do you base it on lat/long, timezones, or.... And again without a place to store the user's preference every developer is guessing (If they care at all) - I personally like yyyymmdd. It's a nit.
Well, I'm certainly really motivated now to help you out. RM does allow you to set the date format:
Hubitat devs are anything but lazy -- but we do have priorities, and date formatting isn't on the list.
So you’re asking for a fix for something and then insult the devs? Not a smart way to go about things. Can’t blame the devs for not making this a priority at this point.
Thanks Bruce 
Download the Hubitat app
