Daily Energy zero

[schalkk]

Hi,

Has anybody tried to retrieve data from the QT2 (3 phase / 4 Channel Micro invertor) via the ECU-R? When I do this, the system only recognizes the first of the 6 active invertors.
In the invertor_qty it does show "6".

Any pointers would be appreciated.

[schalkk]

I now have all the inverters working after switching to HA via the HACS installation. Sees all 6 the inverters.

However, two issues remain:

1. Sees the inverters as YC1000 although it is a QT2 (all 6 starts with 901)
2. The daily energy and lifetime energy does not match with what I see in the APS mobile App or on the EMA website. HA is always lower.

[HAEdwin]

New model inverter that should be compatible with the QS1 but isn't yet identified as one. There are two steps in solving this.

1. Please enable debug logging: [Settings]>[Devices & Services]>choose the menu to
   
2. wait for the next interval to pass and stop the debug logging. A log file will be downloaded. Examine this log and look for the lines where the [custom_components.apsystems_ecur.APSystemsSocket] is outputting (less meaningfull) data. I need the second data string of the three available. Please post it here.
3. I will add the ID to the integration after verification.

[schalkk]

Hi,
here you go!
03 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur.APSystemsSocket] b'415053313130313931303030323030303100062023050813190090100000420801303201f4008b00cc019c00d2019f00d6019900cd90100000576401303201f4008b00d3019d00d6019c00e5019900db90100000698301303201f4008900cc019a00d6019e00d7019a000090100000623401303201f4008c0097019700d3019900e6019f00e490100000694601303201f4008d00cb019800d6019b00e0019c00df90100000735201303201f4008b00bf019800e6019500f1019700ec454e440a'

[schalkk]

I see in HA that the Timzone for the ECU is set to GMT-8 while in the EMA App, it is showing Europe/Amsterdam. What could be causing this?

I stil have the question as to why the Total Daily Energy and Lifetime Energy do not match between HA and ECU app or EMA Website. HA is always behind. Could the timezone be impacting this?

[HAEdwin]

Thank you

1. Sees the inverters as YC1000 although it is a QT2 (all 6 starts with 901)
2. The daily energy and lifetime energy does not match with what I see in the APS mobile App or on the EMA website. HA is always lower.

1. I will add the QT2 inverter for next release, the data structure is the same as the YC1000. Same goes for the YC600/DS3/DS3D-L type inverters they all have the same data structure.
2. The data passed to EMA is not in sync with the data passed to HA so there might indeed be a slight difference in values. To indicate this difference, I can show you the graph below. The purple line is the data sent to EMA, blue is HA data. Values might differ more on days with patches of cloud in opposite to a day with clear skies. This is due to the five minute interval.
   
   I noticed the timezone issue also, this is the data from the ECU and apparently can't be set correct using the ECU app so it's a bug on APsystems part.

[schalkk]

Hi,
Thanks for the quick update! Much appreciated,

For me the difference between the number is not small.

• Lifetime - HA 854 vs EMA 1160
• Daily - HA 13.74 vs EMA 19.88
  Is this data retrieved from the ECU or is it aggregated in HA?

[HAEdwin]

What interval is set for the integration? I would recommend setting it to 300. But I might have to dive deeper into this. Fact is that the daily values should not differ to much.

[schalkk]

It is set to 300.
BTW Firmware version on ECU-R-EU is 1.3.5B. Received it in Feb 2023.

[HAEdwin]

Lifetime energy shown in HA is data taken from the ECU. This same data is sent to EMA but is not being used so I assume that the EMA site uses different calculations.

[schalkk]

For interest sake, I just connected to the AP on the ECU with EMA MGR to check the values on the ECU-R.

It seems that HA and EMA MGR lines up but EMA App (and Website) is way above.

Lifetime Energy

• HA - 856.5
• EMA Mgr (AP) - 856.44
• EMA app (internet) - 1,160

Daily Energy

