not sure you noticed, there were exclusively European countries included in the discussion. Every such country has its own convention. Even on the official level (ie EU documents), there is no single standard enforced.
Speaking about the international format, you mean likely ISO 8601. But at first it’s YYYY-MM-DD format (so not widely used in Europe), at second, while it’s currently being implemented in Europe, it’s rather advice rather than real change. I’m not aware of date-time format changes in the countries I live.
…which is logical, as only european people are affected with “wrong” date format
Leading zero or not, most (if not all) EU countries use time, followed by day-month-year, while US uses reversed format…
But, since most important thing to look for is international compatibility and possible problems when not using it i guess current format is best to use.
EDIT: but then again, many other things are also reversed, say numbering: number 25: many EU countries say five and twenty, while US says twenty five.
I didn’t know only European counties where involved.
But it fixes the dateformat issue globally. And you can sort on alfabet and still get the correct order. Whenever doubting this format fixes a lot of isseus. Still. M$ for instance tries to ignore this format as much as possible.
I am not participating in the beta but it was important to me to also add my heartfelt thank you for you dealt with the community response.
I have read the beta release note a day ago and was impressed with how everything I had read in the blog thread was addressed. Thank you!
Same here with two addons. I haven’t installed the beta yet, so I tested it with Samba Backup because it doesn’t encrypt it. The data from addon_config is saved directly in the backup of the addon (config subfolder).
This has nothing to do with the new backup method introduced in 2025.1.0 .
All add-ons that exist like Samba Backup, Google Drive Backup and OneDrive Backup use the old scripts (that still exist) to make an unencrypted backup.
action: hassio.backup_full
I still run it daily to be sure I have a working backup during the betas, in case something is wrong. And they are still unencrypted if you don’t set a password, like with the add-ons.
The addon_configs was never included as a folder. If the add-ons are made properly the data should be included in the back-up of the add-on itself which is part of a Full backup or Partial backup where the Add-on is included.
You can check an unencrypted backup by opening the .tar and the .tar.gz inside of the specific add-on.
I just checked through the new method and opened a0d7b954_nginxproxymanager.tar.gz. The data from addon_configs is inside the config folder of this file.
ISO 8601 has been around for almost 40 years. I don’t understand why it hasn’t been more widely adopted. However, whatever the reason, there should be no question about using it for the purpose of this discussion.
I thnk it was already stated: unneeded warning appears when downloading unencrypted backup file, something like
decrypting is not supported for this backup copy. Downloaded backup will stay encrypted and won’t be possible to open it. You need a decryption key for restoring
(translated from local language).
Warning still shows on beta7. File can be easily opened, though (since it’s not encrypted).
Just a quick note to say thank you for this change. I was pretty furious about being forced to encrypt my local backups-to the point where I was ready to stop supporting the HA project financially. This is a welcome reversal!
Alright, everyone, that’s a wrap for this thread! Your feedback was incredibly helpful this past week - I am going to work on ensuring that there is a Beta thread here every month now to allow y’all who are not a member of the Discord server a chance to offer valuable insight.
If you have feedback about anything that was released in 2025.2, please head over to the blog thread specific for this release to continue the conversation.
One last note: THANK YOU. Thank you for your feedback, compliments on how this situation was handled, and everything in between. We seriously cannot do this without your input - please keep it coming and keep it healthy.
We seriously cannot do this without your input - please keep it coming and keep it healthy. 