But why? Makes absolutely 0 sense to force a local encryption on a home usage system.
6 Likes
You can make unencrypted full or partial backups through yaml automations, scheduling them when you want, and sending them to the location of choice, same as always. This can be scheduled at any time like turning on a light. No add-on needed unless you want to send it to a cloud target. Those add-ons still work using the same methods.
Though I do notice a bug where the location option is not showing when switching to yaml mode, UI mode would seem āeasy for newbiesā
6 Likes
same here with HACS. HACS itself disappeared from the left menu, after reloading it is back, but all (or at least most) Hacs integrations are no longer working. Need to re-download all of them, but some are now missing.
Seems like a somewhat messy update.
1 Like
I had the HACS errors, but got over those, but after a while I have lost the developer and settings/system views. Tried reboot via the terminal, but that did not recover.
SmartIR fail after upgrade to HA core 2025.1 - i get error: Cannot import name āHVAC_MODE_OFFā
Hi,
after upgrade to HA core 2025.1 all smartIR integration started appearing errors as describe below.
i did update to smartIR from 1.17.9 to 1.17.12 but itās didnāt help.
Can U pls help ?
Configuration warnings
Platform error āclimateā from integration āsmartirā - cannot import name āHVAC_MODE_OFFā from āhomeassistant.components.climate.constā (/usr/src/homeassistant/homeassistant/components/climate/const.py)
Platform error āclimateā from integration āsmartirā - cannot import name āHVAC_MODE_OFFā from āhomeassistant.components.climate.constā (/usr/src/homeassistant/homeassistant/components/climate/const.py)
Platform error āclimateā from integration āsmartirā - cannot import name āHVAC_MODE_OFFā from āhomeassistant.components.climate.constā (/usr/src/homeassistant/homeassistant/components/climate/const.py)
Platform error āclimateā from integration āsmartirā - cannot import name āHVAC_MODE_OFFā from āhomeassistant.components.climate.constā (/usr/src/homeassistant/homeassistant/components/climate/const.py)
i also open a discussions in the git page:
They donāt mention this important thinkā¦ who know why ???
I created a bkp folder in my NAS and itās work 
Thanks a lot.
Does the backup retention work correctly?
For me it is only keeping 1 online backup, no matter what I set it to.
I started it manually several times, because the automatic backup failed this morning without giving a reason in the log. However after every backup only the latest one is available online.
Also the notification for the failed backup could not be ignored and only went away after a Home Assistant restart.
Skipping. The forced encryption via the UI is a no go for me.
1 Like
There is max 1 cloud backup. Which seems odd considering the 5GB allocated.
That being said, here the same āresultā a failed upload to the cloud at 4.45. Could it be the forced time is the issue? Simply too many in the CET time zone all at once?
2 Likes
HACS itself failing is not a general problem. I still have HACS working, still in the left menu bar and all costum integrations intact. I had the Miele integration chatting in the log about deprecated values and that was fixed within 1 day. It must be a specific costum component that triggered your problem
Or maybe they are still using HACS v1?
2 Likes
Yeah, me to @madbrain! I just tried this new Back Up feature and Iām totally confused. Just like you, I simply wanted to do a MANUAL backup like I always do and had to wade through all of these menus setting up automated backups, until at the end when I was able to turn off auto-backup and do a manual.
However, in the backups list now in Settings > System > Backups in the show all backups, it didnāt appearā¦ until I discovered there was a hidden filter for Automatic that wasnāt checked, which is exactly WHERE my MANUAL backup was! I chose to store it both locally and in the cloud, because why not.
Also, I always NAMED my manual backups so I knew what they were, but apparently thatās no longer possible (that sucks). Also, even though I only have 9 backup files on my HA system disk going back to July 2024, the UI is showing me 22 entries (including the new Automated Backup) going back to Jan 2024.
In the past, my Backup Management was that I backed up every time I updated something, before and after, and then copied them from my HA drive to another computer via Samba. I kept only a handful on my HA drive to keep the storage clean. I have no idea WHY the Backup UI is now showing I have 22, when there are only 9 on the disk. Previously, whenever I deleted old backups from the HA drive, the list in the old UI would immediately update with the correct files.
Iām glad this is a āwork in progressā. Things Iād like to see (and perhaps Iām missing something):
(1) Easier method of doing MANUAL backups with less confusion
(2) A way to NAME your MANUAL backups
(3) Consistency in what the UI is reporting and what is on disk in terms of actual backup files (perhaps this new method stores files differently, and we no longer have access to them, which would be BAD for my use, but MANUAL means should be maintained for those of us who prefer it). My system changes rarely, and on-demand. I donāt require nightly backups, or even automated ones.
(4) That these comments arenāt just wasted breath (which is why I quit beta testing).
If I have totally missed the old, easy manual backup method somewhere, please enlighten me.
EDIT: I just tried to delete some of the older files the UI lists and get a āFailed to delete backups - Unknown errorā error. So, I guess they arenāt really there, just a zombie. Great. Iām quickly losing confidence in my backup routine.
4 Likes
Admittedly, I saw this trend over a year ago, and started losing interest in HA as a result. I keep up with updates, but donāt mess with my setup much anymore. I set up my HA mostly in 2020 and it was hard as I was new to home automation. I STILL use YAML for all of my automations and scripts because of what you canāt do in the UI, AND because I comment the hell out of mine and you canāt do that in the UI, and Iād never remember why I did whatever I did. Designing for the lowest common denominator is never a good plan. But if itās all about getting more users, then thatās what organizations usually do. I hoped those in charge would see the value in the power user.
11 Likes
I had the same problem. Removed and added HACS again. After that I had to download all integrations and cards again. For some I had to add the custom repositories again, before I could download.
Now all works as before, but this 2025.1 update was a shitty one. Would expect better quality control by the developers.
Waitā¦ are you saying that with the new backup system, even if manual and local, that I canāt get into it to parse out individual files, but my only option being a full restore? If thatās the case, then I may revert and never go beyond 2024! Thatās ridiculous!
Please tell me Iām wrong.
EDIT: I just successfully reverted to 2024.12.5. Iāll wait to see how this sorts out. It appears Iām not the only one unhappy atm.
6 Likes
Iām another one here.
Oh, itās small all right, 0 bytes when my NAS is asleep :).
Itās got dozens of terabytes of free space, though, while each HAOS backup is only about 1GB, so minimizing the backup size is not an important goal for me. Minimum the power consumption from the NAS, as well as the noise from the platter based hard disks when Iām in the room, is more important, and that is why I use autosuspend on Ubuntu and WOL on clients that need to access the NAS.
Of course, I could switch every single client to backup at 4:45am instead of the current 2am, but I feel like the flexibility to choose a different time should be there, as it is in Samba backup.
3 Likes
Feedback taken. Interesting
4 Likes