Closed SebSkarp closed 1 year ago
The same for me, but with version 15.2.1 only.
So some updates from my end. I downgraded back to latest 14.x.x version and then it got up and running again. I then tried upgrading to 15.1.1 and fingers crossed but it seems to be working for me again. For the time being I will not go to to the latest version, since it seems to be working again.
I have the same problem. First I did the OTA update to version v15.2.1. Then I completely erased the ESP32, formatted the SD card and re-flashed and set everything up again. When that didn't work either, I took a completely new ESP32 and set it up again. In the beginning it runs reasonably well, but already after 15 minutes I get into an error loop and the ESP32 restarts every minute with the error "Reset reason: Exception/panic". In the Overview screen, only "Initializing (delayed)" is continuously displayed.
Same here with 14.X version. Could OTA update to 15.2.1 but still the same. Changed to new SD-Card to test if it was broken, but still the same. What I noticed from was the "LED Light" on the ESC32-Cam newer comes on at startup like before.
same here (with 15.2.1). I've toggled logs to DEBUG then reboot. so toggled to ERROR again. It works now... Strange
An other ESP32-Cam did not solve it and not the same config on an other SD-Card. Now I am back on the same ESP32-Cam board with new fresh files and new alignment etc. seems to work. Some kind of corruption of files on the SD
I've been looking for the problem again and found something.
I fetch the following data every 3 minutes via API with Node Red. http://192.168.xx.xx/json http://192.168.xx.xx/sysinfo http://192.168.xx.xx/rssi http://192.168.xx.xx/statusflow It has always worked great in the past.
Since my new ESP is up and running this afternoon, it restarts automatically every 3 minutes (at the same interval as my API query) with the error "Reset reason: Exception/panic". That struck me as suspicious :). In my experiments, I found out that this always happens when I retrieve "sysinfo" via the API. Even if I open "http://192.168.xx.xx/sysinfo" in the browser, the ESP crashes immediately. The other three (json, rssi and statusflow) are still working fine.
For an hour now I've disabled polling of "sysinfo" in Node Red and everything works fine. However, I always have to restart the ESP manually after it crashes. The automatic restart after the crash does not directly lead to it running again.
An other ESP32-Cam did not solve it and not the same config on an other SD-Card. Now I am back on the same ESP32-Cam board with new fresh files and new alignment etc. seems to work. Some kind of corruption of files on the SD
That didn't help me either. I took a new ESP and a new SD card, re-downloaded the files from GitHub and didn't restore any backups either. I completely reinstalled and set up everything. With the same result that it crashed again and again.
Mine has actually been working great since I first downgraded then upgraded again. Still kind of waiting for it to crash but for now that seems to have done the trick for me 🤞🏻
An other ESP32-Cam did not solve it and not the same config on an other SD-Card. Now I am back on the same ESP32-Cam board with new fresh files and new alignment etc. seems to work. Some kind of corruption of files on the SD
That didn't help me either. I took a new ESP and a new SD card, re-downloaded the files from GitHub and didn't restore any backups either. I completely reinstalled and set up everything. With the same result that it crashed again and again.
Mine up for 45 minutes now, lets see.
Can someone try whether calling "sysinfo" via the API still works for you? I assume that as soon as you call up "http://192.168.xx.xx/sysinfo" in the browser, you will have the same error again in the log.
Going to the IP and using menus to get to see System/Info work fine
Going to the IP and using menus to get to see System/Info work fine
What kind of answer is that? Of course you can use the website, but that doesn't change the fact that "sysinfo" no longer works via the API. I only use the web interface for setup and get all the data via the API into the home automation for visualization.
Sorry, dumb reply then!
Hi,
this is also one of the problems I have. I also can´t take a new reference image etc. My version is also v15.2.1', Release: v15.2.1 (Commit: b24b7d5).
[0d00h02m14s] 2023-05-01T06:12:25
"http://192.168.xx.xx/sysinfo" in the browser, the ESP crashes immediately
I can confirm this! We will have a look on it in https://github.com/jomjol/AI-on-the-edge-device/issues/2380
I also can´t take a new reference image
This just got fixed in v15.2.2
"http://192.168.xx.xx/sysinfo" in the browser, the ESP crashes immediately
I can confirm this! We will have a look on it in #2380
Fixed in https://github.com/jomjol/AI-on-the-edge-device/pull/2381
We just released v15.2.3 which contains some bug fixes.
I think this bug report here covers more than one issues, some or all might be fixed by now. Please test the latest release and create a new bug report (separate for each issue) if you still have issues!
This issue gets closed now.
Still got the same error on v15.2.4
Still got the same error on v15.2.4
Please test the latest release and create a new bug report (separate for each issue) if you still have issues!
did you solve this?
I just got the same...
@juhnu1 which version are you using or which version do you want to install?
The Problem
Yesterday my watermeter stopped working. Noticed in HA since not giving values. When I got home I logged into the watermeter device interface to see it saying "Initializing (delayed) but nothing really happens.
Tried updating to the second latest version (due to seeing some people having issues with the latest version?), but still no change. I am not a coding kinda guy, so any help would be much appreciated. What should I do to fix it?
See included log for ref.
Thanks
Version
Release: v15.1.1 (Commit: 03c84a1+)
Logfile
Expected Behavior
No response
Screenshots
Additional Context
No response