Let's Control It

hi!

I've been developing a plugin and all ws going well but now espeasy keeps crashing.

I got rid of plugin, recompiled but same problem.

Re downloaded source and compiled uploaded same problem.

Tried different chip same problem.

Once I've entered the wifi details on 192.168.4.1 it reboots and i can connect ok.

HOWEVER, as soon as i reboot it all goes wrong - web won't connect and it reboots itself every minute or so.

serial output:

wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v614f7c32
~ld
���U57 :

The serial is usually unresponsive but sometimes i can sneak in a reset command.

The config ap then comes backup on 192.168.4.1

trying to connect often results in a chip reboot.

Sometimes I see a message saying not enough memory to show web page..

eventually the usual wifi list comes up and i can start all over again - leave it there and the chips rebooots after a few minutes...

i've rebooted routers/switches etc just in case.


anyone got any ideas?

Flashed a blank bin?

Yep did that just in case


Anyways I've solved it sort of.

I forgot I was running a macro on the source to remove unneeded plugins.

It seems that at least one is required or the problems ensue!

I've have to work through the 40+ plugins I remove to see which one causes the problem - a task which will take days!!

What was the plugin that was really required?
Maybe I can add a remark to it to help others.

TD-er wrote: ↑28 May 2019, 10:55 What was the plugin that was really required?
Maybe I can add a remark to it to help others.

Hiya, not finished my hunting as yet but will let you know

Just had my self build reset due to watchdog.
This isn't good as it's not running any sensors, only plugin active is to drive my servos in my blinds so just inactive except for 10 seconds a day lol.

Cant see it being a plugin if none are configured so guess it must be a problem with base framework eek

How to debug?

None of my other esps have reset and the other blind running same firnware hasn't reset yet. Maybe a blip on the psu...

It can also happen when the ESP is waiting for a reply on some network connection.
Something like NTP request can also trigger this I guess.

There have been some fixes lately regarding timeout settings not being honored.
These are present in core 2.5.2, so you may want to try that one.
But there are more possible causes for WDT resets.