Wrong date in Properties

[Pch]

The only format allowed in date and date/time keys in source mode is the ISO8601 one … which is then parsed in the format set at your device OS level by Properties in Live Preview and Reading …

So, date and date/time keys needs to be written as YYYY-MM-DD or YYYY-MM-DD[T]HH:mm to be parsed correctly by Properties, otherwise it can lead to some unexpected results, like what you’ve encountered here (the day part was parsed as the year and the first 2 digits of 2024 were taken as the day).

Edit: Here’s a post with a longer explanation about what’s happening with the “wrong date”: here

---

These could also be useful :

Properties: let the user customize the way Dates/Times are saved/written

This FR was created to capture the discussion related to letting the user choose in which format the dates of type “date & time” in properties are saved on file. Currently, we use ISO 8601, extended syntax, second resolution, local time. While the format chosen for the internal representation may be subject to minor changes in the future, we do not plan for having the users pick a different format. We would like to have fixed format to facilitate interoperability with outside software. If you…

Properties: let the user customize the way Dates/Times are displayed (independently from OS)

Mod-Note: This FR is specifically about customizing the way dates are displayed not the format they are written on file. Currently, the displayed format follows what you have chosen at OS-level. Use case or problem As far as I could see, how dates/times are displayed within Properties seems to be device dependent instead of just re-using the format from the YAML. My device was not set to use dates formatted as YYYY-MM-DD and I had to go and change these settings so Properties would actually …