Local Energy Management: Integrating PV Inverters and Battery Storage via Modbus TCP

Reviewed: 25 September 2026. A local connection to an inverter can support monitoring without a cloud request for every reading. It does not automatically guarantee sub-second measurements, maximum self-consumption or safe control. A working system needs three distinct pieces: a correctly interpreted measurement, a decision based on sufficiently recent data and a supported way to control the load.

Begin with the device, not a copied register number

Home Assistant’s generic Modbus integration requires an explicit register configuration. A device-specific integration may already handle those details. Connection type, address, data type, scaling and polling settings are separate choices. [1]

The installation record should identify the inverter, firmware, manufacturer register map, communication interface and intended measurement. PV production is not automatically grid export: household consumption and battery charging can change the available surplus. A controller using the wrong measurement can make a perfectly decoded number drive the wrong decision.

What SunSpec standardises

SunSpec publishes model definitions for supported data points. A device’s implemented model and point definitions determine interpretation; the name SunSpec alone does not establish a universal register address or support for every model. [2][4]

A verification sheet should contain the address convention, unit identifier, register type, signedness, word order where relevant, unit, scaling and invalid-value behaviour. A manual’s displayed register number and a client’s protocol address may use different numbering conventions. The correct conversion must come from the device and client documentation, not from a guess.

A numerical example without a hardware address

For a fictional integer point with raw value 1234 and scale factor −1, the scaled value is 1234 × 10⁻¹ = 123.4. The unit still comes from the point definition. A floating-point point or an unavailable-value marker must not be interpreted through that example by default.

The Modbus and SunSpec Register Decoder supports offline checking of raw values. It does not discover a device’s map or confirm that a register represents the intended measurement. The existing SunSpec reading tutorial covers model discovery in more detail.

Polling frequency is not measurement freshness

A request every second does not prove that the device refreshes its internal measurement every second. Network delay, device processing, timeouts and competing clients can further change the observed interval. The useful test records successful responses, failures and the age of values during ordinary operation and a deliberate communication interruption.

Home Assistant exposes timeout and polling controls, but their presence is not a timing guarantee. [1] The starting interval should follow the manufacturer’s supported behaviour. More frequent requests are only useful if they produce sufficiently fresh information without destabilising communication.

Surplus control needs a consistent definition

Consider a fictional system reporting positive power for export. If export is 2.4 kW and a 2 kW heater starts, unchanged generation and other consumption would leave about 0.4 kW export. A rule that immediately requires 2.4 kW to keep the heater running would undo its own action. This illustrates why the measured quantity, switch-on condition and switch-off condition must be designed together.

Different thresholds, minimum operating times and appropriate filtering can form part of that design. There is no universal threshold gap valid for every controller: it matters whether the signal already includes the controlled load. Device protection and manufacturer limits take precedence over a minimum-on timer.

A commissioning record should specify behaviour for unavailable, stale and implausible data. Keeping the last value forever can hide a disconnected meter. Monitoring and write access should be commissioned separately; an observed register does not establish permission to write adjacent registers.

Local transport and secure transport are different

Secure SunSpec Modbus specifies mutual TLS, certificates and role-based authorisation. That is a distinct supported capability, not a property automatically added to ordinary Modbus TCP on port 502. [3]

Support must be established at both endpoints. Where the equipment only supports ordinary local Modbus, network access should be limited to the required controller and equipment. A browser decoder supplies neither transport encryption nor access control. No device settings or live registers were changed for this article.

Acceptance criteria for the integration

• The chosen point is documented for the actual device and firmware.
• Decoded values agree with a suitable reference under several operating conditions.
• Sign conventions and units are recorded.
• Response timing and missing-data behaviour have been measured.
• The automation responds predictably when communication fails.
• Any control path is supported and respects equipment limits.

These observations establish what the installation actually does. A copied YAML example or the word “local” cannot replace them.