SolarpunkHomes
Sign inCall us · +44 7510 081687
Solar
Solar · Error codes · Sigenergy
1004Sigenergy · SigenStor (EC controller + BAT modules + Gateway)

1004 on a Sigenergy SigenStor: Equipment fault. Official suggestion (summarised): Standby/shutdown, open DC and AC switches, wait until fully powered down, restore and boot; if not cleared submit fault feedback

Short answer

On a Sigenergy inverter, 1004 means: Equipment fault. Official suggestion (summarised): Standby/shutdown, open DC and AC switches, wait until fully powered down, restore and boot; if not cleared submit fault feedback. 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: Equipment fault. Official suggestion (summarised): Standby/shutdown, open DC and AC switches, wait until fully powered down, restore and boot; if not cleared submit fault feedback.

Likely causes:

  • Internal circuit fault.

Is it safe?

Does the inverter stop?Yes
SeverityFault — needs a manual reset once the cause is fixed
Engineer needed?Yes

The inverter stops until the fault clears or is reset.

Resetting itself: no.

Manual reset: see notes.

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.
  • Restart via the mySigen app (owner account can issue standby/shutdown then startup).

What the engineer will check

  • Power-cycle including DC/AC switches.
  • Component replacement.
  • Sub-IDs: ID1 power module; ID2 control module; ID3 auxiliary power supply; ID4 built-in PID module; ID5 monitoring module; ID6 heating film; ID7 external fan; ID8 abnormal night-time PID; ID9 energy storage cluster fault.

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

A code explains what the controller detected, not a confirmed root cause.

Reviewed: 24 September 2026