Storage And Logs
Files, logs, and support evidence
Storage shows persisted device files, while logs explain what happened during polling,
commands, scenarios, and service work. This is the main evidence source for diagnostics.
Storage, Modbus Log, and Scenario Log
| Area |
Shows |
Open it when |
| Storage |
Configuration files, device profiles, and service data on SPIFFS and SD Card. |
You need to verify what is actually stored on the device. |
| Modbus Log |
Polling and command history grouped by folder and file. |
A device does not respond, values are stale, or a command fails. |
| Scenario Log |
Automation execution history. |
You need to understand why a rule did or did not run. |
Storage as persisted truth
Storage does not replace Setup, but it lets service engineers see which files are really stored on the device.
Use Setup for normal changes. Use Storage for checking, downloading, analysis, and careful service work.
SPIFFS and SD Card
| Medium |
Role |
Notes |
| SPIFFS |
Internal device storage. |
Always available, but limited. Polling logs may rotate by free-space pressure. |
| SD Card |
Main place for larger logs and service data when mounted. |
Common runtime/event logs are stored only on SD. With SD active, some SPIFFS logging controls become disabled. |
How to read Modbus Log
The current UI separates folder navigation from file operations: choose the folder or area on the left,
then work with files and actions on the right. This makes deep log structures easier to use.
Choose the line
Use RTU 1, RTU 2, or TCP. TCP is bus3 and must not be replaced by RTU 1 data.
Open a folder in the tree
The tree shows storage structure. Files and actions remain in the right pane.
Select a file
Check date, size, and device context. If the log is needed for support, download it before cleanup.
Switch Table / Charts
Table view is better for exact events. Charts are better for value dynamics.
What to collect before support escalation
- Control screenshot with the selected device and visible state.
- Modbus Log file for the affected line and device.
- Scenario Log if automation is involved.
- Settings screenshot showing line mode, MQTT/gateway, and storage state.
- Device configuration files from Storage if the issue survives reboot.
Safe actions
| Action |
Use when |
Risk |
| Download |
Before service work, deletion, or sending evidence to support. |
Low. Check that the file does not expose secrets. |
| Refresh |
After settings changes, reboot, or a long wait. |
Low. It may reveal a newer tree state. |
| Delete |
Only when the file is not needed or consumes space. |
High for configuration. Download first. |
| Edit |
For service correction when Setup is not suitable. |
High. Invalid JSON can break configuration loading. |