• HA - 15.72
• EMA MGR - 15
• EMA App - 21.4

Really Strange! Which numbers should we trust?

[schalkk]

I have asked APS support for clarification.

[HAEdwin]

@schalkk Did you happen to receive a reply from APsystems yet?

[schalkk]

@HAEdwin No reply yet. Sending them another e-mail. This time specifically to EMEA Support.

[schalkk]

@HAEdwin

Still no reply.

I have watched the ECU Current Power and Today Energy very closely. I compared the numbers in the EMA Web with the numbers in Home Assistant.

It seems that the problem is related to the "Today Energy" (same with Lifetime Energy) starting to increment, every day, hours after the Current Power. The Current Power starts incrementing shortly after sunrise, but the Today Energy number only start to show it's first non-zero number around 10:30 to 11:00 every mornning.

Here is today's example:

Once "Today Energy" starts to increment, it stays in step with the number shown in the EMA website.

Here is the pattern for the last 3 days:

Just an observation.

[HAEdwin]

Not sure why it is increasing late in your graphs, below are mine. Did you check the time zone and correct time on devices?

[schalkk]

@HAEdwin Really strange! I have check using the EMA Mgr app, it shows the correct time and timezone. If I check via the port 8899 I get GMT-8, which is not correct.

Is the one API call for GetRealTimeData (code 0002) collecting all the values or do you collect energy via the GetEnergyOfWeekMonthYear (code 0040)? Could they be using different timestamps (as seen by the EMA Mgr app & API)

[schalkk]

@HAEdwin This issue has now been sent to the APSystems programmers according to the Tech Support team.

[HAEdwin]

I suppose there was no answer from APsystems? Daily energy, timezone as well as a missing MAC address for the wireless interface are all ECU firmware bugs that have been around for a long time, no effort is being done to solve it.

For the daily energy; it is not being sent to EMA (I sniffed the data), it is calculated at EMA. I have to think of a way to calculate kWH within the integration. See also #207

YC1000 and QT2 share the same protocol. In the new release you'll also see the QT2 mentioned.

The difference between the lifetime energy in HA versus EMA is strange. Lifetime energy from the ECU is being sent to EMA but I guess they wanted to synchronize it with the actual data being sent to EMA and is therefor calculated at EMA. Thing is that there is a five minute interval which means that there is always a estimate... a cloud can shortly appear in front of the sun that is not picked up bij the ECU and vice versa. The push to EMA and the pull for HA are not synchronized so there always will be a difference.

[HAEdwin]

I am currently evaluating the values ​​when using the history data read by the ECU. The daily energy value is a better match than the previously read value, so I will implement it in a beta version.

[HAEdwin]

The pre-release v1.2.31b contains an extra ECU query that introduces (part of) the use of energy history data. This is a query I previously described but was never needed (we thought). To compensate load time for the integration, I shortened the sleep-time between opening and closing the port. I also introduced the keepalive, a careful introduction to removing this sleep-time and keeping the port open. Success will depend greatly on compatibility with different ECU models and firmware. If you own an older model starting with 2160xxxxxxx ECU-R, you can even leave out the open/close functions, but does this work for other ECU models? I could make it optional in the UI settings. Anyway it should solve this issue. Please let me know if it does so that I can close the issue.

[schalkk]

Hi,
I installed the new beta, restarted HA.
The results look much the same to me:
From: HA

From APSystemsema.com

On HA the daily energy is still 0 @11:51am and the Lifetime Energy is way lower than EMA (6.28MWh vs. 4,357.9kWh)

Thanks for the effort!

[HAEdwin]

Thanks for the feedback!

I noticed that EMA itself does the calculation for Today's Energy and Life Time Energy. You are on firmware version 1.3.6C with the ECU 2160xxxxx (that's the older model ECU-R without SunSpec logo on the back right?) - I'm still on firmware 1.2.25b with the same type of ECU so there's a difference also.

If you enable debug logging for the integration, what does the log show? I am especially interested in the four lines of the log after "Querying ECU...".

