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

mrxnode Overview

Your mrxnode is an edge device that connects on-site hardware to the Mirox platform. This guide walks you through accessing the device, registering it with the cloud, activating applications, and building an edge cluster.

Device Setup

Connecting via SSH

To access your mrxnode device, connect via SSH using the device's IP address.

ssh appuser@<device-ip>

Login Credentials:

UsernamePasswordPurpose
appusermirox (unregistered) / Device UID (registered)Customer access
mrxuserDevice TokenSystem administrator access

Password Change

Once the device is registered with a Mirox platform, the appuser default password is automatically replaced with the device's unique UID for security.

First Login

When you connect to a fresh or unregistered device, you will see the following banner:

  ███╗   ███╗██╗██████╗  ██████╗ ██╗  ██╗    ██████╗ ███████╗
  ████╗ ████║██║██╔══██╗██╔═══██╗╚██╗██╔╝   ██╔═══██╗██╔════╝
  ██╔████╔██║██║██████╔╝██║   ██║ ╚███╔╝    ██║   ██║███████╗
  ██║╚██╔╝██║██║██╔══██╗██║   ██║ ██╔██╗    ██║   ██║╚════██║
  ██║ ╚═╝ ██║██║██║  ██║╚██████╔╝██╔╝ ██╗   ╚██████╔╝███████║
  ╚═╝     ╚═╝╚═╝╚═╝  ╚═╝ ╚═════╝ ╚═╝  ╚═╝    ╚═════╝ ╚══════╝

Welcome to mrxnode - an Edge-Node for the Mirox Platform

==========================================
    CLOUD REGISTRATION REQUIRED
==========================================

This device must be registered before use.

To register:
  mrxcloud register <service>.<domain>

Example:
  mrxcloud register myservice.mirox.io

After registration, reboot the device.
==========================================

Registering the Device

Recovery Mode Required

Device registration is only possible when booted into recovery mode. Fresh devices boot into recovery by default.

Re-registering a Device

If the device is already registered to a platform, you must unregister it first using mrxcloud unregister.

If the device was previously registered but not properly unregistered from the platform (e.g., device was reset), the registration command will fail. In this case, you must delete the device from the platform first to clear its registration before re-registering.

To register your device with the Mirox SaaS platform:

mrxcloud register service.mirox.io

For a complete list of mrxcloud commands, see the Command Cheatsheet.

After successful registration, switch to the main system slot and reboot:

mrxos switch A
sudo reboot

The device will now boot into Slot A with the registered configuration.

Setup Application Usage

After registration, activate the Generic Relay application to control the HAT hardware:

sudo mrxhat activate generic-relay

Verify the activation status:

sudo mrxhat status

For a complete list of mrxhat commands, see the Command Cheatsheet.

Edge Cluster Setup

To run a K3s cluster on your mrxnode devices, additional setup is required.

Prerequisites (SaaS)

Before initializing a device as an edge node, complete these steps in the SaaS:

  1. Register the device - The device must be registered with the cloud
  2. Assign device to a park - The device must be assigned to a park
  3. Create edge cluster - An edge cluster must be created for the park

Step 1: Initialize Node (Recovery Mode)

In recovery mode, initialize the device as an edge node:

sudo mrxcloud node init

The device automatically receives:

  • The park assignment from the SaaS
  • A unique edge node number

Step 2: Start K3s Cluster (Normal Mode)

After rebooting into the normal system, initialize the cluster:

sudo mrxnode init

Node 1 creates a new cluster. Additional nodes join the existing cluster.

Step 3: Bootstrap FluxCD

After successful cluster initialization, set up FluxCD:

sudo mrxnode bootstrap

FluxCD automatically synchronizes configurations from the OCI registry.

Check Status

# Check cloud connection and registration
sudo mrxcloud status

# Show node configuration
sudo mrxcloud node info

# Check K3s and FluxCD status
sudo mrxnode check

# Show FluxCD sync status
sudo mrxnode flux-status

Related Features

  • Command Cheatsheet — full reference for mrxcloud, mrxos, mrxnode, and mrxhat
  • How-To Guide — network and disk configuration tasks for your device
  • Container Deployment — deploy and manage containers on the device
  • Troubleshooting — power-button recovery and common fixes
  • Edge Cluster Orchestration — how devices are managed as an edge cluster from the platform
  • Generic Relay — control HAT relay hardware from a registered device
Next
mrxnode How-To Guide
MIT Licensed | Copyright 2026 Mirox Verwaltungs GmbH