MMM-Hoymiles-Wifi

schris88

@evroom Hi there, maybe you can confirm, if the inverter has multiple inputs there seems to be an array of pv_data objects in the json (as seen in the test.json you pushed)

so the meter should combine all pv data power to have the total, right.
But we dont need to do that by hand because the combined value should be in dtu_power already, you can get rid of all the try except.

I just didnt change it in the beginning because for inverters with only one input it makes no difference because its pv_data power and dtu_power is always the same value.

evroom

@schris88

First of all, those are details I need to have a look at now that the basis is there.
Perhaps there are other values and queries that make sense and that I can use. Like dtu_power and dtu_daily_energy.
Also saving some data to not have counters showing 0 when the invertor is inactive needs to be implemented.
During testing I found out that the pv_data for port 1 and 2 were different sometimes and that is why I needed to add those checks.
And they can never hurt. Better to be safe than sorry.
Furthermore, when you have only 1 panel connected, it is needed anyway.

evroom

@schris88

Just FYI, I declare(d) more parameters than really necessary and actually used, in order to allow for more counters to display.
For example a gauge for each panel; more details on the energy production of each panel; etc.
I will make a remark about this in the code.

schris88

@evroom That sounds good, but we should loop through the pv_data objects and display each as a graph. In the end, there could be a config setting like detailed: true to activate the display of all pv_data objects as individual graphs. If set to false, we could display a single graph with the total power.

There are Hoymiles inverters with 6 inputs, and adding 6 × 6 to 8 variables can quickly add up. This might not be an issue for us, but it’s worth considering if the module should be as generic as possible.

Sorry I´m a IT-Consultant who, sometimes it breaks through :D