Before a change

Record the current firmware, serial number, network access method, port modes, and one known-good integration test. Arrange a maintenance window for changes that restart services or the unit. Keep a copy of the point definitions and installation wiring/address list.

1. Save the appropriate configuration

Use “Back up configuration” in the SB1000 web interface's Device Settings. Complete any authentication/unlock step and confirm that the .sbb file was downloaded. Label it with the installation, serial number, firmware, and date.

Store a configuration backup as sensitive installation data: it can contain network and credential settings. Do not attach it to a public issue or send it as an ordinary unreviewed diagnostic export.

An NFC .varibitsconfig template is a reusable selection of supported settings. It omits secrets or asks for them and does not replace the device's configuration backup.

2. Update firmware

1. Use the update workflow offered by the device and the firmware intended for SB1000. Check the target version and release notes.
2. Maintain reliable power and a stable local connection during upload. Close unnecessary sessions and avoid simultaneous configuration changes.
3. Start the update and allow the device to complete it and restart. A temporary disconnected page can be expected during reboot.
4. Reconnect using the configured address and verify the running firmware version before retrying an upload that appeared to lose its connection.
5. Recheck the intended operating modes and the known-good integration test.

Do not assume an upload failure message proves the old firmware is still running. If the unit remains unreachable, first check power/link, the current address, and any reported update result. Use the documented recovery procedure for that release or contact support instead of improvising a factory reset.

3. Restore deliberately

Restoring a .sbb configuration replaces current settings and point/device maps and then reboots the unit. The web interface describes the scope before confirming. Factory-locked identity values such as the serial number are preserved; copied network or integration settings can still be inappropriate for the destination installation.

1. Confirm the backup belongs to the intended product and installation and is compatible with the target firmware.
2. Save the current configuration first if you may need to return to it.
3. Check the IP address and network details that will take effect, including duplicate-address risks when restoring to a replacement unit.
4. Choose the restore file, review the warning, and restore only the intended configuration.
5. Reconnect after reboot and verify both identity and integration behavior.

A restore is not a merge of just the settings you were viewing. A failed restore must be investigated from its reported error; do not repeatedly try unrelated backups.

4. Verify and hand over

Check one correct point in each active integration, source quality/freshness, the intended polling/cache settings, and required write/release behavior. Confirm commissioning has ended and test overrides have been removed.

Record firmware/app/client versions, actual IP/service ports, bus settings and Unit IDs, point-map revision, and the location of protected backups. Provide the operator with a clear way to regain local access.

When contacting support

Include the serial number, running/target firmware versions, exact error, time of the change, access method, and what still works. Share redacted screenshots and a minimal failed transaction first. Send a backup containing secrets only through an explicitly agreed support route.