Methodology

How InverterCompat builds compatibility records

InverterCompat is a structured compatibility database. Search may be fuzzy, but compatibility facts are not. Every published Pair page is tied to canonical entities and stored source evidence.

Manufacturer sources first

Primary compatibility claims come from manufacturer compatibility lists, manuals, integration guides, technical bulletins, or equivalent official documents.

Canonical entities

Aliases and imperfect typing are handled in search. The fact layer binds an exact inverter and an exact battery entity before a Pair verdict is returned.

Evidence stays attached

Compatibility, communication method, setup value, technical limitation, document version, date, page, and raw source row remain traceable in the database.

Current Deye LV baseline

DY-LV48-0127

Issued: 2026-08-03
Source role: Current manufacturer compatibility baseline
Historical versions: Retained, not overwritten

Not Listed ≠ Incompatible. A missing current listing is not converted into an incompatibility claim unless a source explicitly says the combination is incompatible.

Scope rules

Series scope is not silently promoted to exact-model fact

Inverter scope: Exact models inherit only from source expressions that explicitly contain them.
Battery scope: Series/family assertions remain series/family assertions unless model membership is independently represented.
Name similarity: Never used to create a compatibility fact.

Commissioning is source-supported, not guessed

CAN, RS485 and setup codes are displayed only when stored against the relevant assertion. A value supported for one battery model is not inherited by another model merely because the brand is the same.

Conflicts remain conflicts

If an official source contains conflicting setup values, both values are preserved and no preferred setup is inferred.

Missing technical data stays unknown

No firmware, pinout, DIP, cable, region, or known-issue statement is invented. Missing data means only that no verified fact is currently stored.

Version history

New sources supersede current status, not history

Current listing: Determined from the latest reviewed source.
Previously listed: Preserved as historical evidence when a later list no longer contains the relationship.
Explicit incompatibility: Used only when an authoritative source states incompatibility.

Publication is a separate quality gate. The Fact DB may contain many queryable relationships. A Pair becomes indexable only after exact identity, current status, evidence, and SEO quality checks pass and an explicit publication record is created.

Automation disclosure

Automation assists extraction; it does not invent facts

Automated work: Structured extraction, normalization, consistency checks, duplicate detection, and regression tests.
Protected boundary: Ambiguous entity expansion, source conflicts, and unsupported technical details are isolated rather than guessed.
Published output: Generated from stored facts and evidence, not filler copy.

Installation safety Compatibility records do not replace current manufacturer manuals, firmware requirements, wiring checks, voltage-class checks, commissioning procedures, or qualified installer review.