It should be a kWh parameter, so it might need a calculation from current energy production in Watts somehow. But it’s all a bit hasty analysis, the addition in HA looks great.
That would be great! Remember to add the calVer correction to correct version display from HACS.
kinda lol… i did a template months back for daily solar energy to combine with P1 datas
utility_meter:
daily_solar_energy:
source: sensor.ecu_today_energy
cycle: daily
that one is available and to select in energy config and does a reset over day switch. So we can see if this is the right way to go tomorrow and see if that addition is good for the integration
1 Like
his ECU has other kind of firmware, atleast version greater then ours somehow
“Version”: “ECU_R_PRO_2.0.0”. With the disconnect port it started working
I tried to add the template but I must do something wrong. How do you implement this on HA? (and by the way does it work!). I’m curious to see it working!
yeah… template is the wrong word, sorry. Its the utility meter integration, where you can addthis as item. Just copy paste as main node in config yaml.
currently it looks like this, will do some value validations later as the power consumed from grid is netto instead of absolute
Nice! I managed to add the script now, let’s see how it works out in the next view hours. Thnx!
Kevin, how did you make the pop card with Voltage details per inverter? Can you share? Is done with card-mod?
Kevin, I found out that the ECU with 2.0 software doesnt work well with a open connection and multiple queries. When I closed them and reopen them for each query, it worked.
Other issue: my HA crashed because the ECU was also in a wrong state. After restart it worked again. Before restarting the ECU it reported after a query for hundreds like below (increment for each UID)
“UID17413”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
},
“UID17414”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
},
“UID17415”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
},
“UID17416”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
},
“UID17417”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
},
“UID17418”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
}
Can we make the integration more robust when ECU respons is not what HA integration suspect?
Even with two solarpanels things are starting to show now (after two hours), this is looking great. You can also add the Forecast.Solar integration. It will plot the forecast on the solar production graph.
What do you mean by this, can you be more specific?
that forecastes i activated too yesterday. Predicting 28Kwh for today, that wont happen 
. Will play with that setup too. I’m still not convinced the energy overview from HA is correct for my situation also.
lots of calculating to do
Did you not forget to specify the maximum output power of your solarpanel grid? But indeed it’s a prediction and I think they will improve things now that they’ve combined the graphs. Frenck has solarpanels 
(but uses SolarEdge though)
Might be the same issue I’m having? Refer to Integration broke Home Assistant 2021.8.0 · Issue #16 · ksheumaker/homeassistant-apsystems_ecur · GitHub
interesting that firmware on ecu can stop HA. Debug logs should show more at least
HAEdwin,
The ECU is not responding anymore with suspected into of ECU, query, inverter query and inverter signal query. So after HA crashed, I disabled apsystems_ecur temporary and restarted HA. After I focussed on the ECU. It responded with hunderds of UIDs (incremented each by one). After restart of the ECU, the response was correct again and stable and integrate HA again.
The ECU showed info as below. But the UID are complete unknown by me of walk over all possible UIDs. After restart only my 5 UIDs are correctly showed.
… buffer was to short to show all
“UID17416”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
},
“UID17417”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
},
“UID17418”: {
“UID”: “’”,
“Online”: false,
“Type”: “Unknown”
}
did your firmware get an update last night? APS is known for just pushing new fw around 3am
No, version is the same ECU_R_PRO_2.0.0
i’m flabbered. How about the script we used from tweakers, is that producing normal output when you run it?