rate and rate_per_time_unit value inf

[wokkeltje13]

The Problem

In MQTT I noticed the value "inf" for "rate" and "rate_per_time_unit"

Did I miss some release notes?
It stopped reporting the values on 13/12, so probably after the update to 13.0.7 (but I am not sure)

Thanks in advance

Version

13.0.7

Logfile

[       4] 2022-12-19T16:46:32 <INF> [MAIN] =================================================
[       4] 2022-12-19T16:46:32 <INF> [MAIN] ==================== Startup ====================
[       4] 2022-12-19T16:46:32 <INF> [MAIN] =================================================
[       4] 2022-12-19T16:46:32 <INF> [MAIN] Branch: 'HEAD', Revision: 304b9e0, Date/Time: 2022-12-11 22:36, Web UI: Release: v13.0.7 (Commit: 304b9e0)
[       4] 2022-12-19T16:46:32 <INF> [MAIN] Reset reason: Via esp_restart
[       8] 2022-12-19T16:46:36 <INF> [MAIN] =================================================
[       8] 2022-12-19T16:46:36 <INF> [MAIN] ================== Main Started =================
[       8] 2022-12-19T16:46:36 <INF> [MAIN] =================================================
[      10] 2022-12-19T16:46:38 <INF> [MAIN] Initialization completed successfully!

Expected Behavior

No response

Screenshots

No response

Additional Context

No response

[TopGoalVl]

Have a look at issue 1578. The bug is fixed in newest rolling.
#1578

[github-actions]

You can use the latest Automatic Build of the the rolling branch. It might already contain a fix for your issue.
Pick the most top passing entry (it has a green circle with a tick in it), then scoll down to the Artifacts and download the file named update_*.

[wokkeltje13]

I used the latest rolling build (I think)
"Merge for next Bugfix Release #953"
Development-Branch: HEAD (Commit: 1ee8f47+)

But after a couple of runs, the inf value remains

2022-12-19T19:18:24+0100,main,004565.0,4565.0,4565.0,inf,0.5,no error,0.0,0.0,4.0,5.0,6.0,5.0,0.2
2022-12-19T19:23:06+0100,main,004565.9,4565.9,4565.9,inf,0.9,no error,0.0,0.0,4.0,5.0,6.0,5.0,9.3
2022-12-19T19:27:56+0100,main,004565.9,4565.9,4565.9,nan,0.0,no error,0.0,0.0,4.0,5.0,6.0,5.3,9.3

Did I use the wrong build?

[TopGoalVl]

I have updated to:

Build Info:
Firmware Version: Development-Branch: rolling (Commit: 0d48c52+)
Firmware Build Time: 2022-12-18 10:20
Web Interface Version: Development-Branch: rolling (Commit: 0d48c52+)

and the bug was fixed.

[wokkeltje13]

With this exact version the bug is solved, but more recent builds still have the bug.

[caco3]

@JoMol, is this working for you in rolling?

[jomjol]

@caco3 : I can confirm. The problem is back!

Need to fix it, before I release.

[jomjol]

Again corrected in newest rolling