Open Kornelius777 opened 10 months ago
I have the same problem after updating to Release 15.6.0. However, the raw value is only false (least significant digit of the digital section) when the analog recognition is used. My other devices (electricity meter, gas meter) show a correct raw value.
Please test and provide feedback for this updated development version, which uses post-processing logic from 15.4 again. Firmware for testing can be downloaded here: https://github.com/jomjol/AI-on-the-edge-device/actions/runs/7878286347
There are alignment problems with this version:
This is 15.6.0:
There was an issue in v15.5, maybe it is related to your issue, please update to rolling where we reverted this regression (https://github.com/jomjol/AI-on-the-edge-device/pull/2778). See https://github.com/jomjol/AI-on-the-edge-device/pull/2899
There are alignment problems with this version
This is most likely a different issue, please make sure the Reference marks are as far apart as possible and have good contrast.
There was an issue in v15.5, maybe it is related to your issue, please update to rolling where we reverted this regression (#2778). See #2899
There are alignment problems with this version
This is most likely a different issue, please make sure the Reference marks are as far apart as possible and have good contrast.
I downgraded to 15.3.0 - everything is running flawlessly now.
Hi guys, I do have those readings and I do not undestand them:
Every time that the fractions digit goes from 9 to 0, the readings are without the leading 0. Is this the correct behaviour? Could the missing 0 affect the values seen in Home Assistant like this? There is a helper that transforms cubic meters to liters and shows the values in HA but they are negative.
Also the main value should be 301 instead of 300. Maybe my meter is not so good and the digits are not changing full but the recognition should "see" 301 in this case.
Release: v15.7.0 (Commit: 0d0b018+)
Any help is much apprecitated, thank you in advance!
@gabimal Is there a reason why you don't let all digits evaluate as one complete number? So you probably won't get rid of your problem. Let all digits be processed as one number and simply use Decimal Shift to add the comma. https://jomjol.github.io/AI-on-the-edge-device-docs/Correction%20Algorithm/#decimalshift
@SybexX thank you for your quick answer! At one point I was thinking to use all digits as one number as you mentioned but I was unsure how it will behave. In this case the decimal shift will be -3?
LE: I have added another 3 digits and got 6 in total:
@gabimal yes, exactly -3 is correct. Since your counter apparently also counts down, you also have to activate "Allow Negative Rate". https://jomjol.github.io/AI-on-the-edge-device-docs/Correction%20Algorithm/#allownegativerates
@SybexX Thank you for confirming the decimal shift value! I'm not sure I understand what you are saying by meter counting down. It's a water meter that counts only up.
@gabimal Your counter once had 301,051 and in your last picture it has 299,667, from this I conclude that he also counts back
@SybexX Sorry about that. The first picture is the present meter reading and the second image (with all new 6 digits) is the reference image took a while ago. Thank you very much for your help and patience!
Hi! I'm also not sure how these raw values are calculated, as the recognition values look good to me. However, the raw value's decimals show something completely different than i expect, and I have no idea why. The "Decimal-Shift" was set to 0, and unchecking the box had no effect.
Could someone help, or is this the bug? Thanks!
Raw values: (the Pre Value in this log was manually set by me)
[POSTPROC] main: Raw: 059.0761, Value: , Status: Neg. Rate - Read: - Raw: 059.0761 - Pre: 59.1507
[POSTPROC] main: Raw: 059.0761, Value: , Status: Neg. Rate - Read: - Raw: 059.0761 - Pre: 59.1507
[POSTPROC] main: Raw: 059.0771, Value: , Status: Neg. Rate - Read: - Raw: 059.0771 - Pre: 59.1507
[POSTPROC] main: Raw: 059.0761, Value: , Status: Neg. Rate - Read: - Raw: 059.0761 - Pre: 59.1507
[POSTPROC] main: Raw: 059.0771, Value: , Status: Neg. Rate - Read: - Raw: 059.0771 - Pre: 59.1507
[POSTPROC] main: Raw: 059.0771, Value: , Status: Neg. Rate - Read: - Raw: 059.0771 - Pre: 59.1507
@SybexX Thanks for the quick response! I read the article before, and my Analog/Digital Transition Start is still set to 9.2 (default). However, I'm still unsure what kind of transitions this water meter makes since I've only monitored it for a few hours so far. I'll propably try a Transition setting between 6 and 8 in the morning. Based on the image, does it look like an early transition to you, or is that something we can even see on the watercount i have? I'm not really familiar with reading water meters, to be honest. I thought it was a normal transition, but there also hasn't been so much water flow since I set it up.
@Hausi91 Always reduce the value gradually, e.g. 9.2 > 9.0 > 8.8 > 8.6......... My water meter behaves similarly and a value of 9.0 works very well for me.
@SybexX Thanks! As soon as I reduced the "Analog/Digital Transition Start" to 9, I'm much closer to the values I expect. Thank you very much. You're the man!
The Problem
Raw Value is 1 m³ too small. Despite the Recognized Values are correct, the Raw Value is calculated "one less" (see attached picture)
Version
v15.5.0
Logfile
Expected Behavior
No response
Screenshots
Additional Context
No response