Boot time very high

[moebius]

On a Wemos D1, the time from a warm reboot until the device outputs a pwm signal is app. 5 seconds.
The pwm signal is defined with this rule:

on System#Boot do
PWM,14,450,3000
endon

This is way too much to use it for a light.
The normal boot time of an esp8266 is around 300ms - why does it take so long with espeasy?

[Micha_he]

Maybe DHCP?

[Domosapiens]

Talking about an official Wemos D1 or a fake ?
This is the official:

5-Stks-partij-D1-mini-Mini-Voor-NodeMcu-4-M-bytes-Lua-WIFI-Internet-van-Dingen.jpg

From here https://nl.aliexpress.com/item/5PCS-lot ... Title=true
See the branding on the chip and board.

I have 2# "fake" Wemos D1 boards, without branding with a lot of problems:
- overly power hungry
- weak WiFi connection
- large start-up time

My other 10+ Wemos D1's (with branding) don't have that problem.

[moebius]

Don't know if it's fake, so let's assume it is...but with none of your problems (wifi connection, power consumption (i dont use the onboard regulator)).

I have also some nodemcu boards - i will check, if there is any difference...

My guess would also be, that espeasy does the startup task only after everything else is up (wifi + dhcp, maybe mqtt connection,...)
But for "switched on" devices, this is way too long...i'm wondering that nobody else has this probem, so maybe it's really the board.

[moebius]

I've tested now with a nodemcu board and nothing changed...

But the log showed clearly where the time has gone:

Code: Select all

349 : EVENT: System#Boot
380 : ACT : PWM,14,450,3000
3491 : SW : GPIO 14 Set PWM to 450
4463 : WIFI : AP Mode disabled
4464 : WIFI : AP Mode ssid will be laserbeam_55 with address 192.168.4.1
4464 : WIFI : Connecting Portal attempt #1
8282 : WIFI : Connected! IP: 192.168.4.211 (laserbeam_55)
8347 : MQTT : ClientID laserbeam55 connected to broker
8352 : Subscribed to: laserbeam/#

This is the log with a modified espeasy.ino, where i moved the network initialization behind the plugins and rules processing. Otherwise the event and act entries show up after the subscribed entry (8 seconds later in this case).
Now the esp acts like a microcontroller and not win95

I think this should be the default behavior.

[grovkillen]

Please report to Github.