Daily yield shows very large number

[GFriedrich]

What happened?

In the morning hours, the values of the daily yield have been incorrectly read.
This happened at 08:27 CEST and the values I got are the following:

08:27:00 CEST

• for string 1: 11
• for string 2: 11

08:27:10 CEST

• for string 1: 65546
• for string 2: 58339

To Reproduce Bug

Just running OpenDTU and waiting for wrong values to show up.

Expected Behavior

If the inverter is still in a "ramp-up" situation in regards to power and the values might be wrong, I would expect that "very off numbers" to be filtered.

Install Method

Pre-Compiled binary from GitHub releases

What git-hash/version of OpenDTU?

v25.9.11 / f7e3693

What firmware variant (PIO Environment)?

generic_esp32

Relevant log/trace output

N/A

Anything else?

First of all: Thanks for this great piece of software. Really appreciate all your efforts here.
I'm using OpenDTU on a HM-600.
Additionally I've the "daily yield correction" enabled. Due to this the incorrectly received sample caused the daily value to be incorrect for the entire day (as the error was stored as an offset).

If you check the binary values from the first string, you will figure that very likely the two bytes of the daily yield contained a value of 0xFFFF (as summed with 11 from the read before you exactly get 65546). So this looks to me like some incorrect read of the daily yield for whatever reason. (Unfortunately it is not so easy to explain for the value of string 2.)

I'm basically wondering if one could simply ignore any values from a daily yield where the value jumps by insane numbers from one read to the other. (Could also be part of the daily yield correction feature.)

But even though I've tried to find any related open issues, maybe this is an already known issue?

Thanks for giving it a check anyways.

Please confirm the following

• I believe this issue is a bug that affects all users of OpenDTU, not something specific to my installation.
• I have already searched for relevant existing issues and discussions before opening this report.
• I have updated the title field above with a concise description.
• I have double checked that my inverter does not contain a W in the model name (like HMS-xxxW) as they are not supported.