-
Notifications
You must be signed in to change notification settings - Fork 669
Replies: 1 comment · 2 replies
-
Please check if you can see something n the log. Enabling the DEBUG log might help.
I guess this is because the device restarted (eg. due to a crash). |
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm sorry, but there are only “RATE TOO HIGH” errors in the log. However, I can assure you that the espCAM did NOT crash when the error occurred at 06:36 pm. As you can see, the uptime timer continued to run until the manual reboot at 10:43 pm. I have just changed the log level from ERROR to DEBUG. However, it seems that both a reboot of the device and a restart of Home Assistant trigger this error. |
Beta Was this translation helpful? Give feedback.
All reactions
-
HA has just offered me a core update, which requires a restart. A good opportunity to take a closer look at the problem. HA was unavailable from about 00:30:15 to 00:31:00. I am attaching the corresponding snippet from the log: No incorrect values are sent or received. Rather, the “not available” status is corrupting the statistics. Unfortunately, I still have no explanation as to where the two seemingly arbitrary values before and after restarting HA come from.
|
Beta Was this translation helpful? Give feedback.
All reactions
This discussion was converted from issue #3247 on September 30, 2024 18:58.
-
The Problem
I use AI-on-the-edge with Home Assistant and Mosquitto MQTT. Occasionally (once or twice a week) the Home Assistant reports a sudden, large spike in value that skews my stats. This seems to be related to a loss of connection from the AI-on-the-edge device. While the water meter value corrects itself, the calculated costs in Home Assistant remain unrealistically high. I traced the problem back to a specific point in time and noticed that the diagnostic JSON was missing for that time period. The 'uptime' value fall to a very low value (from 180k to 1.5k sec) but NOT zero during the disconnect and then restored afterwards, suggesting that the device was never actually switched off but send corrupted data.
Is this a bug that I can fix from the "AI-on-the-edge" side, or do I need to do a workaround within the Home Assistant?
Version
Release: v15.7.0 (Commit: 0d0b018+)
Logfile
Expected Behavior
The device should not lose its connection. The transmission of values should be acknowledged as correct. If something is wrong, no incorrect values should be sent, but the device should be detected as unavailable so that the statistics are not falsified.
Screenshots
Additional Context
The connection should be very good (-66dBm) since I already specifically moved an access point for it.
Beta Was this translation helpful? Give feedback.
All reactions