FAQ

FAQ

Short answers with a pointer to the long ones. The README's When something is wrong covers the error cases; this list is for everything else.

Does the integration write to my inverter? For the battery, yes, automatically, whenever the inverter reports one: block 124's charge and discharge rate entities need no flag. For the export limit, power factor and grid connection, not unless you tick Enable experimental export controls (BETA) in the options; without it there is no export entity and the set_export_limit action refuses to run.

My inverter has no sensors after setup, or only the MPPT ones. Your device is in float mode and publishes block 111, 112 or 113, which are not preselected. Open the options and tick them, or switch the inverter to int + SF. SunSpec models explained.

Where is the rated power, the vendor state, the battery reserve? Disabled by default. Open the entity and switch it on. Entity names and IDs.

Can I poll faster than 5 seconds? No. How polling works in depth says why. Every point of an entry shares one interval.

Can one point be polled faster than the others? No. For a control loop that needs a fast grid reading, a meter with its own connection is the better source.

Can I run this next to the Home Assistant Modbus integration, or next to openHAB, Solar-Log, evcc, on the same inverter? Only through a Modbus proxy. Most inverters accept exactly one connection. Sharing the inverter with other programs.

Two Home Assistant instances, one inverter? Same answer: a proxy.

Two inverters, or an inverter and its meter, on one IP? One config entry per unit ID. The integration takes turns on the connection by itself. Several inverters on one connection in the README, and the unit IDs in Vendor notes.

The export limit switches itself off after a minute. That is the inverter's revert timer, and it is a feature. The revert timer, and how not to get caught by it, and the keepalive automation in Zero export and export limiting.

Does an export limit of 0 % give me zero feed-in? It gives you zero production. The limit caps the inverter's output, not the flow at the grid connection. Zero feed-in with self-consumption needs a control loop against a grid meter. Zero export and export limiting.

I changed the export limit and the inverter ignores the new value. On a Fronius this is documented behaviour: a new value applies only once the enable flag goes from off to on again. Use the sunspec2.set_export_limit action, which does both in one write, or turn on the integration's Re-apply the export limit and power factor by switching them off and on when their value changes option and let it do the cycle. Vendor notes.

Why is lifetime energy a number in the millions? SunSpec reports watt-hours. The README's Energy dashboard section shows the kWh conversion.

Why does the export limit entity show a value the inverter is not using? Block 123 has one register for the limit, and it holds whatever was last written. There is no register that reports the limit in force. The exported watts are the only witness. Block 704 reports the remaining revert time, which is the closest thing to an answer.

Does it support Huawei, Growatt, Deye, SolaX, Victron? No. Those speak Modbus with their own register maps, not SunSpec. Vendor notes.

Can I add my own block definition for a vendor block? Not through the options. The definitions ship inside the integration and are refreshed from the SunSpec repository. A missing vendor block is read anyway; only its point labels are missing.

How do I get the config_entry_id for the service action? Build the action in the visual automation editor, pick the entry from the dropdown, then switch to Edit in YAML. The id is also the last part of the URL behind Download diagnostics.

Why is the version in the diagnostics different from the HACS one? It is not, once Home Assistant has been restarted after the update. HACS downloads the files; the running version changes on restart.