You maintain plants from several brands and each one has its own portal. Alarms arrive scattered, in each portal’s own jargon and codes, and nobody knows which one is urgent. With Suntropy Connect, Alexandria reads all your brands and answers you in a single conversation.
Reads the portals of
HuaweiAlarm watch
Turn on the brands you want to watch. Suntropy reads their alarms periodically, every 10 to 30 minutes depending on what each manufacturer’s API allows, and keeps them for up to 30 days after they close. It flags new and closed ones, and keeps track of which ones you have read.
One scale for every brand
Each manufacturer classifies its alarms its own way. Suntropy normalises them to critical, major, minor and warning, and every alarm comes with the cause and the recommendation given by the manufacturer itself.
Monitoring overview
This is how Alexandria answers with the real data of a maintenance account with five connections. We have removed the names of customers and plants.
You have 62 plants from 4 brands across 5 connections, 1,047 kWp in total. 48 are healthy, 4 have an active fault and 10 are not reporting. This month they have produced 14,194 kWh, counting the 53 plants that report monthly data.
| Connection | Plants | kWp | Healthy | Fault | No comms | kWh month |
|---|---|---|---|---|---|---|
| 27 | 824 | 22 | 1 | 4 | 10.653 | |
| 17 | 119 | 12 | 2 | 3 | 2.819 | |
| 11 | 56 | 7 | 1 | 3 | 722 | |
| 6 | 45 | 6 | 0 | 0 | — | |
| 1 | 4 | 1 | 0 | 0 | — | |
| Total | 62 | 1.047 | 48 | 4 | 10 | 14.194 |
What I would look at first
By plant, the furthest off is the 15 kW one with the 2034: 0 kWh since the 8th. By connection, in kWh per installed kWp so far this month:
Careful not to read this as low production: in account 1 and in SolisCloud there are plants that are not reporting and add no kWh, but they do count towards the kWp. The average drops because of missing data. Before drawing conclusions, I would get those plants reporting again.
Diagnosis
A code doesn’t tell you what to do. Faced with an alarm, Alexandria works the way your back-office technician would, but with all the portal data at hand:
Code, the manufacturer’s description and the exact time it was triggered.
Real-time status of the plant and the inverter.
5-minute data: voltage per phase, frequency, strings and current.
Daily production before and after the alarm.
Ranked hypotheses, what is urgent and what to ask the customer before sending out a technician.
It used to produce about 89 kWh a day. Since 4 November it starts up and stops, and since the 8th it has produced nothing.
In the inverter’s 5-minute readings, phase C is well above the other two:
| Reading | A‑N | B‑N | C‑N | Phase to phase | Status |
|---|---|---|---|---|---|
| Mon 9 · 7:55 | 224,8 | 224,1 | 261,8 | 408,8 · 409,1 · 409,3 | Trying to start |
| Mon 9 · 12:10 | 219,9 | 220,6 | 265,3 | 406,0 · 404,1 · 406,8 | Stopped due to fault |
| Mon 9 · 15:00 | 223,5 | 223,3 | 272,8 | 413,1 · 413,1 · 413,9 | Stopped due to fault |
| Tue 10 · 7:50 | 218,6 | 222,8 | 266,3 | 406,3 · 405,9 · 407,9 | Stopped due to fault |
Voltages in volts, mainland Spain time. Frequency 49.97-50.03 Hz. Output power: 0 W.
What it is
The phase-to-phase voltages are normal (404-414 V): if the grid were high, they would rise too. What moves is each phase relative to neutral: C rises to 262-273 V while A and B drop to 219-225 V. It is a shifted neutral: loose or broken in the distribution board, at the inverter connection or upstream, at the service connection. The inverter sees overvoltage on phase C and disconnects, which is exactly what it should do.
Before you go, ask them
On the visit, measure
This is a real case from November 2026, with the readings exactly as FusionSolar returns them. We tell the whole story, with the reason behind every measurement, in Alarm 2034 “Grid Overvoltage” on Huawei.
More diagnoses, step by step
Compatibility
You connect each manufacturer’s installer account, the same one you use in their portal today. Each brand has its own way of granting access:
Huawei FusionSolarThe installer’s Northbound (API) account. Note: only plants whose owner has granted “API Access” appear.
How to request the API accountYour SEMS+ account.
Official OAuth authorisation. You choose which plants to share.
Deye’s official OpenAPI, EU region.
Monitoring Deye plantsKeyId and KeySecret from the SolisCloud API.
Partner plan with your own app, or Enlighten authorisation.
Read-only. Suntropy never writes or changes anything on the plants. The credentials for each account are stored encrypted.
How to get started
Signing up is free. Alexandria lives inside Suntropy, at app.suntropy.ai.
In Settings › Suntropy Connect › Connectors, add each manufacturer’s account.
“Which plants are failing today?” and from there, whatever you need.
With Alexandria (Suntropy AI), Suntropy Connect monitoring is free.
Frequently asked questions
No. Suntropy Connect reads the portals you already use (FusionSolar, SEMS+, iSolarCloud, Deye Cloud, SolisCloud, Enphase) with your installer account. You don’t change portal or inverter.
No. Access is read-only: Suntropy never writes or changes anything on the plants. Alexandria tells you what is happening and what to check; your team carries out the work.
Today, Huawei FusionSolar, GoodWe SEMS+, Sungrow iSolarCloud, Deye Cloud, SolisCloud (in beta) and Enphase. For each plant it reads the real-time status, energy, devices, the 5-minute history and the alarms.
Every 10 to 30 minutes, depending on what each manufacturer’s API allows. Alarms are kept for up to 30 days after they close, with their read or unread status.
In FusionSolar, the installer’s Northbound account only sees the plants whose owner has granted “API Access”. Ask the owner to enable it and the plant will appear.
Yes. Suntropy Connect also works as a connector in ChatGPT and Claude with a Suntropy Connect licence. If you use it with Alexandria, inside Suntropy AI, monitoring is free.
Suntropy AI
All your brands in one conversation: what is failing, why and what to do first.