Skip to content

Changelog

Every change to Mirox, grouped by month. Filter by group or by kind of change.

Clear filters

October 20268

AgentFixData collection

A data logger's device list is now read whole

A data logger that announced more devices than it delivered previously left the newest entry out of its list, so that device was never polled. The device list is now read whole, and a short list seen while running falls back to the logger's web interface. Plants receive this with their next agent update.

mirox-agents 3.2.194 – 3.2.196
AgentImprovements and fixesData collection

A battery storage system and a second generation of a solar data logger can now be added. Adding or updating several components of one plant at once no longer fails.

  • A second generation of a solar data logger can now be added, reading inverters and environment sensors behind it.
  • Adding or updating several components of one plant at once no longer fails for inverters, combiner boxes and strings.
  • Combiner boxes and strings now carry their own loss figures beside the inverter loss.
  • A feed-in meter's data now comes from the meter configured on the plant.
  • A manually added network device now gets one alive check in the network monitor, with an action to run it.
mirox 2.15.632 – 2.15.645mirox-agents 3.2.153 – 3.2.157

September 20268

AgentImprovements and fixesData collection

A wind plant without a feed-in meter now gets its production from the turbines' lifetime energy counters. It no longer raises a fault for the missing meter.

  • A battery's control signal now reads zero on its chart while the direct marketer is connected and asking for nothing.
  • A battery plant's settlement no longer drops quarter-hours after each restart of the on-site data collection.
mirox 2.15.468 – 2.15.483mirox-agents 3.2.67 – 3.2.72
Read more in the documentationData loggers
AgentImprovements and fixesData collection

Inverters behind a data logger are read again after a missed reply. Wind turbines and battery modules no longer read as offline for most of the day.

  • An inverter behind a data logger is read again after a missed reply, instead of dropping out of the data.
  • Wind turbines and battery modules no longer read as offline for most of the day while their connection is checked every 30 minutes.
  • A plant's mean irradiation no longer includes a reading higher than the sun can deliver.
mirox-agents 3.2.50 – 3.2.51
AgentImprovements and fixesData collection

Linyang battery alarms name their condition, Phoenix Contact WebVisit park controllers report their limits and setpoints, and blue'Log loggers stay connected at plants with many strings and sensors.

  • Alarms from Linyang containers now name the condition, such as a charge over-temperature, instead of only an alarm level.
  • A Phoenix Contact park controller with a WebVisit interface now reports grid and marketer limits, and the setpoints applied.
  • blue'Log loggers no longer drop in and out at plants with many strings and sensors.
mirox 2.15.397 – 2.15.406mirox-agents 3.1.449 – 3.1.454
Read more in the documentationData loggers
AgentImprovements and fixesData collection

Expected power is worked out again through stretches where irradiation readings were lost, and Huawei inverters now report model, firmware and rated power.

  • Irradiation sensors are no longer reported as sending nothing for hours at a time, and expected power and performance ratio are worked out again.
  • Huawei inverters now report their manufacturer, model, firmware version and rated power in their component details.
mirox-agents 3.1.445 – 3.1.446
Read more in the documentationComponents

August 20268

July 20266

June 20263

May 20263

April 20261

March 20261

January 20262