Skip to content

June 2026

Changes released in June 2026.

Open in the full timeline

Web appImprovements and fixesNetwork & remote access

The status dots of data loggers and network devices now follow the live readings. A device that went down no longer shows green.

  • When a device's web page cannot be opened through remote access, a Mirox page names the reason instead of a raw error.
  • Each of a device's web pages can be given its own login, separate from the device login.
  • Devices that block unfamiliar addresses, such as a FRITZ!Box with rebind protection, can now be opened as well.
  • On a plant's "Market" tab, "Accounting country" can now be set to "None" for a plant without EEG accounting, which hides the EEG values.
  • A QReader data logger's value mapping now offers "By External (W)", a power limit set by external control in watts, optionally tied to a segment.
mirox 2.14.137 – 2.14.141
Read more in the documentationProxyData loggers
Web appBreaking changeMajorNetwork & remote access

A connected site's tunnel address is now assigned automatically

A connected site added to a plant's remote access no longer asks for a tunnel address, which is now assigned. Connected sites that already exist keep their current address.

Action required: Organization admins and technicians who set up remote access: when you add a connected site, take its tunnel address from the configuration you download instead of choosing one, and use that address when you configure the remote router. Connected sites that already exist are untouched and keep their current address, so nothing has to be changed on routers that are already connected.

mirox 2.14.75 – 2.14.76
Read more in the documentationVPN
Web appImprovements and fixesNetwork & remote access

Strings added by hand can now be deleted, and a network scan that finds nothing says why.

  • Strings added by hand can be selected on the components page and deleted after a confirmation prompt, while detected strings stay.
  • A network scan that finds nothing now says whether it could not reach the plant network or the scanned range held no devices.
  • All address ranges of a direct remote-access connection are edited in one list and saved together; ranges already used on the plant are flagged.
  • A plant's on-site agent keeps running when the plant is removed from an organization's remote access or that remote access is deleted.
mirox 2.14.57 – 2.14.67
Read more in the documentationComponentsVPNRemote access
Web appImprovements and fixesNetwork & remote access

The day power chart now marks only connection losses that really happened and names the remote access connection that dropped. The record of remote access activity opens on the most recent weeks.

  • On a plant without remote access, the day power chart no longer marks the whole day as a lost connection.
  • Where a connection really dropped, the chart now names the remote access connections affected, or states that their state is unknown.
  • The record of remote access activity opens on the most recent weeks, and the weekday labels stay in place while scrolling.
mirox 2.14.55
Web appFeatureNetwork & remote access

WireGuard remote access can now use a pre-shared key

A WireGuard remote-access server created on a plant now has "Require a pre-shared key" on by default, and the connected site receives an extra generated key alongside its keypair, shown once right after creation. For an existing connection, "Include a pre-shared key" adds, renews or removes the key when its configuration is regenerated.

mirox 2.14.26 – 2.14.37
Web appFeatureNetwork & remote access

Network scans now take a range and show devices as found

Starting a network scan on a plant's networking page now opens a dialog where "Scan range (optional)" limits the scan to part of the network and "Overwrite existing names" replaces device names with the latest analysis. Found devices appear in the table while the scan runs, filling in as they are identified.

mirox 2.14.26 – 2.14.37