I really appreciate the work that has been put into the new release and I understand the point of the MVP very well. I use HA for not that long now, but meanwhile I have 35 integrations (both official and from HACS) installed and everything works. After updating I got overwhelmed with error logs both for the built-in integrations as well as the community ones; so I quickly reverted back to the 2024 version without further analyzing.
Key aspect for me to be using the new version is availability of my integrations, since I have my house run by them. Fixing one or two of them comes with the open source approach, but not 50%. I am gonna come back, when availability is given.
I must agree with the criticism to the “forced” encryption approach as a design philosphy. Software should be made to make peoples live easier and not produce more hassle than necessary. People run HA locally for a reason; what is the security point in there?
please join in, it’s a major issue, as all cards using hui-generic-entity-row are affected, like
fold-entity-row,
template-entity-row,
multiple-entity-row,
input-text-entity-row,
text-divider-row
etc.
it’s so peculiar, that entities in a regular entities card are now no longer moddable like before, but the entities inside a fold-entity-row are…
to name but one change we are facing.
By the looks of it now, we are going to have to write dedicated mods for all different combinations in card and entities… which of course is a terrible experience. And no clue why this was done, or how. Must be some benefit in HA core Frontend for this, but even that is non disclosed.
Given the fact card-mod is not very well maintained and has a lot of open issues, I dont have high hopes we could see a fix for this in card-mod itself, so again, we’re on our own here.
Great backup stuff! However, I wanted to configure my backup NAS location which works fine, but I realized that at 4:45 my NAS is shutdown because I want so save the energy. Can we please have a configurable timer so I can run it at 7:15 in the morning?
Hi,
Just updated to 2025.1 (and now back to 2024.12.5) and it broke my Ecowitt integration. I’m using the integration from HA and not from HACS, so that is not the issue.
I received the following error in the log:
ImportError: cannot import name ‘POWER_WATT’ from ‘homeassistant.const’ (/usr/src/homeassistant/homeassistant/const.py)
As someone before me I just signed up here to add my name to the list of people rejecting where HA is going with this…
overlooked fact: encryption password gets replaced by a system-generated key
I can already imagine this key leaking somewhere, resulting in cloud backups being potentially decryptable, specially cause you can’t protect them with a key of your own choice.
Forced encrytion is equally annoying as the missing possibility to restore backups offline. When offline use gets prevented and data accessibility is restricted, commercial reasons immediatly come into mind.
HA should stay an open system for every usage scenario a user might have… that’s the origin HA came from. Obligatory changes to configurable options allready in place are (no doubt here) an us-vs-them attitude developing.
This is the first time for me for an update to cause major issues:
After updating to 2025.1 skyconnect just cannot start. I could not reconfigure it in any way either, it keeps saying that an unknown error occurred. Which of course completely killed my zigbee network. Curiously enough my sonoff zigbee sticks are working.
Also the new Zigbee2Mqtt update messed up the RODRET IKEA remotes.
For the first time ever, I am very grateful for backups as I could roll back both the core and zigbee2Mqtt updates, and everything is working again.
the manual backups in this screen are created by clicking the update button in the tile card confirmation upon updating, which is still available and offering user choice
Great release, great new backup functionality!
I am using a postgres db for history data, the database size is 1,6gb but my backup only has 50mb.
The setup process makes me believe these data is included (“Settings and history included”) - which is obviously not the case. Maybe add a hint for this in the setup process and the settings overview
Well - after reading about this backup saga, I’ve made my mind up.
No update from 2024.12 until unencrypted backups and restores are working absolutely flawlessly.
I am forever thankful to the devs for creating this marvellous piece of software - but you started this change to the backup and restore feature at the wrong end.
Good approach, make unencrypted backup possible for local storage and force the user to enter his own password for cloud upload. This way the user is completely aware that he has to store the password. Having an automatic password can be overseen and forgotten so easily.
