Data and privacy in practice
Live readings go directly between OctoMonitor and EcoFlow
OctoMonitor connects to EcoFlow for supported REST and MQTT access, processes the response in the current app runtime, and retains supported history and configuration in this installation.
Telemetry history stays in this installation. Live readings and supported device commands still cross the network directly to EcoFlow; OctoMonitor adds no hosted telemetry cloud between them.
EcoFlow services
EcoFlow REST and MQTT provide supported live device readings, status refreshes, and control paths.
- EcoFlow API credentials
- Live device readings
- Supported device commands
OctoMonitor runtime
The browser, PWA, or native runtime maps readings, renders the interface, and evaluates enabled local rules.
- Processes readings in the active app
- Runs supported local rules
- No OctoMonitor telemetry cloud
Local app storage
Supported history and configuration stay with the current app installation unless you export or restore them yourself.
- Telemetry and report history
- Dashboards, notes, and solar setups
- Automations, schedules, and preferences
Ready to try OctoMonitor?
Open the app when you are ready to compare the guide with your own device and runtime.
Open OctoMonitor