Skip to content
Seth edited this page Aug 15, 2024 · 15 revisions

SolarEdge Modbus Multi Integration

This integration provides Modbus/TCP local polling to one or more SolarEdge inverters for Home Assistant. Each inverter can support three meters and three batteries over Modbus/TCP. It works with single inverters, multiple inverters, meters, and batteries. It has significant improvements over similar integrations, and solaredge-modbus-multi is actively maintained.

Installation

Install with HACS: Search for "SolarEdge Modbus Multi" in the default repository,

Open your Home Assistant instance and open a repository inside the Home Assistant Community Store.

OR

Download the latest release and copy the solaredge_modbus_multi folder into to your Home Assistant config/custom_components folder.

After rebooting Home Assistant, this integration can be configured through the integration setup UI. It also supports options, repair issues, and reconfiguration through the user interface.

Major Features

  • Inverter support for 1 to 32 SolarEdge inverters.
  • Meter support for 1 to 3 meters per inverter.
  • Battery support for 1 to 3 batteries per inverter.
  • Automatically detects meters and batteries.
  • Supports site limit and storage controls.
  • Supports Three Phase Inverters with Synergy Technology.
  • Polling frequency configuration option (1 to 86400 seconds).
  • Configurable starting inverter device ID.
  • Connects locally using Modbus/TCP - no cloud dependencies.
  • Informational sensor for device and its attributes
  • Supports status and error reporting sensors.
  • User friendly: Config Flow, Options, Repair Issues, and Reconfiguration.

More Features

  • Complete device and entity category support in Home Assistant.
  • Supports the Energy Dashboard and Long Term Statistics.
  • Robust error handling and polling cycle handling.
  • Dynamic loading/reloading and configurable options through Home Assistant UI.
  • Opens a connection every poll cycle instead of holding it open (with option to hold open).
  • Meter events: shows one or more active meter events as an attribute, or an empty list if no events.
  • Sensors that are unsupported or invalid are treated as "unavailable".
  • Avoids stale sensor data by changing state to "unavailable" if an update fails.
  • Sensors with units VA, var, VAh, and varh are considered advanced types, disabled by default to avoid sensor clutter.
  • Validates sensors based on SunSpec model.
  • Uses a current version of pymodbus.