Open luebbe opened 4 years ago
There are two places where wdtFeed is used to avoid this problem. Your analysis is probably correct in that dumphex takes a long time to run and blocks WiFi causing a WDT reset - the "classic ESP8266 problem". It is precisley why I took the exceptional step of "feeding the watchdog"
I thought I had solved this with the wdtFeed, obviously I will need to look into it again. Thanks for your diligence and support.
Steps to reproduce:
The last messages are:
The decoded stack trace is:
Probably it's just the
PANGO::dumphex(payload,len,16);
call needing too much time, because when I comment it out, the WDT reset doesn't occur.