H3-12.0-Smart + Fox ess EP12: compatible with conditions
The source supports this combination only under stated conditions.
Communication & inverter setup
Conditions attached to this Pair
EP series battery cable sizing is minimum 6 mm2 for 30 A charge/discharge.
AU configuration guide requires the listed battery quantity/configuration limits; installations outside guidelines may affect warranty.
Each EP12 is rated 11.52 kW charge/discharge; if battery power is insufficient, PV may supplement inverter capacity and the inverter can derate.
EP12 compatibility table specifies 1 to 4 EP12 units per battery stack; H3 Pro may use two stacks.
How to read this page
Confirmed by this dataset
- The verdict is derived from bound canonical entities, not fuzzy matching.
Not assumed
- Missing pinout, firmware, cable or DIP data does not mean none is required.
- A source-listed setup value is not automatically treated as a manufacturer-recommended method.
Source evidence
View raw source evidence
{"inverter":"H3-12.0-Smart","battery":"EP12","market_code":"AU","source_page":7,"source":"EP12 Inverter Compatibility List exact model table","series_scope":"H3 SMART"}Why H3-12.0-Smart + Fox ess EP12 is listed this way
Compatibility basis
This published page binds the exact inverter H3-12.0-Smart to the exact battery model Fox ess EP12. The current database resolution is CONDITIONAL under FOXESS_EP12_AU_EXACT_COMPAT_20260204. The verdict is produced from the stored manufacturer-source relationship for these canonical entities, not from fuzzy search similarity or a generic voltage-class assumption.
Communication setup recorded for this Pair
No communication setup is added to this page unless it exists in the stored source evidence.
Evidence coverage
The result is backed by 1 page-level evidence record on page 7 of EP12 Inverter Compatibility List (2026-02-04) (2026-02-04).
No extra wiring, DIP-switch, firmware, cable, charge-limit, or pinout claim is created from absence or analogy.
The source attaches 4 explicit conditions to this Pair; the condition text is shown separately and is not generalized to other models.
Search by the model names you actually have
The search layer can handle aliases and fuzzy input; compatibility is checked only after the exact database entities are confirmed.