November 2026
Changes released in November 2026.
Detected capacity no longer reads above the nameplate
A plant's detected capacity no longer reads above its nameplate when a group of shaded strings at half current makes healthy single strings count as parallel rows. For affected plants the detected capacity moves down toward the nameplate. Plants receive this with their next agent update.
A plant controller can now be added as a data logger
A plant controller can now be added as a data logger, with the on-site agent reading the power, energy, operating state, string positions and fault codes of the plant's string inverters. Plants receive this with their next agent update.
A device's web page over remote access loads when its stored port answers only with an error. A device whose web interface port was stored wrong needs one scan of its web interface first.
- A restarted on-site agent connects to the platform at once instead of waiting up to 3 minutes.
A stopped unit's fault event closes once the unit produces again
A stopped unit's fault event previously stayed open for a day or more after the unit recovered. It now closes once the unit produces again. Plants receive this with their next agent update.
The components page no longer marks a string as not connected
A string that produced no energy on one day but energy within the last 30 days is no longer marked as not connected. The not-connected mark now uses the same 30-day energy window as the "probably not connected" badge on the components page. Plants receive this with their next agent update.
In a plant's event list, the no-communication summary updates again.
Device faults standing for days are raised once, not every night; a silent tracker raises its event after 20 minutes.
- A device fault that stands for days is now raised once, not each night.
- A silent tracker now raises its no-communication event after 20 minutes, not 15.
- A condition the on-site agent retracted no longer announces a resolution.
The month-to-date yield no longer counts the previous day twice
A solar data logger's month-to-date yield previously counted the previous day's production again on the first day of a new month, inflating the lifetime energy sum. The repeated production is no longer published, and figures already issued keep their value. Plants receive this with their next agent update.
False offline and unreachable alerts, false fault events and false data holds no longer fire on loggers, inverters and battery historians. An inverter fault that re-raises after its first raise now opens its fault event again.
- A plant no longer reads offline after a brief network link drop.
- A data logger's month-to-date yield no longer opens a false mismatch on a late step.
- A data logger is no longer alerted unreachable while the plant's network link is pending.
- A data logger outage is now reported once per episode.
- A battery historian's cell voltages are no longer withheld as "not fed".
In a plant's event list, DC measurement-defect, tracker and battery events no longer repeat. In an export, frozen lifetime-energy totals are not shown.
- In a plant's event list, DC measurement-defect descriptions now name the faulty DC reading.
- In a plant's event list, tracker silence and fault-stop events no longer repeat at night.
- In a plant's event list, a battery unit at rest no longer posts a state change every night.
- A data logger whose device list could not be read no longer reports its inverters as missing.
- In an export, a lifetime-energy total frozen at its maximum value is no longer shown.