MarcusWichelmann/EnergyExporter

Add support for multiple Modbus TCP connections

jeff47 opened this issue ยท 7 comments

I have two inverters for my house, both have Modbus TCP enabled. Do I need to collect from both -- and run two instances of SolarEdgeExporter, one for each?

Hi,

yes, it looks like that, that each inverter only exports its own local metrics, they are not aggregated. Even in a master-slave setup.

But you're lucky, because I have the same issue right now and plan to implement support for multiple inverters in the very near future. So you won't have to run multiple instances of the exporter then.

So please be patient, I'm working on it. ๐Ÿ‘๐Ÿผ

Awesome!

Nearly finished. Currently working on also adding InfluxDB support, then I'll release it as a new major version (because of breaking config changes).

Nearly finished. Currently working on also adding InfluxDB support, then I'll release it as a new major version (because of breaking config changes).

Any docs and tips you have on getting influxdb up and running would be great -- I've not used it yet, and finding it a little confusing!

I'm just using their docker image: https://hub.docker.com/_/influxdb
And here is a described, how you can generate the token that you can then give to the SolarEdgeExporter: https://www.influxdata.com/blog/getting-started-with-c-and-influxdb/

The reason I'm considering InfluxDB is, that my prometheus instance currently explodes because of years of high-resolution data. InfluxDB has the nice feature of being able to downsample the data over time.

But InfluxDB is still completely optional, you can continue using whatever you're using right now to retrieve the collected data (Prometheus, JSON, ...)

It's released: https://github.com/MarcusWichelmann/SolarEdgeExporter/releases/tag/v2.0.0
You'll have to update your appsettings.json because of some breaking changes. Please check the README for details.

Have fun and please let me know if everything works. ;)