Appearance
Export your data
Your readings and alarms belong to your tenant. You can download them as ordinary files without a support ticket. Devices speak standard MQTT and HTTP, so firmware can be pointed at another broker when you leave.
A single “export whole tenant” archive is not available yet. Use the steps below for what you need today. A fuller tenant export is planned later.
Readings (CSV)
- Open Reports.
- Create or open a Readings export.
- Set the time range and pick devices, an asset, a device profile, or a device type.
- Choose the telemetry keys you need.
- Click Download (or Send now / schedule if tenant mail is connected).
The file is CSV. See Reports.
Alarms (CSV)
- Open Reports.
- Create or open an Alarms export.
- Set the time range and optional severity / status filters.
- Click Download.
Configuration (JSON) — Export / Import
Each of these screens has Export JSON (or Export tree) and Import. Use them to back up a board or move configuration into another Autoconnecto tenant. Name clashes save as “… (copy)”.
| What | Where | Notes |
|---|---|---|
| Dashboards | Dashboards → row menu → Export JSON; Import on the list | Widgets and layout. Re-bind devices/aliases if needed. |
| Device profiles | Device Profiles → row menu → Export JSON; Import | Alarm rules and calculated fields. Rule-engine link is cleared on import — attach an engine again. |
| Rule engines | Rule Engines → Export; Import | Imports as draft. Passwords, tokens, and auth headers are cleared — re-enter secrets. |
| SCADA boards | SCADA Boards → Export; Import | Mimic document. Device bindings may need re-pointing on another tenant. |
| Assets tree | Assets → Export tree (whole tenant) or row Export (one SITE/AREA/ZONE and its children); Import | SITE → AREA → ZONE hierarchy (and site numbers). Devices are not moved. |
| Scheduler | Scheduler → Export; Import | Imports as draft with devices cleared. Pick devices (and engine, if used) before Activate — Activate stays off until at least one device is set. |
See also Dashboards.
Other useful downloads
| What | Where |
|---|---|
| Audit log | Audit → Export matching (CSV) |
| Analytics ranking | Analytics → Fleet check → Export CSV |
| Trips | Trip Ops / trips export when that Solution is in use |
Devices (move the fleet)
- Note each device’s type, name, and how it publishes (MQTT topics or HTTP path) from Devices and Check connectivity.
- On the device or gateway, change the broker URL / host and credentials to the new platform.
- Keep the same payload shape your firmware already uses, or adapt once in firmware.
There is no proprietary device wire protocol. The ESP32 SDK and HTTP examples use documented topics and JSON.
API (scripted pull)
Authenticated REST under api.autoconnecto.in (Swagger in the app under Documentation, or API overview). Use it when Reports windows are too small for a one-shot history pull — page by time range into CSV or JSON on your side. The same Import endpoints used by the app are available under each resource’s /import path.
Stay on Autoconnecto off our cloud
If the goal is to leave hosted cloud but keep the same product, ask about on-prem / own server (Docker Compose + licence). That is a deploy choice, not an export.
Coming later
Full tenant export (devices, assets, profiles, dashboards, and a readings window in one archive) is planned. Until then, use Reports + the JSON Export/Import steps above + the API for history and configuration you need to keep.
