Well.
You see “my” code is mostly “AI” in this case Gemini. like I also said in my post in the beginning of my thread
Since I’m not really happy with the backup function in homey, I did ask Gemini to help create a script to get all flows and split them up, in separated folders/files as backup.
So be my guest.
But better ask “Ai” 
Sorry, of course meant MB. Now it’s 94,5 MB. Download does not work on iPad too.
Mike_Nono is correct, on right click „open or save file“ one can save a json file.
The „save flow file“ doesn’t work at all
Thanks, this is very useful feedback.
Great to hear that the Payload Too Large issue is fixed, especially with your large backup.
The Android result also helps narrow down the remaining download issue. So the fallback link itself works, but the automatic download triggered by the gray Download file button still doesn’t start the actual download in those browsers. Long-pressing Open or save the file and selecting Download link is currently the working route.
I’m going to keep this as an open issue rather than consider the browser-download problem fully fixed. I’m already working on the download handling for the next development version, with the aim of making Download file initiate a real file download directly while retaining the manual link as a fallback.
Thanks for testing this on multiple Android browsers — that is exactly the kind of cross-platform testing I can’t reproduce on my own devices.
Thanks for the clarification — MB makes much more sense. 
I’ll keep an eye on the memory usage nevertheless. An increase from around 88 MB to 94.5 MB is worth measuring during repeated backup/download operations, but at this point I don’t want to call it a memory leak without further testing.
Your iPad result is also very useful. It confirms what we’re now seeing on Android as well: the backup JSON can be saved using the “Open or save file” fallback link, but the normal download/save action is not working correctly in all browsers.
So I won’t consider the browser download issue fixed yet. The next development version is reworking this part specifically, while keeping the manual link as a fallback.
I’ll also investigate “Save flow file” separately since you report that this doesn’t work at all.
Thanks for testing and for the clarification.
Thanks Mike! 
That’s clear enough for me. I’ll keep you credited for the original backup scripts and the work that started this project.
And yes — AI has definitely been part of the development process on my side as well. That’s also something I’ll keep transparent in the source repository.
Thanks for letting me build further on it!
Hi Dennis, FYI I just tested with Firefox & Chrome browsers on a Windows machine, same situation.
As requested here’s the github and the code, free to use and to evaluate: GitHub - 94brwdfyst-coder/Homey-backup-center: backup center for homey selfhosted server en homey pro · GitHub
as requested the source code is online see github
Backup Center 0.3.28 — improvements and more testers welcome!
Thanks for all the feedback so far. A new development build is now available on GitHub.
What changed?
37 automated tests, lint and the Homey build pass. Version 0.3.28 is running on my Self-Hosted Server with all four Flow cards present. Real NAS compatibility still needs testing; SMB3 encryption and required SMB signing are not supported.
Would you like to test it? I would particularly appreciate browser download tests, SMB/SFTP tests on different NAS systems, and scheduled Flow backups. Please include your Homey model/version, browser or NAS/protocol, steps and any error message. Never post passwords, API keys or complete backups.
This update is available through GitHub for developer installation; the App Store Test release has not been updated to 0.3.28 yet. Setup and limitations.
Thanks for helping improve Backup Center!
as requested you can now test if sftp and smb2 work. Haven’t test them out myself.
Hi Dennis,
Homey Pro 2026 v13.5.0
App v0.3.28
Still no change in behaviour at both Android and laptop
I can’t find/see a SHA256 fingerprint from my Synology NAS, only a SHA1 type seems to be available, which probably isn’t accepted. The error messages are not taking me to a solution:
It refuses to save the config when something’s off, I have to start from scratch everytime, → a bit annoying.
Its config is getting saved, even if the test fails. Saves me a lot of repetitive entering of data. Thank you.
It’s unsure what is wrong here.
I can’t find the right format to enter here (no confirmation or clear error message):
The (just made up) share name 'smb'
The existing folder is called '/home/backup/homey/1_homeypro/smb'
Does it matter if I use / anywhere as leading or trailing slash?
Permissions:
smb://NAS.IP.address/home/backup/homey/1_homeypro/smb I can read/write files from a filemanager.Protocol support
I didn’t find any error mgs in the SMB logs, apparently it doesn’t initiate a connection
It did work last night with app v0.3.27, only I can’t recall seeing a (critical) push message (it was on automatic)
(API Key RW permissions: Devices/Flows/Variables/Zones/Apps)
With v0.3.28 it does not work anylonger, both scheduled & manual backup fail (I’ve seen this strange phenomenon with other AI apps: one day it works fine, but after an update for something else, it’s suddenly broken)
Can’t test as SMB doesn’t work yet
Thanks again for all your testing. I’m working on the fixes for your finds. I’ll try to get another testbuild ready this evening.
I’m about to publish version 0.4. SMB en SFTP are working for me now. I tested it on my minipc, which isn’t a NAS. So not sure if it will work on your site. Hope you’ll try it out and let me know. ETA 15 min.
No hurrries, and , thanks. Oh, plain FTP would be fine for me as well.
Hi all,
Homey Backup Center v0.4.0 is now available on GitHub.
A big focus of this release has been improving and testing network backups, especially SMB2 and SFTP. Thanks Peter_Kawa for your testing and patience.
During testing we found that the SMB client was attempting to use NTLMv1 authentication. This was the reason the connection could fail even though the same SMB share worked correctly with other clients.
Version 0.4.0 now explicitly uses NTLMv2.
SMB2 has now been tested end-to-end against a Samba server on Ubuntu:
SFTP has also been tested end-to-end against OpenSSH/SFTP on Ubuntu:
SHA256 is the recommended host-key fingerprint format, but SHA1 fingerprints are also accepted for NAS/server compatibility.
The fingerprint is the SSH/SFTP server host-key fingerprint shown by your NAS/server. You do not need to generate a new SSH key specifically for Homey Backup Center.
Saved network destinations now reload their settings when selected. Passwords remain hidden; leaving the password field empty keeps the previously saved password.
The current end-to-end tests were performed using Samba and OpenSSH on Ubuntu.
Synology and QNAP have not yet been verified end-to-end, so feedback from Synology/QNAP users would be very welcome — for both SMB2 and SFTP.
Flow cards and scheduled SMB/SFTP backups were also not part of this test round yet, so feedback on those is welcome as well.
Thanks to everyone who has been testing and reporting issues. The SMB authentication feedback in particular helped track down the NTLMv1/NTLMv2 problem.
GitHub / v0.4.0:
it’s uploaded to github. hope it will work on your side as well. otherwise let me know.
Glad to help you discover any issues.
Homey Pro 2026 v13.5.0
App v0.4.0 → but it got updated to app store update v0.4.2 along the way
Synology NAS DS214play - DSM 7.1.1-42962 Update 9
TL;DR - Fixed. Believe it or not, an underscore in a folder’s name in the path to the destination folder, results in error “Network operation failed. Check folder, permissions and protocol support”;
Test backup works OK
What works
homey_backup_webdav which has underscores in it), without specifying a path to destination folderhome), and choosing a path without an underscore in a folder’s namehome), and specify a path with a folder’s name holding a dash (backup/homey/1-homeypro/smb)What doesn’t work
home), and specify a path with a folder’s name holding an underscore (backup/homey/1_homeypro/smb)(Possibly this was the issue with v0.3.28 as well)
I use SHA1 but none of the keys is valid. I don’ t see any “host-key fingerprint”, only a Certificate SHA1 Fingerprint, and a Public Key SHA1 Fingerprint. The Synology NAS certificate is self-signed, perhaps that’s a nono?
As mentioned before, plain FTP will be fine as well for LAN only usage.
Automatic Scheduled WebDAV backups work again, but there’s no (critical) push notification. But, as I don’t like automagically generated notifications on my phone, I’d rather create a flow myself for failed backup notifications.
For now I selected an other test user as recipient (which hasn’t a phone to send push msg to).
I hope my findings help you out a bit.
Backup Lokaal gaat niet goed, daarom cloud-backup aangeschaft . na update Home versie 13.5.0 kon ik nu wel cloud backup herstellen maar lokaal backup nog steeds niet in orde. Daarom benieuwd of deze app wel lokaal kan backuppen en herstellen. Wanneer komt app op site van Homey zodat ik deze kan testen ?
Backup Center v0.4.2 – new name, certification update & SMB2/SFTP improvements
Hi everyone,
A small update on the app previously known as Homey Backup Center.
The app has been renamed to Backup Center. This change was made as part of the Homey App Store certification process: the app name may not contain “Homey”. The App Store description and artwork also needed some adjustments, so I used the opportunity to clean up the presentation of the app as a whole.
What changed in v0.4.2?
SMB2 and SFTP testing
Since the previous update, I have also completed real end-to-end testing of both network backup methods.
SMB2: a complete JSON backup was successfully written to a Samba share using SMB2/NTLMv2.
SFTP: a complete JSON backup was successfully written over SFTP with SSH host-key verification enabled.
So these tests went beyond just checking whether a connection could be established: actual backup files were created and verified on the destination.
Certification
Version 0.4.2 has now been prepared/submitted for Homey App Store certification with the new name and presentation.
The source code and v0.4.2 release are also available on GitHub:
Backup Center v0.4.2 on GitHub
Thanks again to everyone who has tested the app or provided feedback so far. Feedback on SMB/SFTP setups, especially different NAS environments, is still very welcome.
— Dennis
