1010 on a Sigenergy SigenStor: Grid power outage. Official suggestion (summarised): Reconnects automatically when grid normal; check AC switch/breaker; confirm off-grid function enabled; ID2 clear manually in app alarm page after checking site
Short answer
On a Sigenergy inverter, 1010 means: Grid power outage. Official suggestion (summarised): Reconnects automatically when grid normal; check AC switch/breaker; confirm off-grid function enabled; ID2 clear manually in app alarm page after checking site. The inverter stops until the fault clears or is reset. An engineer is needed to fix the cause.
Reviewed 24 September 2026 · 1 source
What it means
The manual says: Grid power outage. Official suggestion (summarised): Reconnects automatically when grid normal; check AC switch/breaker; confirm off-grid function enabled; ID2 clear manually in app alarm page after checking site.
Likely causes:
- Grid outage or AC switch off; ID2 = unit remains shut down after an earlier outage.
Is it safe?
| Does the inverter stop? | Yes |
|---|---|
| Severity | Fault — clears by itself when the condition goes |
| Engineer needed? | Yes |
The inverter stops until the fault clears or is reset.
Resetting itself: ID2 lock: yes (clear in app).
Manual reset: n/a.
What you can check
- Read the alarm code, name and ID in the mySigen app.
- Report it via mySigen app Support > Troubleshooting (Sigenergy's stated route) or contact your installer.
- Check the AC isolator and the consumer-unit breaker feeding the system are on.
- Check whether there is a local power cut (DNO 105).
- For ID2 'grid power failure lock', clear the alarm in the mySigen app alarm page once power is back.
What the engineer will check
- Check off-grid/backup configuration.
- Sub-IDs: ID1 grid power outage; ID2 grid power failure lock.
Who to ask for: battery storage / PV inverter.
Certification: Sigenergy-trained installer; MCS PV/battery installer for certified installs; electrical work to BS 7671.
What you might notice
Sources
- Sigenergy Alarm List (Version 05) ↗ · 05 · Reviewed 24 September 2026
A code explains what the controller detected, not a confirmed root cause.
Reviewed: 24 September 2026