I have forgotten to specify END in the suffix.
Line 38 of APSsystemsSocket.py should then be changed from self.ecu_energy_history_suffix = "END00\n" to self.ecu_energy_history_suffix = "END00END\n". Then restart HA and see if that made a change to Today's Energy.

[schalkk]

Hi,
Yes, the ECU does not have the SunSpec Logo. I received it in March this year.
Daily energy is now starting to report numbers after the code change.

Debug info:
2023-11-20 15:23:22.422 DEBUG (SyncWorker_5) [custom_components.apsystems_ecur] Querying ECU...
2023-11-20 15:23:25.429 DEBUG (SyncWorker_5) [custom_components.apsystems_ecur.APSystemsSocket] b'4150533131303039343030303132313630303031323038333030310000aa3d0000028e00000011d0d0d0d0d0d0d00006000631303031324543555f525f312e332e36433030394574632f474d542d3880971b05ce12000000000000454e440a'
2023-11-20 15:23:34.451 DEBUG (SyncWorker_5) [custom_components.apsystems_ecur.APSystemsSocket] b'415053313130313931303030323030303100062023112015193490100000735201303201f3007b001a0186001a0187001b017f001990100000694601303201f30078001a0182001b0186001d0185001d90100000623401303201f30079001c0180001d0185001e0187001e90100000698301303201f3007900180186001d0183001c0189001c90100000576401303201f30076001b0187001a0182001e0183001d90100000420801303201f30077001a0188001a018600160182001b454e440a'
2023-11-20 15:23:34.451 DEBUG (SyncWorker_5) [custom_components.apsystems_ecur.APSystemsSocket] b'415053313130303630303033303030901000007352ab901000006946ab901000006234ab901000006983ab901000005764ab901000004208ab454e440a'
2023-11-20 15:23:34.451 DEBUG (SyncWorker_5) [custom_components.apsystems_ecur.APSystemsSocket] b'41505331323030373630303034303030302023111400000000202311150000000020231116000000032023111700000005202311180000000020231119000000002023112000000011454e440a'
2023-11-20 15:23:34.451 DEBUG (SyncWorker_5) [custom_components.apsystems_ecur] Got data from ECU
2023-11-20 15:23:34.452 DEBUG (SyncWorker_5) [custom_components.apsystems_ecur] Returning {'timestamp': '2023-11-20 15:19:34', 'inverters': {'901000007352': {'uid': '901000007352', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 23, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [26, 26, 27, 25], 'voltage': [390, 391, 383]}, '901000006946': {'uid': '901000006946', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 20, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [26, 27, 29, 29], 'voltage': [386, 390, 389]}, '901000006234': {'uid': '901000006234', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 21, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [28, 29, 30, 30], 'voltage': [384, 389, 391]}, '901000006983': {'uid': '901000006983', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 21, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [24, 29, 28, 28], 'voltage': [390, 387, 393]}, '901000005764': {'uid': '901000005764', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 18, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [27, 26, 30, 29], 'voltage': [391, 386, 387]}, '901000004208': {'uid': '901000004208', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 19, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [26, 26, 22, 27], 'voltage': [392, 390, 386]}}, 'today_energy': 0.17, 'ecu_id': '216000120830', 'lifetime_energy': 4358.1, 'current_power': 654, 'qty_of_inverters': 6, 'qty_of_online_inverters': 6, 'data_from_cache': False, 'querying': True, 'restart_ecu': False}
2023-11-20 15:23:34.453 DEBUG (MainThread) [custom_components.apsystems_ecur] Finished fetching apsystems_ecur data in 12.032 seconds (success: True)

[HAEdwin]

Thanks for testing, this looks much better now. Don't forget to disable debug logging again ;)

[HAEdwin]

