RAW value is not updated, but Recognition value is right

[sbeuchat]

The Problem

Hello

I've checked into the existing issue, but I didn't find any similar issue / bug correction.

The recognition value is right (7472.759)

But the RAW value isn't updated

I have played with CheckDigitalIncreaseConsistency, but it doens't help.

Did I missed something?

Thanks in advance for your support

Version

11.3.0

Expected Behavior

No response

Screenshots

No response

Additional Context

No response

[jomjol]

Can you update to the newest version? 11.3.0 might have some bugs there.

[Hoovercraft]

I have the same problem. It first appeared when my counter went from 576 to 577. The RAW Value remains static although the actual value is recognized.
My version is 12.0.1

[haverland]

@Hoovercraft: I'm not sure, what kind of correct value it should be.
dig3 = 6.8 and ana1=8.6 is on the most meters the digit = 6, because the digit is at ana3=0 on 7.0.
So the 576 should be correct.
But it could be the meter digit switches very late (analog >9.x)

[haverland]

The Problem

Hello

I've checked into the existing issue, but I didn't find any similar issue / bug correction.

The recognition value is right (7472.759)
@sbeuchat: you problem should be fixed in 12.0.1. But I've tested on rolling.

[jest01]

Hello,

i have the same problem, the raw value dosn't updated

the ESP32 could not be reached and could only be reactivated by power on/off.
I am currently using version 12.0.1

[haverland]

Hello,

i have the same problem, the raw value dosn't updated

Thanks. Any example is welcome. I've added it as test case.
We working on it and currently all posted examples are test cases for the next change.

[Hoovercraft]

another day, another wonder ... no idea what happened, didnt change anything, but its working again

[jest01]

Hello,

after a second ESP32 didn't work either, I looked in the serial log and found that the brownout detection had responded...for whatever reason
I bet on the internal voltage regulator in the ESP and have solved the voltage supply with a 5V power supply and a LD33V3 with 3.3V. Since then everything has been going well again.
Could that possibly be a cause?

Best regards

[Hoovercraft]

New day, new miracle. The problem is there again. Maybe a solution: if you go via the settings/set previous value menu, the value from the previous value is displayed for current value. Looks like a wrong mapping. Workaround: switch off the previous value in the config.

[haverland]

I think it's a bug in post-process on calculation of the last digit. It's fixed in the next release.

[caco3]

Please re-open if issue still happens again