This project is not endorsed by, directly affiliated with, maintained, authorized, or sponsored by ABB or FIMER
HA Custom Component to integrate data from ABB/Power-One/FIMER PV mono-phase and three-phase inverters that support SunSpec Modbus Models M1/M103/M160, natively or through the VSN300/VSN700 wifi logger card. The VSN300/VSN700 cards provide a SunSpec to Aurora protocol adapter so that all modbus commands are translated to the proprietary Aurora protocol.
The component has been originally developed by @binsentsu for SolarEdge inverters, I adapted it, adding some features, rewriting all the registers' mapping, for my Power-One Aurora PVI-10.0-OUTD 3-phase inverter to which I added a VSN300 card. It has also been tested with an ABB TRIO-8.5-TL-OUTD-S through a VSN300 and REACT2-3.6-TL through a VSN700 datalogger.
Register address map has been implemented following the vendor's specification documentation, available in the doc folder.
- Installation/Configuration through Config Flow UI
- Separate sensor per register
- Configurable TCP modbus port, also at runtime (no restart needed)
- Configurable modbus slave address, also at runtime (no restart needed)
- Configurable register map base address, also at runtime (no restart needed)
- Configurable polling interval, also at runtime (no restart needed)
- Supports SunSpec models M1, M103, M160
This integration is available in HACS official repository. Click this button to open HA directly on the integration page so you can easily install it:
- Either click the button above, or navigate to HACS in Home Assistant and:
- 'Explore & Download Repositories'
- Search for 'ABB Power-One PVI SunSpec'
- Download
- Restart Home Assistant
- Go to Settings > Devices and Services > Add Integration
- Search for and select 'ABB Power-One PVI SunSpec' (if the integration is not found, do a hard-refresh (ctrl+F5) in the browser)
- Proceed with the configuration
Download the source code archive from the release page. Unpack the archive and copy the contents of custom_components folder to your home-assistant config/custom_components folder. Restart Home Assistant, and then the integration can be added and configured through the native integration setup UI. If you don't see it in the native integrations list, press ctrl-F5 to refresh the browser while you're on that page and retry.
Enable Modbus TCP client on the VSN300, take note of the Unit ID (aka Slave ID) of the inverter (depends on the model, default on some models is 2 on others is 247) and during the configuration of the component, use the appropriate Slave address. Another important parameter is the registers map base address, default is 40000 but it may vary. All these parameters can be reconfigured after installation, clicking CONFIGURE on the integration.
Configuration is done via config flow right after adding the integration. After the first configuration you can change parameters (except custom name and ip/hostname) at runtime through the integration page configuration, without the need to restart HA (this works since v2.5.0).
- custom name: custom name for the inverter, that will be used as prefix for sensors created by the component
- ip/hostname: IP/hostname of the inverter - this is used as unique_id, if you change it and reinstall you will lose historical data, that's why I advice to use hostname, so you can change IP without losing historical data
- tcp port: TCP port of the datalogger
- slave id: the unit id of the inverter in the chain: default is 254, if using VS300/VS700 it's usually 2
- register map base address: the base address from where the register map starts, usually it's 40000, but for ABB VSN300/VSN700 dataloggers it's 0
- polling period: frequency, in seconds, to read the registers and update the sensors
If you like this integration, I'll gladly accept some quality coffee, but please don't feel obliged. :)