Welke versie gebruik je momenteel? Der GitHub versie bevat aardig wat wijzigingen. Laat het vooral weten en wat er precies niet werkt, dan kijk ik wat er aan gedaan kan worden.
Hi Peter,
Thanks, this is very useful — especially the SMB2 testing because you’ve narrowed the problem down quite precisely.
The underscore behaviour is interesting. From your tests it looks like underscores are fine in the SMB share name, but an underscore in a folder name entered in the destination path causes the network operation to fail. A dash in the same position works.
That gives me something very specific to investigate in the path handling rather than SMB2/Synology in general. And yes, it’s quite possible this also explains some of the behaviour you saw with v0.3.28.
Regarding SFTP: the fingerprint Backup Center asks for is the SSH server host-key fingerprint, not the Synology TLS/certificate fingerprint. So the self-signed Synology certificate itself shouldn’t be the issue. Please don’t use the “Certificate SHA1 Fingerprint” as the SFTP fingerprint. I’ll look into making this distinction clearer in the UI/documentation, and also into the best way to obtain the correct SSH host-key fingerprint on Synology DSM.
I’ll also keep your suggestion about plain FTP for LAN-only environments in mind, although I’d prefer to get the existing secure options working reliably before adding another protocol.
Good to hear that the automatic scheduled WebDAV backups are working again as well.
Your point about failure notifications makes sense too. A Flow trigger for a failed backup would give users the choice of whether they want a push notification, timeline notification, logging, or something else, instead of forcing a phone notification.
And thanks for testing this on a Synology DS214play / DSM 7.1.1. That gives me a real Synology environment to add to the tested configurations.
I’ll investigate the underscore/path issue first.
Dennis
Thanks Peter. I’ve now reproduced your folder structure on a separate Samba server and tested both:
backup/homey/1-homeypro/smb
and
backup/homey/1_homeypro/smb
Both the connection/write test and an actual backup succeed with the underscore path on my test setup.
So I don’t want to simply disallow or replace underscores, because they are valid and do work with Samba.
Could you please run the failing underscore test once more on v0.4.2 and send me the complete error message shown by Backup Center?
In particular I’m looking for the part containing something like:
SMB failed during smb-list-folder
SMB failed during write-probe
or
SMB failed during rename-probe
If there is a Diagnostic: / STATUS_... part, please include that as well. No password or other credentials are needed.
That should tell me exactly which SMB operation behaves differently on Synology DSM.
hij staat nu online:
Backup Center
Houd je instellingen veilig met eenvoudige, betrouwbare back-ups.
de naam moest ik veranderen omdat er Homey instond, en dat was niet toegestaan. Maar je kunt hem nu dus uit de app store downloaden.
Haven’t tried it yet. Does plain FTP work?
Hi Dennis,
This is an English-language thread, and very few people know Dutch, so please…
at the moment no. But we could try to get that working as well.
Thanks for your efforts in developing this app! ![]()
I checked whether I was able to make a backup to my Synology NAS (running DSM 7.4.1) via both SMB and SFTP. My share is named Homey Pro and the folder is called Back-ups.
Connecting and making a backup via SMB (via hostname) was uneventful and worked without a problem.
Setting up the connection through SFTP (via IP) was a bit more challenging, as Synology does not seem to provide an easy option in the DSM interface to display the SSH host fingerprint.
As a workaround, I used FileZilla (FTP client I use on my laptop). When creating a new connection to an unknown device, it shows the fingerprint. Also, for existing connections you can view the fingerprint by clicking the
-icon in the bottom righthand side of the window.
With that missing piece now available, I was able to connect successfully to my NAS via SFTP and generate a backup.
I haven’t done any further tests.
Some questions. If I understand correctly,
- A restore entails a full restore of everything that was backed up. Will it be possble in a future version to perform selective restores? Such a specific devices or variables?
- Insights are currently not part the backup. Is backup and restore of that data planned for a future version?
- In addition to standard Logic variables I use variables created by the Better Logic Library app. Are these also part of the back-up?
now it does. Try it out pls.
Hi Dennis,
Homey Pro 2026 v13.5.0
App v0.4.2
Synology NAS DS214play - DSM 7.1.1-42962 Update 9
SMB
It’s OK now
Did you adjust anything, or is it the moon and the stars to blaim ![]()
A test backup succeeded
SFTP
Man, for FS I couldn’t figure this out on my own
![]()
Thanks to @SunBeech great ‘Filezilla’ tip I can now succesfully connect to SFTP as well ![]()
In my case it would be: No option at all →
@Dennis_Weel Is it a plan to add this ‘How to find the Synology host-key fingerprint’ tip by Sunbeech to a FAQ section in post # 1?
app v0.4.3
Confirmed, plain FTP works @ Synology NAS
About the SFTP SHA fingerprint.
Why not have it shown in the app settings, like in cli/termial.
Like when you access a new site and have the user ok it?
Then save it
Check hostverifier function for js script
With an “empty” Homey, or with a Homey with deleted devices/variables/zones/flows etc., within the limited scope of this app (edited), that should be possible. It shows what is missing on your Homey compared to the backed up data:
Not atm. Did not find anything related in the JSON.
@Dennis_Weel Including BLL logic variables would be a very nice to have.
Translated to EN
Backup Local is not going well, therefore cloud backup purchased . after update Home version 13.5.0 I could now restore cloud backup but local backup still not in order. Therefore, it is curious whether this app can backup and restore locally. When will app come on site from Homey so I can test it ?
Always start at post 1 (most dedicated app topics provide for additional app info in the opening post) ![]()
This app can backup locally, or to a local or online network share, but it does not backup just everything, as mentioned in post # 1.
In case the native Homey local backup per USB tool isn’t functioning as expected, you’d contact Athom support https://homey.app/support
Thanks Peter ![]()
Just to clarify the restore part: Backup Center already supports selective restore for the changes it detects.
It first compares the backup with the current Homey and creates a restore plan. Creating that plan does not change anything on Homey. You can then select which detected changes you actually want to restore instead of restoring everything from the backup.
This is also exactly why I changed the restore interface in v0.4.4. It became clear from the feedback that the old interface did not make the selective part obvious enough.
Restoring something that has been completely deleted or is missing from Homey is a slightly different case though. I want to be careful with that distinction, especially for devices, because Backup Center cannot recreate physical radio pairings. I’ll investigate further what can safely be recreated from backup data.
About Better Logic Library variables: they are not currently included.
I agree that BLL variables would be a very nice addition. I’ll look into how BLL stores/exposes its variables and whether there is a reliable way for Backup Center to both back them up and restore them safely.
I don’t want to promise support until I know both sides are possible, but I’ll put it on the list for investigation. ![]()
And because I have a few BLL’s myself I will try to work on that today. Not sure if a new build will come out today. I already made huge efforts. And want to have some spare time as well ![]()
Will put it on the to do/investigate list.
You’re absolutely right, I should’ve added “within the limited scope of this app”. Edited my post accordingly.
Just ignore us every once in a while
No hurries, mate. I appreciate all effort you put in it.
Hello Dennis, great app. But I need a bit more explanation.
I’ve installed the app.
But where in the configuration can I specify a folder on my computer so that the backup is written there?
So, without network settings.
I use Homey web
Hi Cor_Brink:
When using Homey Web, Backup Center cannot write directly to a folder on your computer. For a local backup, use the Download option; your browser will then download/save the backup file to your computer.
If you want Backup Center to write backups automatically to a specific folder, that folder needs to be available over the network using SMB2, SFTP or FTP. hope this is helpful.


