bjorn.sivertsen
Great additions this time around, particularly happy about being able to choose my own site for backups.
Great additions this time around, particularly happy about being able to choose my own site for backups.
Excited for that Bluetooth panel!
Thanks for noting that; fixed!
The new backup settings are great. Well done!
I have one suggestion - allow external backup locations to hold more than the internal backup quantity -configurable by the user, eg with 3 configured backups max stored on HA it should allow more than 3 to be stored in OneDrive/GoogleDrive etc
I’m glad that setting temperature on a thermostat was added, just because I was feeling crazy when it wasn’t working last night lol. I even checked the github test commands and saw exactly what I was saying and that it was supported (I’m guessing in preparation for today’s release), but couldn’t get the same phrases to work in the dev tools.
Now it all makes sense
I like to see progress on the HA Voice PE. But did you ever officially support voice using ESPHome, especially on the M5Stack Echo? I guess many people bought that device for use with HA voice and it has open issues for building for a month now: Unable to compile for M5Stack Atom Echo · Issue #286 · esphome/firmware · GitHub. While there are workarounds, it would be nice if something you even have a tutorial on ($13 voice assistant for Home Assistant - Home Assistant) would actually work out of the box as it is supposed to.
1 reply
Great release! I hope someone will also create a Nextcloud integration for backups.
What I miss is the ability to keep older backups, in case I don’t realize in time that something broke. This might be solved by simply saving the configuration files, which should be really small.
This could also lead to the possibility of having some kind of config history. I tend to keep old automations in case my new approach doesn’t turn out to be better. These usually get forgotten and never deleted.
I used to have a self-hosted git backup, but it stopped working, though I really liked the history it provided. If ever implemented, it could potentially be added to the automation/script pages themselves.
Edit: I seem to be having problems downloading backups. They fail after downloading 1-1.5GB (tried five times to different locations).
3 replies
Sooo, there was a lot of heat during the last update feedback thread. I just wanted to chime in and say thanks for the changes that were made based on this feedback. They addressed a lot of the critique (if not all of it).
Also: Very glad the graphs are getting some attention. Integrated Grafana graphs just aren’t an ideal solution.
Keep up the good work!
Great stuff, basically all the criticism against the new backup-system was fixed. Great release.
Backup screen is stuck in “Creating backup” for around 45min
That 1 automatic backup looks completed and is available for download as seen on the screenshot…
You can extract them and check the size with something like Wiztree (Windows) or Filelight on Linux.
This is awesome. I wish there was a way to support more than one MCP server at a time for a given assistant.
Excited to use the TP Link integration with support of robovacuums
Thanks for listening to the feedback and integrating them in the new Version.
One thing i noticed while trying the new backup feature is that Network Storage Connections are always open. I’m using my NAS mainly to store backups and data i don’t need very often, so i configured it to go to sleep if there is no active connection. When i add my NAS to Home Assistant it keeps the connection always open even if it’s not needed. It would be nice if Home Assistant only connects to my NAS while making the backup. My workaround now is to start it once a week and sync the backup folder to my NAS.
… and in the energy dashboard the titles are wrong when comparing energy data (for instance, jan 2024 with jan 2025):
That already exists, just add the network mount in the settings panel
Considering the heavy criticism voiced in the previous release thread, the excessive positivity in this post, especially in presenting the “iterations” on backups, is quite hilarious.
That doesn’t take away anything at all from the fact that the community input has been taken very seriously. It shows a willingness to accept input and change course where necessary. This whole episode considerably strengthened my trust in the leadership of this project. Really well done!
You can find instructions on the website
does anyone know if anyone is working on dropbox integration?
Would also love to see other backup rotation. scheme options like Grandfather-father-son.
Amazing update as always!
That’s much better - backups are now nicely configurable. Thanks all!
See if https://github.com/home-assistant/frontend/issues/24089 helps, and you can add your details there. Maybe something to do with the names but not sure exactly what.
1 reply
Unencrypted backups! Thanks! I was waiting for it 
I prefer to create backups from My backups page (were you see list of backups). But there is no backup progress indicator on that page, you have to go back to see it.
It also would be nice to see actual progress bar with eta 
Users who are affected have been actively informed about this using a repair. Additionally, users affected by this will get information from pip when trying to update as well.
…/Frenck
Thanks for this new release!!!
Love this possibility to enable disable per location 
Is the shared conversation thing not working for anyone else? Or did I miss configuration steps?
A generic WebDAV integration would work with Nextcloud and pretty much any other service that supports the same interface.
Another great release, thank you Nabu Casa and the community.
Congrats Frenck, we always knew you were a star.
Hey Paulus, your feature of the year, I didn’t get a chance to look at the beta but read the notes. Mate it isn’t an analogue phone it’s VoIP.
1 reply
fantastic job everyone!
Google Calendar integration seems to have broken for me upon upgrading (Setup failed for ‘google’: Unable to import component: No module named ‘ical.recurrence’)
Before I open a bug report - has anyone else encountered this?
1 reply
@gjohansson-ST Thank you for adding Filter to the GUI-accessible sensors!!
Interested in assisting with Voice! Reach out to let me know how I could help.
I’m not sure that’s HA’s job. There are a multitude of ways to get this info anyway.
Also check the size of your DB, if your using the built-in DB (SQLite).
1 reply
Great response to the feedback!!!
Sorry to report the final changes to b11/b12/release did not yet fix this
Yes the backups were made, are in their respective locations but 1 failure (OneDrive still a troublemaker) causes the frontend to show there are none.
what’s more, even while my Synology is currently asleep,
and it should be listed under ‘unavailable locations’ it is listed in the available locations, and selectable
the integration is Not showing as failed
while the entities are of course, as the device is asleep:
a restart makes the system connect Backups Backend and Frontend again:
and show the Synology correctly now (this is a first in my config, didnt happen during beta, so b11/b12 did fix that apparently)
However, the original issue leading to all of this was the disconnect of the Onedrive, to which the backup actually was Not made, and flukes the system completely
2 replies
Same problem - only with MS One Drive:
see Allow separate backup schedule per location
and add your +1?
I wish we had a way to keep one major backup per week/month that doesn’t get deleted for X months. That way we could find that one thing(whatever it might be) that broke and we didn’t notice in time. I’m doing this with an automation that creates a manual backup for now but there are downsides to that.
I still “see” the old back-up panel, none of the nice new stuff for me here in Germany?
1 reply
Unfortunately I’m in a Phase where I can’t put Time into checking Things out.
Just wanted to leave a massive Thanks to all Devs and Deciders! Relief Feedback and Critics are been heard and taken serious. By reading it’s really awesome. Let’s skip next Year the .1 directly 
Again, applause and hurray!
No not splitting hairs. It is a VoIP connection to Home Assistant. The fact that an ATA connector was then used is irrelevant. If it was a analogue phone connection, Home Assistant would have to have line voltage and an AC Ring Generator.
That is why when I read the Beta notes I had a wbry smile on my face.
Can you tell I am a Telecommunications Engineer
I did that 40 Minutes ago, change nothing. Restarted HA, no change. Just went back and there it is… 
All my previous backups are showing as 0 bytes in size.
On the main backups page it shows as NaN
I see the same.
When my NAS is offline the UI says no backup was made … despite locally on the HA Server the files are there.
Installed update and litter robot authentication has failed email address and password have been checked.
I think you’ll need to setup the developer account at google first, look at the integration documentation, how to do that Google Drive - Home Assistant
also make sure my.home-assistant.io links to your instance (which is also described in the documentation I link above, see scenario 2)
1 reply
if your using deepstack there was quite a model update, so it learns better, if you go to back up settings and untick deepstack your huge back up will drop down by about 5gb (well it does for me).
1 reply
Backups to OneDrive seem to go to Apps\Graph - sort of mentioned in the docs but could be clearer.
I’m really happy to see this as a built in feature of Home Assistant. The previous Add-on I was using for this managed to define it’s own folder name and supported generational backups. Are these on a roadmap for the backup integrations?
1 reply
what is even worse I’m not aware about any feedback from devs side that they are aware.
For sure it would be show stopper for me too, so I’m going to stick to 2024 until confirmation it’s fixed
BTW let me share my thoughts about the blog post. I really don’t like the tone of it. there is no word about “we made mistake”. Instead “we are so great we listening to your great feedback”. This is not a transparency I would expect. It feels like releasing broken features, to fix them later on is good plan how to present company as listening to the community attempting to make us grateful
3 replies
to that purpose i use samba backup. does a daily backup, keep only the latest in the HA, and keep 30 on a NAS.
this way i can have a quick roolback, often enought, but also the ability to roll further if needed without filling up the SD card.
since we now can use a type: energy-date-selection on the statistics-graph card I learned that we can use a collection_key option to
however, there is no example of that in the yaml documentation, nor can we do this in the UI to see what it should be (it’s a yaml only option as are the energy cards)
anyone found out how to set a collection_key?
1 reply
exists also a state to check if the backup was successfully?
Post your logs, or better still in GitHub. Posts like yours don’t help.
Backup is stuck on uploading to locations for about 11h
I don’t think “mistake” is the right word, they introduced the new cloud backup and made the decision to implement a good practice of encrypting those backups. They also encrypted the local backups which the community responded negatively.
They have listened to the community and introduced the option to have unencrypted backups not only locally but now with multiple backup locations offering the option to also replace a bunch of addons. Google Drive Backup, Samba Backup etc which all in all in very positive.
What really would the apology be, “sorry we had security in mind” there is no real need to point fingers, they have responded really well in my opinion.
1 reply
Google Drive backup integration seems like a step backwards compared to the long established unofficial add-on, as it requires much more convoluted setup (generating your own API credentials).
1 reply
general. Only personal accounts are supported, isnt that mentioned in the docs?
edit
yes it is OneDrive - Home Assistant
read before write
thnx,
I thought I needed to open the google integration which was not there,
Now I’ve set it up and I am testing it,
I still forsee one issue, via the addon I limited the amount of backups to 7 because of space,
locally I have 30, so I think my drive will be full soon.
But we will see.
The previous third-party integration https://github.com/sabeechen/hassio-google-drive-backup did the same job and also provided a number of very useful sensors that allowed you to analyze how the previous backup ended. Are there such sensors in this integration?
1 reply
Exactly the same problem for the esp32-s3-box-3 as the M5Stack Atom Echo for HA Voice PE. A good few months now of not being able to compile the default installation for this device. It seems these two devices were pushed to get things moving and now are not being supported on the platform and no efforts to resolve.
I like to see progress on the HA Voice PE. But did you ever officially support voice using ESPHome, especially on the M5Stack Echo? I guess many people bought that device for use with HA voice and it has open issues for building for a month now: Unable to compile for M5Stack Atom Echo · Issue #286 · esphome/firmware · GitHub . While there are workarounds, it would be nice if something you even have a tutorial on ($13 voice assistant for Home Assistant - Home Assistant) would actually work out of the box as it is supposed to.
I had this too. It looked to be an issue in the UI cache. Once I Ctrl+F5, the sizes appeared.
1 reply
I use a raspeberry pi 4 B+ as HA Dashboard only, and after this update it became almost useless due to high CPU load, and stucks . I find out if i remove the history card(s), the performace get’s normal, and the dasboard work fine. Anyone have this problem too?
nope. No entities or events yet unfortunately.
mentioned quite a few times in #beta Discord though, so hopefully those calls were noted by the team.
Seems those are an essential part of a mature core system, allowing the user to automate notifications and other feedback.
In the end, we wont all be watching that Backups configuration panel most of the time
HOME ASSISTANT WILL BE ABLE TO CALL YOUR ANALOG PHONE TO TELL YOU A MESSAGE
Remember our tutorial on turning an analog phone into the world’s most private voice assistant? Thanks to Jamin, we now have a way to call your analog phone from Home Assistant!
You can use
assist_satellite.announceto have Home Assistant call your phone and play a message when someone picks up the phone.If you use an LLM as the brains for your voice assistant, you can take this one step further with the new
assist_satellite.start_conversationaction. Instead of playing an announcement, it starts a conversation between Home Assistant and the user, with Home Assistant saying the first message. Left the garage door open for 30 minutes? No problem, let Home Assistant call and ask if they want to close it.(Starting a conversation with the default conversation agent is a bit more work and did not make it this release).
Paulus mentioned in the Home Assistant 2025.2 release party video that this assist_satellite.announce feature will likely not be extended by Nabu Casa developers themself but it would be such as awesome feature if Assist AI could call up mobile phones to start a conversation between Home Assistant and the user.
Some use case scenarios could for example be to call up your neighbours (if they approved it) on their mobile phones if there is a fire alarm trigger by a smoke detector. Or call members of your neighbourhood watch if burglar alarm is triggered while the alarm system is armed. Question could be if they are able to go chwck it out for you or not and then it can inform you who has responded.
They also mentioned in the Home Assistant 2025.2 release party video that they would love it if some independent developer stepped up and extended it so that it could call mobile phones too.
I jumped on the update as it seemed good as usual only… it, for the first time ever, actually broke a good chunk of my existing setup. I lost MQTT and ZHA so lost my lights and heating… i spent a good hour restoring so in the last update… thank heaven for the backup change. All in all think i shall have to skip this for the next one.
I am not sure on what side the issue is, maybe we can fix that in future. But you know as fix you can use another browser 
Thats totally fine, with the new backup dashboard we provide a simple backup solution. If you had already a nice solution just keep it 
I had the same until I reloaded browser
Might be a small thing - but would it be possible to have a file retention configuration per file location?
Ideally I want to have one backup process per night. I’d like to keep only 2 days on my homeassistant host system but longer on my network storage. As it is now I’d have to configure two seperate backup processes for this?
Almost got excited about OneDrive backups, but they still don’t support “Work or School” accounts.
Next attempt for a backup with storage location One Drive:
Error during backup in async_upload_backup:, message {“error”:{“code”:“invalidRequest”,“message”:“Parameter Exceeds Maximum Length”,“innerError”
Hi, I really appreciate all the change to the backup integration. Well done so far.
But I still have an issue with automatic backups to my local NAS. This worked fine over years until 2025.1.
I opened an issue at github and described it here:
What do you think about this?
Thanks Hoppel
1 reply
