Backup & Restore
The master Reactor device has, in its control panel, options for backing up and restoring the entire set of ReactorSensors' conditions. When the Backup Now button is clicked, the current sensor configurations are written to a file named
reactor-config-backup.json on the Vera or your openLuup install (in the same directory as the plugin files). A link is provided so that you can download this file and store it locally, which is recommended, in case your Vera storage becomes corrupted.
If a copy of the Reactor backup file is not downloaded and saved elsewhere than on the Vera, a factory reset or replacement of the Vera would also lose the only backup available, and require the user to rebuild all ReactorSensors manually. Therefore, downloading and archiving your Reactor configuration any time you've completed important changes is highly recommended.
When downloading backup files, modify the filename to include the date, and perhaps even time. I like to use YYMMDD or YYMMDD-HHMM format (e.g.
reactor-config-backup-181130.json), since it ends up sorted properly by date in the alphabetical file listings.
Reactor backups are fast and cheap! Back up before making big changes to your ReactorSensor configurations--if it doesn't go well, you can easily revert back to the last known good version. Once you finish your work and you are satisfied with the results, back that up, too, and download the file for safe keeping.
Restoring from Backup
The Restore button restores the last configuration backup (stored on the Vera as
/etc/cmh-ludl/ on Vera or the directory in which Reactor is installed on openLuup), if it exists. You may restore the entire configuration, or just that of a single ReactorSensor.
When restoring "ALL" configurations, Reactor will attempt to find the target ReactorSensor for each configuration by searching for an existing ReactorSensor with the same name as the configuration; if it is not found, the restore is not performed, so if you are restoring after a factory reset of your Vera, for example, it may be necessary to create multiple sensors and then rename them prior to attempting the restore. Alternately, you may do a "directed restore," in which you choose a single configuration to restore from those available in the backup file, and specify the target ReactorSensor to which the configuration will be restored. In this latter case, the name of the target sensor is not relevant, because you are telling Reactor explicitly where to save the configuration.
The restore process takes several steps. Make sure to stay on the Backup and Restore tab until all of the restore steps report "done." A hard-refresh of your browser is then required to ensure that the restored configurations are properly displayed by the user interface.
Renumbered devices... no easy way
Restoring ReactorSensors does not "fix" device numbers in conditions, expressions, and activities. The same applies for scene numbers in "Run Scene" activities. You'll need to go through the configuration and fix these yourself, although they should be easy to find--Reactor marks these items "missing" in the various configuration tabs, and displays the last known name of the device is many cases.
Restoring from an Archived Backup File
If you have an older backup file from which you need to restore configuration, here is the procedure:
- Make a current backup, and download the current backup file (see above). This ensures you have a current snapshot before moving forward, as a precaution should you take a misstep in this procedure and need to reverse it.
- Make a copy of your archived file and name the copy
- Use the uploader at Apps > Develop apps > Luup files to upload the file created in the previous step. openLuup users can use scp, ftp, or whatever other tool you normally prefer to transfer the file into the same directory as that in which the Reactor plugin files are installed.
- Go to the Backup and Restore tab on the Reactor master device. You should now see that the "current backup" is reported with the date of your archived backup. You may proceed with your restore as usual.
- You may want to take a final backup after all of this, to capture the configuration in its new current state.