-
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
MQTT Uptime and rate odd for a moment after restart #1658
Comments
I tried to reproduce your issue, but I can't! On my side, all looks ok.
As you can see, my uptime starts at zero and the rate is also zero: Maybe you had some issues with NTP? If you can reproduce it, please provide a full DEBUG log! |
At the moment I am doing tests with changed system configuration. Therefore I have to restart the system more often. I have the negative values after the restart every time. Procedure:
See message log (debug mode). EXTRACT!
See attached full message log (2022-12-28) |
@TopGoalVl Can you give a feedback if #1840 solves your issue? You can get it from here: https://github.com/jomjol/AI-on-the-edge-device/actions/workflows/build.yaml?query=branch%3Atry-fixing-negative-uptime-after-restart |
Hallo zusammen,<br>
am 16.01.2023 gab es einen Neustart des Systems. Der Wert für "uptime" war wieder negativ (siehe Message log, debug level).
Die Rate Werte waren dieses mal nicht negativ. Allerdings wurde der gespeichert "prevalue.ini" Wert (416.0110 m³) aus dem config Ordner in das Datenfeld "ChangeAbsoluteRate" übernommen, was zu einem extrem hohen Wasserverbrauch, an diesem Tag, führt. Das kann nicht richtig und auch nicht so gewollt sein.
Den Sachverhalt habe ich bereits im Issue #1730 mitgeteilt.
Extrakt aus Message log:
------------------------
```
[0d00h05m32s] 2023-01-16T00:40:46 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/uptime, content: -3568 (msg_id=6)<br>
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/changeabsolut, content: 416.0110 (msg_id=24)
```
NTP Sync ok!
------------
```
[0d00h05m19s] 2023-01-16T00:45:24 <DBG> [TFLITE] Make Allocate
[0d00h05m20s] 2023-01-16T00:45:24 <DBG> [TFLITE] Make Allocate
[0d00h05m20s] 2023-01-16T01:45:24 <INF> [SNTP] Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
[0d00h05m20s] 2023-01-16T01:45:24 <INF> [SNTP] Set SNTP-Server to de.pool.ntp.org
[0d00h05m20s] 2023-01-16T01:45:24 <INF> [SNTP] Waiting until we get a time from the NTP server de.pool.ntp.org
[0d00h05m20s] 2023-01-16T01:45:24 <INF> [SNTP] Status: Reset
[0d00h05m22s] 2023-01-16T00:40:35 <INF> [SNTP] Status OK
```
Details Round #1:
-----------------
```
[0d00h05m22s] 2023-01-16T00:40:35 <DBG> [TFLITE SERVER] ----------------------------------------------------------------<br>
[0d00h05m22s] 2023-01-16T00:40:35 <INF> [TFLITE SERVER] Round #1 started<br>
[0d00h05m32s] 2023-01-16T00:40:45 <DBG> [MQTT SERVER] Publishing static MQTT topics...<br>
[0d00h05m32s] 2023-01-16T00:40:45 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/MAC, content: C8:F0:9E:A2:63:50 (msg_id=2)<br>
[0d00h05m32s] 2023-01-16T00:40:45 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/IP, content: 192.168.188.6 (msg_id=3)<br>
[0d00h05m32s] 2023-01-16T00:40:45 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/hostname, content: LeuVoShWz6 (msg_id=4)<br>
[0d00h05m32s] 2023-01-16T00:40:45 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/interval, content: 4.8 (msg_id=5)<br>
[0d00h05m32s] 2023-01-16T00:40:46 <DBG> [MQTT SERVER] Publishing system MQTT topics...<br>
[0d00h05m32s] 2023-01-16T00:40:46 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/uptime, content: -3568 (msg_id=6)<br>
|
|
|
[0d00h06m12s] 2023-01-16T00:41:26 <INF> [POSTPROC] main: Raw: 0416.0110, Value: 416.0110, Status: no error
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/status, content: Sending MQTT (msg_id=15)
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT SERVER] Publishing system MQTT topics...
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/uptime, content: -3528 (msg_id=16)
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/freeMem, content: 3024199 (msg_id=17)
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/wifiRSSI, content: -49 (msg_id=18)
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/CPUtemp, content: 76 (msg_id=19)
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT] Publishing MQTT topics...
[0d00h06m12s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/value, content: 416.0110 (msg_id=20)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/error, content: no error (msg_id=21)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/rate, content: 0.000015 (msg_id=22)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/rate_per_time_unit, content: 0.000015 (msg_id=23)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/changeabsolut, content: 416.0110 (msg_id=24)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/rate_per_digitalization_round, content: 416.0110 (msg_id=25)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/raw, content: 0416.0110 (msg_id=26)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/timestamp, content: 2023-01-16T00:40:49+0100 (msg_id=27)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/main/json, content: { "value": "416.0110", "raw": "0416.0110", "pre": "416.0110", .. (msg_id=28)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [MQTT IF] Published topic: LeupoldsPub/Wasserzähler/status, content: Flow finished (msg_id=29)
[0d00h06m13s] 2023-01-16T00:41:26 <DBG> [TFLITE SERVER] CPU Temperature: 76.7
[0d00h06m13s] 2023-01-16T00:41:26 <INF> [TFLITE SERVER] Round #1 completed
[0d00h08m49s] 2023-01-16T00:44:02 <DBG> [MAIN SERVER] info_get_handler
[0d00h08m49s] 2023-01-16T00:44:02 <DBG> [MAIN SERVER] info_get_handler
[0d00h10m13s] 2023-01-16T00:45:26 <DBG> [TFLITE SERVER] ----------------------------------------------------------------
```
|
so my modification did not help as I understand you. Then we will not add it to the next release. The other things also look odd but I do not really have the time to look into it as I can not reproduce it. Could you try to reproduce it using the https://jomjol.github.io/AI-on-the-edge-device-docs/Demo-Mode/ and document it so we can reproduce it as well? |
I wanted to check the fix for issue #1658, but I get the following error in PIO.
|
which branch are you using?
|
I now have version 14.0.0 installed. If the error occurs again, I'll create a new post. |
The Problem
I think that the reported bugs do not affect the essential functions of the system.
See log files (extract).
Version
Release: v13.0.8 (Commit: 04f2f23+), 2022-12-19 20:41
Logfile
Expected Behavior
No response
Screenshots
No response
Additional Context
Build Info:
The text was updated successfully, but these errors were encountered: