pv2mqtt

Description

Publish data from SunSpec-compliant inverters to an MQTT broker, including Home Assistant MQTT discovery.

This service allows me to have all of the data of my PV inverters together in once place on a local machine, instead of using a different API (and possibly cloud service) for each one. It also allows multiple "readers" to use the data without conflict.

One pv2mqtt instance can poll multiple devices on multiple buses and the refresh interval is configurable per device.

Configuration

To configure pv2mqtt, make a copy of pv2mqtt.dist.yml and edit the copy to match your setup.

You need to define a "connection" for each physical connection (= modbus bus) your devices are connected to and a "device" for each device you want to read data from.

In addition, you may need to set up a user account on your MQTT broker.

Building/installing/running

The easiest way to run pv2pqtt is to use a container:

$ docker pull ghcr.io/martijnvds/pv2mqtt:latest
$ # (images are available for amd64, i386, arm64 and arm/v7)

$ # Or build it yourself:
$ docker build -t pv2mqtt .

This way, you will always have a supported Python version, and you won't clutter up the system with dependencies.

It's also possible to install the dependencies manually, outside of a container by using the included requirements.txt.

Once you've downloaded or built the container, you can run it:

$ docker run --rm \
    --volume $(pwd)/pv2mqtt.yml:/pv2mqtt.yml:ro \
    martijnvds/pv2mqtt:latest

This makes the configuration file available in the container as /pv2mqtt.yml. The container is built with to automatically start pv2mqtt using that configuration file. You can specify a different one on the command line:

$ docker run --rm \
    --volume $(pwd)/pv2mqtt.yml:/etc/pv2mqtt.yml:ro \
    martijnvds/pv2mqtt:latest \
    /etc/pv2mqtt.yml

If you use a serial (RS-485) connection, you also need to pass through the serial device to the container at startup. Make sure you use the same device name in your configuration file!

$ docker run --rm \
    --volume=$(pwd)/pv2mqtt.yml:/pv2mqtt.yml:ro \
    --device=/dev/ttyUSB0:/dev/ttyUSB0:rw \
    ghcr.io/martijnvds/pv2mqtt:latest

Limitations

Currently, only inverter data is read and published.

Tested devices

The program has been tested with the following devices:

Device	Type	Comment
AP Systems YC600	Micro inverter with external monitoring box	Works (via ECU-R-Pro); make sure Modbus is enabled; default TCP port is 502
SolarEdge SE3680H-RW000BNN4	"Regular" inverter	Works over wifi, should also work over wired ethernet and RTU; for wifi/ethernet usage, Modbus-TCP needs to be enabled; default TCP port is 1502

Links

• pysunspec2 - SunSpec library that does the heavy lifting.
• Home Assistant SunSpec integration - Alternative if all your inverters support Modbus-TCP and you only need your data in Home Assistant.