Configuration Backup and File APIs
The current release has no standalone File Manager menu. To back up or migrate configuration, open Device Configuration > Advanced Configuration > Configuration Import/Export. This workflow handles known JSON configuration files and does not expose arbitrary LittleFS browsing or online editing, reducing Web assets and device memory use.
Back Up Configuration
- Sign in to the device Web console and open Device Configuration > Advanced Configuration.
- Select Export and choose only the configuration files required for the backup.
- Record the board model and firmware version with the download, and protect files that contain network or platform credentials.
Common files include:
| File | Content |
|---|---|
device.json | Device identity, time, and logging settings |
network.json | WiFi, static IP, and compiled network module settings |
features.json | Runtime feature switches |
protocol.json | MQTT and Modbus RTU settings |
peripherals.json | Peripheral definitions, pins, and parameters |
periph_exec.json | Peripheral execution rules |
rule_scripts.json | Rule scripts |
The export dialog is the source of truth for files available on a device. Pins, Flash partitions, and compiled capabilities differ by board, so do not overwrite one hardware type with a complete bundle from another hardware type.
Restore Configuration
- Export the target device's current configuration as a rollback backup.
- In Device Configuration > Advanced Configuration, select one JSON file or a FastBee configuration bundle.
- Select Import and choose only the entries that should be replaced.
- Restart when prompted, then verify Network, Peripherals, Peripheral Execution, and Protocols.
If import fails, check the JSON syntax, file name, and available device memory. For a 503 response, follow Retry-After; do not repeatedly refresh or resubmit.
File APIs for Custom Firmware
The source still contains /api/files, /api/files/content, /api/files/save, and /api/filesystem. They are registered only when a custom build explicitly sets FASTBEE_ENABLE_FILE_MANAGER=1. Current release environments keep this feature disabled and provide no matching Web page.
These authenticated endpoints are intended for custom diagnostic or integration tools. Normal configuration migration should use /api/config/transfer/*; do not depend on the file APIs or expose arbitrary path writes.