I don’t think the Synology backup integration can work with a typical SMB share. The integration does some Synology-specific things, if I understood the information in the release party stream yesterday correctly.
Read again:
And then:
- delete the Samba Share
- reconfigure Synology DSM (was necessary for me)
- use Synology DSM directly as backup location
With this update I seem to have lost all ZHA functionality. I get the following error a lot in the logs: Failed to send request: Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>
Does anyone experience similar problems?
Did not realize that documentation was missing. Here’s a preview while an update is reviewed.
Would it be possible to use iCloud Drive as a backup location.
I do not have any space one OneDrive nor on Google Drive. But have plenty on ICloud Drive.
Possible?
Yes. Someone just has to write an integration for it.
I’m sending the backup to Proxmox, where the VM is running samba.
The Samba Backup plugin can be set to back up HA to a shared drive in a folder I named, but with HA backups the backup is only saved to the shared drive (you can’t set a specific folder) and this causes confusion with backups from multiple HAs.
Am I missing something or how do I deal with this? I don’t want to create another network connection for each machine.
I’m sticking with Samba Backup for now.
- Is this confusing folder naming something that might be fixed in future or are we stuck with it?
That’s up to MSFT to fix
- Are other apps that use the same mechanism for storing files in OneDrive going to put them in the same folder?
No. The folders would be called Graph 1, Graph 2, etc.
- What happens if I rename the Graph folder in OneDrive? Will HA recreate the Graph folder or recognise the name change and keep putting backups in there?
A manual rename should work fine (emphasis on should, no guarantees)
- The previous Add-on I was using for this managed to define it’s own folder name
If you are a new user of that addon, your folder is also called “Graph” now, there’s an issue open on the repo
Can’t do that with a personal microsoft account.
You absolutely can, just need a subscription. Also, it doesn’t matter which where the application, only the account types the application supports (would need to allow personal accounts), which is configured during the creation of the application
Not sure what happened to the energy graphs? But contrary to what is claimed in the blog post they (especially the bar charts) look different:
- they seem aligned more to the left
- the x-axis seems less granular with only a indication every 4 hours
I much more preferred the previous look… I find the current one a real step back.
It’s a shame you didn’t read the GitHub issues.
+1, my solax integration seems to fail with a
ImportError: cannot import name ‘ModbusRtuFramer’ from ‘pymodbus.transaction’
since the update
Not going to start again the talk which was here a month ago (meaningless) - but you definitely missed the point about a feedback received during a beta-testing. Please do not answer.
No problems here. Was running with the ZBDongle-P before and switched to HA Connect ZBT-1 during the 2025.2.0b releases and all works fine for me.
My 101 Zigbee devices on ZHA are rock solid.
It might be a specific device you have that has an updated implementation in ZHA that is causing the issue. But not sure how to diagnose that.
Out of curiosity: why it was decided to move to echarts.js from chart.js?
Btw, Frontend uses some “standard” components like Material, Paper-tabs. Recently noticed that some repos became achieved on December. Does this mean that these components will be not maintained? Then may be Frontend should start thinking about alternatives? I am not an expert here, these are just my worries.
Hi, in my case, downloading a backup from the Home Assistant interface, it is very slow, the speed is about 4 MB and the backup file size is about 16 GB.
Has anyone the same issue? I’m using a Raspberry Pi 4 over an SSD disk.
Thanks
Lovely - great to see the backup system continue to develop!
If there was only WebDAV backup location support I could finally start using it (I don’t want to store the backup on Google etc but woudl like to store it on our Nextcloud server)
Is your backup encrypted? If so it is automatically decrypted on download, which can be slow on a Pi4, especially with such a big backup.
No issues here. Did you try refreshing the app cache?
And tried how it looks in your browser?
Do you have any HACS/custom components installed for styling/interface?