I'm pretty sure Today Energy's issue has been resolved for the ECU-R, ECU-B and ECU-C. I'm closing this issue, if anything pops up, feel free to create a new issue. Notice that there might still be a small difference between the ECU en EMA values. EMA does it's own calculation but is sometimes adjusted by the maintenance interaction with the ECU in the evening. That's also the reason that the Lifetime Energy is different between both the ECU and EMU. I'm not sure what the valid/true value would be. Need a arithmetician for that to give us some advise.

[HAEdwin]

@schalkk Strange, I don't think this is due to the integration right now. All the values in the debug log are set to zero so that's what is being read and displayed. The Life Time value of zero means that the ECU must have reset somehow or might have a defect. EMA calculates the Today Energy and Life Time Energy seperate from the ECU so these numbers don't always match up with HA. There are 18 people that have updated to the latest release until now. Have you powercycled the ECU allready?

[HAEdwin]

On the 21th of november your ECU status was:

ECU ID: 216000xxxxxx
ECU model:1
Lifetime Energy: 4358,5 kWh
Current Power: 63 Watt
Today Energy: 0 kWh
Last EMA connect:D0D0D0D0D0D0D0
Inverters: 1 of 6 online
Signal Channel:10
Firmware Version:ECU_R_1.3.6C

At 10:03 in the morning, but still only one inverter online.

----------------  Inverter data  ----------------
Date/time:20231121100354
ECU model:01
----------------
Inverter ID:901000007352
Inverter online:0
Inverter mode:YC1000
No Data / Offline
----------------
Inverter ID:901000006946
Inverter online:1
Inverter mode:YC1000
Inverter Frequency:49,9 Hz
Inverter Temperature:16 Degrees
Inverter Power Ch1:15 W
Inverter Voltage Ch1:392 Volts
Inverter Power Ch2:16 W
Inverter Voltage Ch2:395 Volts
Inverter Power Ch3:16 W
Inverter Voltage Ch3:389 Volts
Inverter Power Ch4:16 W
----------------
Inverter ID:901000006234
Inverter online:0
Inverter mode:YC1000
No Data / Offline
----------------
Inverter ID:901000006983
Inverter online:0
Inverter mode:YC1000
No Data / Offline
----------------
Inverter ID:901000005764
Inverter online:0
Inverter mode:YC1000
No Data / Offline
----------------
Inverter ID:901000004208
Inverter online:0
Inverter mode:YC1000
No Data / Offline

How are the panels positioned?

[schalkk]

Hi,

Here are the latest debug after a restart of the ECU-R.

2023-11-22 13:34:11.193 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur] Querying ECU...
2023-11-22 13:34:14.204 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur.APSystemsSocket] b'4150533131303039343030303132313630303031323038333030310000aa41000006db00000000d0d0d0d0d0d0d00006000631303031324543555f525f312e332e36433030394574632f474d542d3880971b05ce12000000000000454e440a'
2023-11-22 13:34:23.225 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur.APSystemsSocket] b'415053313130313931303030323030303100062023112213331590100000735201303201f30075004301920044018d00450192004490100000694601303201f40074003e01900047018f004d0191004d90100000623401303201f40075004301930045018b00470191004790100000698301303201f400740057018f00480193004e0190004b90100000576401303201f40072004b0191004d0193004f018d004b90100000420801303201f30073004f01960047018f005001900046454e440a'
2023-11-22 13:34:23.225 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur.APSystemsSocket] b'415053313130303630303033303030901000007352ad901000006946ad901000006234ad901000006983ad901000005764ad901000004208ad454e440a'
2023-11-22 13:34:23.225 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur.APSystemsSocket] b'41505331323030373630303034303030302023111600000003202311170000000520231118000000002023111900000000202311200000003420231121000000002023112200000000454e440a'
2023-11-22 13:34:23.225 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur] Got data from ECU
2023-11-22 13:34:23.226 DEBUG (SyncWorker_6) [custom_components.apsystems_ecur] Returning {'timestamp': '2023-11-22 13:33:15', 'inverters': {'901000007352': {'uid': '901000007352', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 17, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [67, 68, 69, 68], 'voltage': [402, 397, 402]}, '901000006946': {'uid': '901000006946', 'online': True, 'signal': 67, 'frequency': 50.0, 'temperature': 16, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [62, 71, 77, 77], 'voltage': [400, 399, 401]}, '901000006234': {'uid': '901000006234', 'online': True, 'signal': 67, 'frequency': 50.0, 'temperature': 17, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [67, 69, 71, 71], 'voltage': [403, 395, 401]}, '901000006983': {'uid': '901000006983', 'online': True, 'signal': 67, 'frequency': 50.0, 'temperature': 16, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [87, 72, 78, 75], 'voltage': [399, 403, 400]}, '901000005764': {'uid': '901000005764', 'online': True, 'signal': 67, 'frequency': 50.0, 'temperature': 14, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [75, 77, 79, 75], 'voltage': [401, 403, 397]}, '901000004208': {'uid': '901000004208', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 15, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [79, 71, 80, 70], 'voltage': [406, 399, 400]}}, 'today_energy': 0.0, 'ecu_id': '216000120830', 'lifetime_energy': 4358.5, 'current_power': 1755, 'qty_of_inverters': 6, 'qty_of_online_inverters': 6, 'data_from_cache': False, 'querying': True, 'restart_ecu': False}

