[oakesm9]

> I kinda hope nobody tries. Their attempts at monetization have been pretty friendly and tame thus far & if something spooks them that could change.

To be fair to them they've been making a big push on adding backup support recently. Their Nabu Casa subscription has built in support for this and was a major selling point for me getting the subscription (I have Wireguard for remote access already).

At the same time they implemented first class support for their own subscription, they added the hooks for other integrations to provide the same level of backup support. Now you can easily choose to use Google Drive, S3, BackBlaze and others just as easily as Nabu Casa. In some ways it's "better" as Nabu Casa only supports a single latest backup.

From this they seem pretty friendly and not too interested in lock-in.

[mook]

Unfortunately their new backup support forces encryption; that makes sense for cloud-based backups but not for local (NAS etc.) ones. Requests for that just get replies to do it with manual backups the old way.

[badlibrarian]

Unencrypted backups is an option.

[tw04]

Why is that unfortunate? Encrypting backups is just a good best practice in general.

[mook]

Because that means I need to manage the encryption key (which is a file, not a password). It makes it harder to do restores because I need to dig out the key.

I don't have anything I care about in the Home Assistant install to need encryption; if you have access to that you are already in the network, same as the actual running device.

[farawayea]

It is unfortunate if you want to deduplicate and encrypt in the target backup.