Find the next thing to check.

Check panel Wi-Fi, GX IP, local routing and Modbus/TCP service. Allow the scan to finish; the GX may still be starting. A saved setup retries temporary discovery failures.

Confirm the expected equipment appears on the GX and supports the required Modbus service. Check GX Unit IDs and the scan result. For HA discovery, repeat with all devices online and a complete MQTT publication.

Some GX Modbus values are zero when the underlying measurement is absent. Zero alone does not establish phase presence or meter connectivity.

Check source entities, energy units, Recorder/statistics and the panel’s configured snapshot entity. Newly created sources need records before history can appear; the panel cannot invent earlier intervals.

The panel displays HA records. HA downtime or unavailable sources can leave gaps, especially for estimated energy. Panel uptime cannot repair missing HA records.

Configure compatible forecast entities in HA and check that the integration makes them available. MQTT discovery does not supply a forecast.

Check the bridge and exactly one full-republish sender at roughly 30-second intervals. suppress-republish is incompatible with this setup. Do not add another sender without checking the existing one.

That is expected for site-qualified entities. The integration detects the sensor IDs automatically; check its discovered devices rather than assuming generic sensor names.

Use the matching complete release. The earlier port exhausted internal RAM with a 25% draw buffer; the working port uses a full-size PSRAM buffer and its matching cache/display settings. Do not copy 4-inch memory settings into it.

Download the firmware matching your exact board and connection mode from your account, then follow its flashing instructions.

Check signal at the installed position, antenna clearance, local access point and power supply. Compare operation outside the case before treating it as a protocol issue.