You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm considering switching z-wave stick, and in that process I realized that the memory of the stick isn't backed up at all, when backing up the store directory. Clicking the "NVM Backup" creates a NVM_.....bin file in the store directory - but is there any way to:
Create this file regularly? (every month/week/night/on include/exclude f.ex.)
I think the current API call is through websockets, which I don't want to automate in curl :P
Remove old bin files, so there is a rolling set of N files
Alternatively overwrite the same one always, then my own backup program can show me snapshots
Note: The warning says the z-wave radio is disabled while backing up, so I can understand why you would not want to do this backup immediately after inclusion/exclusion... Maybe a compromise could be that every night, a backup job runs that checks if anything has changed since last backup. I imagine the NVM backup won't contain stuff like states -- although it might contain neighbor/route maps, which can change once in a while..
Mike.
The text was updated successfully, but these errors were encountered:
Hey,
I'm considering switching z-wave stick, and in that process I realized that the memory of the stick isn't backed up at all, when backing up the
store
directory. Clicking the "NVM Backup" creates aNVM_.....bin
file in thestore
directory - but is there any way to:Note: The warning says the z-wave radio is disabled while backing up, so I can understand why you would not want to do this backup immediately after inclusion/exclusion... Maybe a compromise could be that every night, a backup job runs that checks if anything has changed since last backup. I imagine the NVM backup won't contain stuff like states -- although it might contain neighbor/route maps, which can change once in a while..
Mike.
The text was updated successfully, but these errors were encountered: