Configuring Data Loggers

Data loggers are the bridge between the equipment at your plant and the Mirox platform: once a logger is configured, the Mirox-Agent starts polling that device on a schedule, normalizing every reading into a single metric vocabulary and streaming it into the platform. This guide walks you through adding a logger, mapping a discovered device to an adapter, confirming it responds with a live probe, and applying your changes — plus the limits of what onboards automatically.

Where Data Loggers Live

Every plant has a Data flow page where you manage its loggers and watch data come in.

Open in Mirox: Data flow — or open Your plants, pick a plant, and switch to the Data flow tab.

The page header shows live tiles for logger health (healthy vs. total), Agent availability, and network traffic, so you can see at a glance whether collection is working. The Data Loggers tab is where you add and manage loggers; the Apply changes button at the top right pushes your configuration to the Agent.

How Data Loggers Are Onboarded

Adding a logger is a guided flow built around a real conversation with the device. The platform opens a temporary read-only connection — a probe — so you can confirm the device responds and see its live readings before you commit anything. There are two ways into the flow:

• Possible Loggers (auto-detected) — when a discovered device's vendor and type match a known adapter, it appears in the Possible Loggers table with the matching adapter pre-filled. This is the fast path.
• Add Logger (manual) — when detection misses or misclassifies a device, the Add Logger button lets you pick any network device and an adapter yourself.

Either way, the same wizard runs and the same live probe confirms the device before you save.

Adding an Auto-Detected Logger

1. Open in Mirox: Data flow (or pick your plant under Your plants and open the Data flow tab).
2. In the Possible Loggers table, find the device you want. Each row shows the device name, IP, vendor/type, and the adapter the platform matched it to.
3. Click the + button on the row. The onboarding wizard opens with that device and adapter already bound.
4. Follow the wizard steps (below) and Save the logger.

Adding a Logger Manually

1. On the Data flow page, click Add Logger.
2. On the Pick device step, search the network-device list by name, IP, vendor, type, model, or description, and select the device.
3. Choose the adapter to use, then click Continue.
4. Follow the remaining wizard steps and Save the logger.

The Onboarding Wizard, Step by Step

The wizard is a single dialog with a sidebar of steps and a live agent-log strip along the bottom, so you can watch the Agent talk to the device the whole time. A connection badge next to the device name reports the probe state (Connecting, Probing, Idle, Error, Done). Which steps appear depends on the adapter:

Credentials and the Vault

If the adapter needs to sign in to the device, the Credentials step asks for a username and password. Credentials you have already stored for that device in the credential vault are offered here so you don't re-type them, and what you enter can be reused for proxy access later.

Running the Live Probe

The Probe step opens a short-lived dry run against the device. The Agent reads what the device exposes and streams live samples back — they refresh every second, and the bottom log strip shows the underlying exchange.

• Wait until samples appear. The connection badge moves to Probing and then settles once readings are flowing.
• If nothing arrives, the wizard retries automatically a few times. If it still can't reach the device, you'll get a clear message and a Reconnect button to try again.
• A stalled probe almost always means the device isn't reachable from the Agent — check that discovery still sees it and that the VPN tunnel is up.

Mapping a Generic Logger's Values

Some loggers are generic — they expose a long list of raw values the platform can't interpret on its own (a power meter, a pyranometer, and a dozen other channels behind one device, each named in the device's own vocabulary). For these, the wizard runs an interactive mapping flow instead of a read-only preview:

1. On the Map values step the Agent enumerates every raw value the device exposes and streams them back with their group, name, unit, and a live sample. You get a searchable table.
2. For each raw value you care about, pick the known metric it represents from the dropdown. Leave the rest unmapped. You can invert a sign per value where needed; unit prefixes (kW, kWh, …) are rescaled to base SI automatically.
3. The Dry run step re-runs the device through your mapping and shows the exact metrics that would be produced — your accept/deny checkpoint.
4. Summary confirms what will be saved.

Only the values you map are collected, and each raw value maps to exactly one metric.

Mapping Readings (Manual Override Adapters)

For non-generic adapters that still expose a configuration step, the Configuration step shows every reading the probe found and lets you choose which to collect, set the polling interval, and apply per-reading corrections (for example, inverting a sign). When you continue, the platform re-probes with your configuration so the Summary step shows the values exactly as they'll be stored.

Saving

On the final step — Summary for manual adapters, or the Probe step itself for zero-config devices — click Save logger (or Add for zero-config). The logger is saved as a pending change. Nothing reaches the Agent yet.

Applying Your Changes

New loggers, edits, and removals are staged until you publish them to the Agent in one batch.

1. Make all the logger changes you want.
2. Click Apply changes at the top of the Data flow page (it reads Apply N pending change(s) when you've queued some this session).
3. The Agent redeploys with the new configuration and starts collecting shortly after.

Managing Existing Loggers

The Data Loggers table lists everything configured for the plant, with search, sorting, and health per logger. The ⋮ action menu on each row lets you:

• Edit logger — adjust the logger's configuration.
• Edit network device — jump to the device on the Networking page to change its IP, credentials, SNMP, or proxy settings (these live in one place, not duplicated here).
• Pause / Resume — temporarily stop collection for a chosen window (15 minutes up to 24 hours) and resume it. Useful during maintenance so a known outage doesn't raise events.
• Remove logger — delete a logger you added through the wizard.

Removing or pausing a logger is also a pending change — remember to Apply changes afterward.

What Can Be Onboarded Through the Wizard

Two kinds of device onboard through the wizard:

• Zero-config families — the adapter already knows the device's full reading set, so you only confirm the live probe and save. Today these are Janitza meters (no credentials needed), Huawei SmartLogger, and Phoenix Contact controllers.
• Generic loggers — devices that expose arbitrary raw values the platform can't interpret on its own. These onboard through the interactive Map values → Dry run flow described above, where you bind each raw value to a known metric. QReader is the first generic logger supported this way.

Device families outside both groups still work, but they aren't wizard-onboardable today: they need a per-device configuration that Mirox prepares and ships with the Agent. Treat onboarding automation as device-specific, not universal.

To understand how adapters speak each device's protocol, normalize units, and discover components, see the Data Scraper architecture page — this guide deliberately doesn't repeat it.

Related Guides

• Managing Network Devices — discover and classify the devices a logger is configured against
• Configuring Components — map collected metrics onto inverters, strings, and combiner boxes
• Data Scraper — how adapters collect, normalize, and forward your data
• Request an Integration — ask Mirox to add an adapter for an unsupported device
• Using the Proxy — open a device's own web interface in the browser using stored credentials