[HAEdwin]

Value for Today Energy reads zero still

History data for yesterday and today also shows zero for Today Energy. The 20th all was well. Did you allready update the integration to the official release v1.2.31?

[HAEdwin]

Got some zero values today also for Today Energy, weird...

[schalkk]

Upgraded to 1.2.31 and restarted HA. No change.

2023-11-22 14:42:08.424 DEBUG (SyncWorker_3) [custom_components.apsystems_ecur] Querying ECU...
2023-11-22 14:42:11.432 DEBUG (SyncWorker_3) [custom_components.apsystems_ecur.APSystemsSocket] b'4150533131303039343030303132313630303031323038333030310000aa410000013300000000d0d0d0d0d0d0d00006000631303031324543555f525f312e332e36433030394574632f474d542d3880971b05ce12000000000000454e440a'
2023-11-22 14:42:20.452 DEBUG (SyncWorker_3) [custom_components.apsystems_ecur.APSystemsSocket] b'415053313130313931303030323030303100062023112214381590100000735201303201f30077000d0183000e018a000d0183000d90100000694601303201f30075000d0184000d0186000e0187000f90100000623401303201f40077000d0187000d0184000e0189000e90100000698301303201f30076000a0182000d0187000d0189000d90100000576401303201f40071000c0183000c0189000e0183000d90100000420801303201f30073000b0185000b018c000b0183000c454e440a'
2023-11-22 14:42:20.453 DEBUG (SyncWorker_3) [custom_components.apsystems_ecur.APSystemsSocket] b'415053313130303630303033303030901000007352ad901000006946ad901000006234ad901000006983ad901000005764ad901000004208ae454e440a'
2023-11-22 14:42:20.453 DEBUG (SyncWorker_3) [custom_components.apsystems_ecur.APSystemsSocket] b'41505331323030373630303034303030302023111600000003202311170000000520231118000000002023111900000000202311200000003420231121000000002023112200000000454e440a'
2023-11-22 14:42:20.453 DEBUG (SyncWorker_3) [custom_components.apsystems_ecur] Got data from ECU
2023-11-22 14:42:20.453 DEBUG (SyncWorker_3) [custom_components.apsystems_ecur] Returning {'timestamp': '2023-11-22 14:38:15', 'inverters': {'901000007352': {'uid': '901000007352', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 19, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [13, 14, 13, 13], 'voltage': [387, 394, 387]}, '901000006946': {'uid': '901000006946', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 17, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [13, 13, 14, 15], 'voltage': [388, 390, 391]}, '901000006234': {'uid': '901000006234', 'online': True, 'signal': 67, 'frequency': 50.0, 'temperature': 19, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [13, 13, 14, 14], 'voltage': [391, 388, 393]}, '901000006983': {'uid': '901000006983', 'online': True, 'signal': 67, 'frequency': 49.9, 'temperature': 18, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [10, 13, 13, 13], 'voltage': [386, 391, 393]}, '901000005764': {'uid': '901000005764', 'online': True, 'signal': 67, 'frequency': 50.0, 'temperature': 13, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [12, 12, 14, 13], 'voltage': [387, 393, 387]}, '901000004208': {'uid': '901000004208', 'online': True, 'signal': 68, 'frequency': 49.9, 'temperature': 15, 'model': 'YC1000/QT2', 'channel_qty': 4, 'power': [11, 11, 11, 12], 'voltage': [389, 396, 387]}}, 'today_energy': 0.0, 'ecu_id': '216000120830', 'lifetime_energy': 4358.5, 'current_power': 307, 'qty_of_inverters': 6, 'qty_of_online_inverters': 6, 'data_from_cache': False, 'querying': True, 'restart_ecu': False}

[HAEdwin]

What if you install the previous version? v1.2.30.

I think Firmware Version (ECU_R_1.3.6C) killed the Today Energy and History data function for the ECU-R with sunspec logo on the back. Version (ECU_R_1.3.5B and ECU_R_1.3.6A) worked well
For me owning an older model ECU-R (ECU_R_1.2.25B) things do work. don't know for how long

Because the values ​​did not match and EMA calculates the values ​​themselves based on incoming data, I think they have now removed this from the ECU. If anyone can help with how these two values ​​are calculated please let us know.

[schalkk]

Same problem with the previous version:

Result:

[schalkk]

On the 22nd of August I had a different firmware version: Aug 1.3.6A Nov 1.3.6C

Does anybody know when 1.3.6C was released?

[HAEdwin]

@schalkk I think the best option will be to calculate Today Energy and LifeTime Energy within the integration. The only disadvantage is that people will initially have to equate their Lifetime Energy to the EMA site.

Yesterday I got a zero Energy Today using the history query method anyway which was corrected later but I can't find the reason for that to happen. There must be something going wrong in the firmware.

[HAEdwin]

@schalkk Currently I've added three extra sensors on DEV where I calculate the LifeTime Energy, Daily Energy and (new sensor) Hourly Energy myself to compare them to the internal values from the ECU. This will also resolve the occasional zero values.

I've allready seen measurement deviations that have to do with rounding. I can imagine that this will paint a more positive picture on the EMA site over a longer period of time. I will continue the measurements. In the mean time firmware versions on the ECU have been updated so I keep that in mind.

[HAEdwin]

@schalkk There have been several firmware updates in the mean time.
Is Today Energy Still Behind Current Power?
I have used my own calculations to see what it yielded, but in the end it remains an approximation and yields little. I notice a few things;

1. There is rounding, both from the ECU (first rounding) and within the EMA (second rounding).
2. The query interval is not synchronized with the ECU updates. Together with the sometimes failing queries, this can lead to a deviation in the measurement results.

A solution could be to run the first ECU query more often and look at the timestamp of the last ECU update. If it differs from the previous one, run a full query. This also argues for removing the optional interval setting and implementing a fixed interval of, for example, 200 seconds. But even then there is a chance that a query beat is skipped, so there will always be differences in measurement results.

[arnovannijnatten]

For me it is still about 5-7 kWh off on a daily basis. Anything generated under 5kWh does not even get registered and reports as 0 for Today energy.
This is also the case for using the EMA Manager app and getting the Today energy data from there. It is very much less than what the consumer EMA app reports. The EMA consumer app is actually much closer to what my electricity net meter registers.
So having a (self) calculated energy today would make sense for my situation.
I am on firmware ECU_R_1.3.9 now.

[HAEdwin]

@arnovannijnatten I think there is something wrong with your ECU, try to replace it under warranty if possible.