-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MaxRateValue from config not considered #382
Comments
Hi, |
Hello,
Thank you for your help! |
Switch on Logging in the config.ini |
Hi, actually I have the same problem since update to v10.0.2. Before it was running stable. I have switched on the logging now and will come back later with the logs. What I have realized already is: since the update I have a lot of suddenly reboots. Before it was running over weeks without any reboot. |
I also have this issue with version 10.0.2. As I remember version 9.1.1 was fine. See attached debug logfile (issue occurs in Round #14 12:55:33): Part of my config:
|
There seems to be a misreading of the neural network file, which was not detected as faulty, because it was below the MaxRate of 0.2. |
Hello,
First of all, thank you very much for your work.
I have the problem that on some days I have a counter change from over 1500 Liter (1.5m3)from my watermeter. That change based on a read out failure. To avoid these errors I have set the MaxRateValue to 0.2. But this is not considered. I have noticed that all numbers in your program are separated with a decimal point but in the config it is written with a comma. When I write it with a point it is changed after saving to a comma. Is this correct or the reason for the not considered max change of the reading.
thank you for your help!
The text was updated successfully, but these errors were encountered: