Let's Control It

Hi folks.

i've running a sonoff with espeasy mega-20191116 more than 2 weeks without problems. Connected to my own WLAN.
Since about 3 days i can't connect anymore.
on the serial interface i see alsways reconnects with error 200 Beacon timeout. i try also other AP's(on other locations) with change the settings by serial -> no success
i try also on the serial the cmd : reset , but the configured SSID and Key stay stored

is there any other information i can find on the Sonoff? After flashing, i have the same problem....

ESPCore: 2_5_2 SDK: 2.2.1

thanks for any hint.

pat

If you reboot (power cycle) the unit, is it then able to reconnect like it should? (and stable)

TD-er wrote: ↑19 Nov 2019, 13:31 If you reboot (power cycle) the unit, is it then able to reconnect like it should? (and stable)

No, i take it to a other location (without a power bank )

Could it be that the supplied voltage to the ESP is lower than when you started?
The voltage of the ESP chip itself has to do with how the RF part (WiFi) is working.
At start of the WiFi, the ESP performs a calibration which is based on the current voltage of the ESP module.
If that voltage drops, it will have a lot more difficulty to have a stable WiFi connection, or even to see all nodes when scanning.

TD-er wrote: ↑19 Nov 2019, 13:42 Could it be that the supplied voltage to the ESP is lower than when you started?

No, is the same. I also tried with the AC power.

TD-er wrote: ↑19 Nov 2019, 13:42 The voltage of the ESP chip itself has to do with how the RF part (WiFi) is working.
At start of the WiFi, the ESP performs a calibration which is based on the current voltage of the ESP module.
If that voltage drops, it will have a lot more difficulty to have a stable WiFi connection, or even to see all nodes when scanning.

But the errors are always the same. (AC and DC)

after a while now.....
but no web interface (also no ping)

Is it possible the accesspoint is hitting some maximum in number of connected clients?
The beacon timeout is something that can happen all the time, but not as frequent as you're seeing here.

There are other reasons why it may happen:
- ESP is running some tasks which are blocking for a while.
- Running with "eco mode" enabled (Tools => advanced)

TD-er wrote: ↑19 Nov 2019, 16:13 Is it possible the accesspoint is hitting some maximum in number of connected clients?

i think not. i test it with 3 different AP's

TD-er wrote: ↑19 Nov 2019, 16:13
There are other reasons why it may happen:
- ESP is running some tasks which are blocking for a while.
- Running with "eco mode" enabled (Tools => advanced)

i send many times the command "reset" on the serial interface. on the wiki, with "reset" they are all settings erased. But i describe above, after that,
the sonoff takes always the connection of the last SSID again
so is there all erased or not?!

Depends, did these unit ever run another firmware before ESPEasy?
(or an old version, older than 2 years old)

Then there may be stored some WiFi credentials which may be used by the ESP to perform a reconnect.

It is also possible the reset is not performed well, or you have set on the factory reset page to keep some settings?

TD-er wrote: ↑19 Nov 2019, 22:45 Depends, did these unit ever run another firmware before ESPEasy?
(or an old version, older than 2 years old)

No, it only run's on a ESPEasy Firmware 20191119. And it run's for about 2 or 3 weeks without problems....

TD-er wrote: ↑19 Nov 2019, 22:45 Then there may be stored some WiFi credentials which may be used by the ESP to perform a reconnect.

It is also possible the reset is not performed well, or you have set on the factory reset page to keep some settings?

it try's to connect to the last SSID i configure.

is there another way to reset the sonoff to it's factory?

To factory, no, drive är since you flashed it with ESP Easy. But if you have a physical connection to it you may want to flash a "blank" bin file before flashing the firmware.

Connecting RX and TX on the ESP at boot should also trigger a full reset to factory defaults (without keeping settings)

I'm always flashing a blank bin file, before flashing the mega-xxxxx

Now, i read in the wiki, after flashing and rebooting : Waiting about 5Min.
Is the bin file extracting after a reboot and takes so long?!

So i will test this szenario...

valbuz99 wrote: ↑20 Nov 2019, 14:51 Now, i read in the wiki, after flashing and rebooting : Waiting about 5Min.
Is the bin file extracting after a reboot and takes so long?!

So i will test this szenario...

Hmm that's way longer than usual.
You can also track the progress of booting via a serial monitor (e.g. Putty via the COM port, use 115200 baud)

so... i flash a new bin-file (mega-20191116)
here a screenshot form serial. the websever was not reachable.

So......

I change the hole HW and now it works again