You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just before I loose the link again, noted it down for people using the APSystems EZ1 microinverters, there the possibility of collecting data from their WR via a python API library - locally.
Some insights from myself, the API basically just returns the current solar production and let control the inverter power.
In comparison to the DTU it provides the absolute powers and no efficiency. Locally I used the efficiency from the specs 97.5% to calculate the relative power which seem to be used here an there. Also there is no event based architecture like for the DTUs, which means a polling interval need to be used.
Sadly the code is hard to read and not documented. A suggestion from myself, clean this up a bit and add reasonable comments to functions and relevant code lines which gives the reason for things happening. This allows people to contribute :)
I'll try to further understand the code and contribute the adapter for EZ1 but not guarantee here.
PS: beside that, awesome project. Thanks for your work
Just before I loose the link again, noted it down for people using the APSystems EZ1 microinverters, there the possibility of collecting data from their WR via a python API library - locally.
https://github.com/SonnenladenGmbH/APsystems-EZ1-API
If the situation comes around could be a possible - additional - extension to the "support" WR list aside from DTU/MQTT for the Inverter
The text was updated successfully, but these errors were encountered: