and how do you use this command line without access to HA? or in emergency situation ie no space on disk to decrypt?
@packetracket, Sorry but I donāt understand how you manage it. do you have different port, but the same IP? If not how you can receive the data from external sensors?
I read the release notes and I searched the GUI prior to my post. I just did so again. I still could not find a mention of how to set a different time for an automated backup. Would you please be so kind as to tell me what I missed ?
I would love it if this end up with an introduction of better undo/versioning of HA configuration. It all seems to me people are used to using backups for this, but itās a hacky workaround.
I have been burned in the past by accidently deleting big part of my dashboard. I had a backup from shortly before and I just restored it.
- how often do you open your backup archives?
- What do you open it up for?
Iāve never done the above two, but I do like the use cases explained by others and see the value in them
- How often do you need to restore your backups?
Iāve used the restore three times. One was to move HA to my new server, the other two were because an official HA update broke my installation. Apparently the option to create a backup as part of an update is no longer available and that is, in my opinion, a huge mistake. This functionality has saved my installation twice, because I had a backup from just before the update that broke my installation.
āAlso, the beta was done over the holidays. Contributors have families and friends, too.ā
To be fair, a beta that covers the redesign of an important component should not be done over the holidays, because of exactly the same reason as you stated.
Thanks for your Words!
Productive is a good idea While i think there is already much productive Feedback here. Well, on your Questions:
Sometimes not for several month, then multiple Times per Day. Iāll average to 2x Month.
Obviously getting previous Settings. And modify/restoring DB without reverting the whole System.
Regulary 1-2x per Month - cloning the productive System to Dev System. And if a new Update goes wrong, iād say 1-2x per Year.
Then, for some more Arguments in this Decision:
- Give the Users the Choice, do not Force them
Another Example might be the Hard Coded DNS. I consider it beeing Anti-Privacy and actually leads to other Complications. While it is deeply buried into the System, at least it can be turned of. I think this should be the Way. - It adds Inconvenience and is in Fact a Single Point of Failure, if the Password is lost
I rarely had Problems with encryted Files. Only, and most of the Times, when i really needed them
In addition, there have been some - productive and constructive - proposals from others, which i think are really solid, and would likely solve this Problems:
- Make Encryption Opt-Out
- Disable Cloud Upload with turned off Encryption
I allow myself to react to some Statements - with all Respect and much Love for you and everyone involved in the Development of Homeassistant:
Isnāt UX rather related with Design and Interaction? The Problem with the Backups is a forced encryption on System level.
I canāt recall a survey/vote about the Roadmap or on (this) specific Features. Where was it? I would have loved to have voted. If the Majority wants something else than me that would be totally fine.
Absolutely. And i think it is just not fair for every single Dev, that HomeAssistant keeps improving so much, and such Decisions overshadow all the excellent work.
But this Discussion doesnāt happen out of nowhere. And if its not solid to include (holidays and/or just some unsolved problem), then i donāt get why it gets released. This is not Windows
I use a NAS for backup and Iād like to retract my statement. I want unencrypted backups when they are local and not cloud.
It is possible to bypass the new backup system. Even if automatic encrypted backups have been set up, one can use the following action in an automation or in a script linked to a dashboard button
action: hassio.backup_full
data:
compressed: true
enabled: true
and it produces an unencrypted backup (if a password hasnāt been specified). Currently there is no deprecation notice on this feature.
You missed nothing
In your local timezone, some process happen on your database every night, 4:45 is a few hours after that so that your backup is the smallest.
Really looking forward to the integrated backup solution. Iām sure this feature will mature over time with all the constructive feedback and I love what you guys do.
Anybody else having issues with starting the zigbee2mqtt add-on after updating to 2025.1.0? I am unable to get it to start since updating, although I updated HA, OS & the add-on at the same time so I donāt know which action has caused issues. Iāll try to add more info here as I dig it up.
Update: solved via the below process. Leaving here in case anybody else does a bunch of updates together like me.
If anybody else has this issue, could be due to updating Zigbee2mqtt from something older than 2.0.0. Check for this in the Zigbee2mqtt log. See the end of issue discussion at the url in the below log snippet for an example of how to update the configuration. Note that the add-on configuration is what needs changing, not HA configuration.yaml.
[2025-01-04 07:28:43] error: z2m: Error: USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration.
[2025-01-04 07:28:43] error: z2m: If this happens after updating to Zigbee2MQTT 2.0.0, see https://github.com/Koenkk/zigbee2mqtt/discussions/24364
I also had all Zigbee2mqtt action sensors failing after the update. See a few different options here to correct it: https://community.home-assistant.io/t/action-entity-missing-for-zigbee-switches-zigbee2mqtt/630468/12, and some other info about avoiding breaking changes during the 2.0.0 update here: https://github.com/Koenkk/zigbee2mqtt/discussions/24198
But why are the Backups still named in the cryptic manner and not e.g. yyyymmdd-hh-mm-ss.
How will anyone deal with this?
I agree with this however this has always been the case Even before. This could be improved.
- how often do you open your backup archives?
Very often. I often change an automation, or script and something does not work and I find the old working yaml in the backup from yesterday and copy paste it back. I even make a manual backup before making bigger changes in automations. - What do you open it up for?
Get old yaml than my revised broken one.
It also happens that I have to hack the files in .storage when e.g. the Deconz integration leaves ghost devices that cannot be removed. I had to do that two days ago. I made a backup just before doing that. - How often do you need to restore your backups?
Mostly to revert broken HA releases - 1-2 times per year. And every 2nd years when getting new hardware for HA.
I am really worried about these encrypted backups. I am worried that I may loose the key. I am worried that I cannot access old yaml.
An MVP is OK when it is a new feature. But taking away a function that we rely on is not OK. You should have made encryption optional. At least for local storage. I am fine that a Nabu Casa cloud backup must be encrypted.
Please make this optional fast.
It is for detection for some Tapo cameras, but maybe for more.
Didnāt update until now. But have read this now here and above already as well.
There is really no auto-backup (with checkbox to unselect this step) before updating Core or Add-Ons?
Unfortunately the team seems to have missed a point about MVP. When doing something new, it really is anything that does something that can be considered useful. But when replacing an existing implementation, it is anything that is at least as good as the earlier one.
Forced encryption is not. It is clearly worse than the old implementation. For very many it is just waste of many sorts of resources. And it brings in the single point of failure with the keys - which many new users will discover too late, if they really act like described in the reasoning of this whole backup change.
If we upgrade HA, could we continue to use the Google drive backup integration (backup on my Synology via samba backup, and another one on my google drive) and not the new HA backup option?
Since 2025.1 my log file is flooded with previously not seen error:
2025-01-04 10:19:51.389 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 1055, in _async_update_entity_states
await entity.async_update_ha_state(True)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 978, in async_update_ha_state
self._async_write_ha_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1148, in _async_write_ha_state
self.__async_calculate_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1081, in __async_calculate_state
capability_attr = self.capability_attributes
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 1087, in capability_attributes
) and MediaPlayerEntityFeature.SELECT_SOURCE in supported_features:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'int' is not iterable
it repeates every 10 seconds, so it is already hundreds of entries since updateā¦ Any idea what it is and how to fix this?
Just FYI, your Card-Mod changes might be effected by this update.
Since I only have a few, I donĀ“t know what is effected, but the code below doesnāt hide the icon in the entities card of my input select anymore.
card_mod:
style:
hui-generic-entity-row $: |
state-badge {
display: none;
}
Iāll live and figure it out when I have time, but itās good to know when you use a lot Card-Mod.