MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Loss Detection
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Permission System
    • Cooperation Restrictions
    • Access Audit Logging
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Loss Detection
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Permission System
    • Cooperation Restrictions
    • Access Audit Logging
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Grafana
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Getting Started

    • First Steps
  • Personal

    • Using the VPN
    • Using the Proxy
    • Setting Up Two-Factor Authentication
    • Managing Your Sessions
    • API Tokens
  • Per Park

    • Managing Plant Contacts
    • Managing Network Devices
    • Configuring Data Loggers
    • Configuring Components
    • Configuring VPN Servers per Agent (Direct VPN)
  • Organization

    • Managing Member Permissions
    • Creating Cooperations
    • Using File Storage
  • Data Export

    • Export Metric API
    • MiroxQL Query Language
    • External Report Generation
    • Using Grafana as an External Read Platform
    • API Overview
  • Support

    • Request Integration Guide
  • mrxnode

    • mrxnode Overview
    • mrxnode How-To Guide
    • Container Deployment
    • mrxnode Command Cheatsheet
    • Troubleshooting

Configuring Components

The Components page is where you describe the physical make-up of a plant — its inverters, combiner boxes, strings, irradiation sensors, and feed-in meters — so the platform knows what it is monitoring. Getting this configuration right is what turns raw measurements into a clear-sky simulation, a performance ratio, loss detection, and string-level analysis. This guide walks you through each task and explains what your edits actually drive.

Where it lives

Open your plant's Components section in Mirox (in the app: open a plant from your plants, then its Components section). The tabs across the top — Stromzähler (feed-in meter), Irradiation, Inverter, Combiner Box, and Strings — group every component type.

Why Configuration Matters

The Components page is not just an inventory. The numbers you enter here become the reference the Digital Twin compares live telemetry against:

  • Clear-sky simulation uses each string's panel datasheet, azimuth, tilt, and panel count to model the energy a string should produce under clear skies.
  • Performance ratio and degradation are measured against the configured peak power, so an under- or over-stated peak power skews every efficiency figure.
  • Loss detection attributes shortfalls to specific components — it can only do that if the component tree is complete and correctly mapped.
  • String analysis and the component states (producing normal, degraded, inferred, and so on) depend on the same configuration.

Keep configured power and string power in agreement

A power mismatch — where the plant's configured peak power does not equal the sum of its strings — degrades digital-twin accuracy. The Review Status card flags it, and you should resolve it before relying on the analysis (see Check the Review Status).

Read the Status Cards

Above the tabs, three cards summarize the plant's configuration health:

  • Peak Power — the configured peak production of the plant.
  • System Metrics — current system-level figures, including the logger count.
  • Review Status — how complete and consistent the configuration is (covered below).

Configure Inverters

Open the Inverter tab. Each row is an inverter the platform has discovered or that you added. Click a row to open its detail drawer, where you can:

  1. Assign a datasheet. Pick the inverter model from the Datasheet dropdown. The datasheet supplies the manufacturer, model, rated peak performance, and efficiency figures shown below the selector.
  2. Add notes. Use the Information field for any free-text context (service history, location, quirks).
  3. Mark as hidden. Toggle Mark as Hidden to remove a decommissioned or duplicate inverter from the main view. Use the Show Hidden switch on the tab to bring hidden items back temporarily.
  4. Click Save.

The drawer also shows read-only state — connected strings, combiner boxes, panel count, connected peak power, status, last-seen time, and discovery source. Use the Connected Components cards to jump straight to that inverter's combiner boxes or strings.

Auto-detection fills the name

An inverter with no name shows a "Waiting for Auto-Detection" placeholder and is named automatically once data arrives. Clearing a name with the eraser hands it back to auto-detection.

Add Combiner Boxes

If a plant routes its strings through combiner boxes (Generatoranschlusskästen), add them so the string tree matches reality. The Combiner Box tab only appears once a plant has at least one.

  1. On the Inverter, Combiner Box, or Strings tab, click Add Combiner Box.
  2. Select the parent Inverter.
  3. Enter the Number of Combiner Boxes to create (1–50) and, optionally, a Name Prefix (for example GAK-).
  4. Click Save.

Add and Configure Strings

Strings carry the panel configuration that drives the clear-sky model, so this is the most impactful part of the page. Open the Strings tab (filter by inverter, and by combiner box where present, to narrow the list).

Add strings

  1. Click Add String.
  2. Choose the target — To Inverter or To Combiner Box — and select one or more targets.
  3. Fill in the string configuration:
    • Number of Strings — how many identical strings to create per target.
    • Panel Datasheet — the panel model; its rated power feeds the peak-power calculation.
    • Azimuth — orientation in degrees (0–360, where 180 = South).
    • Tilt — angle in degrees (0–90).
    • Panels per Row and Parallel Rows — together these define how many panels each string carries.
  4. The dialog previews the estimated peak power you are about to add, computed from the panel rating and counts. Click Save.

Edit strings in bulk

  1. Select one or more strings in the table (or none, to apply to a wider scope).
  2. Click Edit.
  3. Adjust the panel datasheet, azimuth, tilt, or panels in series.
  4. Choose the scope under Apply changes to — Selected Strings, All Strings in Combiner Box, All Strings in Inverter, or All Strings in Park.
  5. Toggle Mark as Verified once a string's configuration is confirmed correct, then Save.

Verify as you go

Marking strings verified is how you track which configuration you have reviewed. The Review Status card counts verified versus pending strings, so a verified plant reads "All Good".

Check the Review Status

The Review Status card tells you whether the configuration is complete and self-consistent:

  • A verified percentage and pie chart show how many visible strings you have confirmed.
  • A power comparison shows the configured Expected peak power against the Strings total, and the Offset between them. When they match, it reads Power Matching.
  • When something is off, the card shows {n} pending strings to review and/or a Power mismatch warning. Click Review to jump to the pending strings, fix the configuration, and mark them verified. If the totals are correct but the expected peak power is wrong, adjust the expected peak power in the plant's core data settings instead.

Once every string is verified and the power matches, the card reads All Good and offers a Deep Analysis action that asks the agent to re-evaluate the plant with the corrected configuration.

Other Component Types

  • Irradiation — the irradiation sensors used as the production reference. Click a row to view sensor details.
  • Stromzähler (Feed-in Meter) — the meters that measure energy fed to the grid. Click a row to view meter details.

Related Guides

  • Component States — the operational states the Digital Twin assigns to the components you configure here
  • Digital Twin — the engine that turns this configuration plus live telemetry into monitoring insight
  • Loss Detection — how a complete, correct component tree lets shortfalls be attributed to a specific string or inverter
  • Solar Plants — the supported solar configurations and the parameters Mirox monitors
  • Configuring Data Loggers — map discovered devices so components start reporting data
Prev
Configuring Data Loggers
Next
Configuring VPN Servers per Agent (Direct VPN)
MIT Licensed | Copyright 2026 Mirox Verwaltungs GmbH