Problems with the current mega version

[micropet]

Good Morning all.
The current mega version is not really working yet.
Board Wemos D1 without external hardware compiled with Arduino 1.8.5.
I get:

19802 : WIFI : Connected! AP: SMC (C8:0E:14:05:BC:C6) Ch: 11 Duration: 3777 ms
19803 : EVENT: WiFi#ChangedAccesspoint
19824 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 23 ms
19835 : EVENT: WiFi#Connected
19934 : MQTT : Intentional reconnect
24958 : MQTT : Failed to connect to broker
32012 : Current Time Zone: DST time start: 2018-03-25 02:00:00 offset: 120 minSTD time start: 2018-10-28 03:00:00 offset: 60 min
32013 : EVENT: Time#Initialized
32020 : EVENT: Clock#Time=Fri,08:37
32023 : MQTT : Intentional reconnect
37047 : MQTT : Failed to connect to broker
37056 : MQTT : Intentional reconnect
42078 : MQTT : Failed to connect to broker
42085 : MQTT : Intentional reconnect
47109 : MQTT : Failed to connect to broker
47115 : WD : Uptime 1 ConnectFailures 0 FreeMem 12256
47116 : MQTT : Intentional reconnect
52139 : MQTT : Failed to connect to broker
52141 : MQTT : Intentional reconnect
57164 : MQTT : Failed to connect to broker
57170 : MQTT : Intentional reconnect
62195 : MQTT : Failed to connect to broker
62202 : MQTT : Intentional reconnect
67228 : MQTT : Failed to connect to broker
67237 : MQTT : Intentional reconnect
72261 : MQTT : Failed to connect to broker
72269 : MQTT : Intentional reconnect
77292 : MQTT : Failed to connect to broker
77297 : WD : Uptime 1 ConnectFailures 0 FreeMem 12560
77298 : MQTT : Intentional reconnect
82321 : MQTT : Failed to connect to broker
82327 : WIFI : AP Mode Disabled for SSID: ESP-201_1
82328 : WIFI : Set WiFi to STA
82344 : EVENT: WiFi#Disconnected
82347 : WIFI : Disconnected! Reason: 'Assoc leave' Connected for 1 m 2 s
82347 : WIFI : Connecting SMC attempt #0
83546 : WIFI : Connected! AP: SMC (C8:0E:14:05:BC:C6) Ch: 11 Duration: 1198 ms
83565 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 19 ms
83577 : EVENT: WiFi#Connected
83676 : MQTT : Intentional reconnect
83751 : MQTT : Connected to broker with client ID: ESPClient_5C:CF:7F:0B:68:52
83753 : Subscribed to: ESP-201/#
83754 : EVENT: MQTT#Connected
84617 : EVENT: Time#Set
done.

ets Jan 8 2013,rst cause:4, boot mode:(1,7)

wdt reset

[TD-er]

What version is this? (file used to flash, or preset used to build yourself)

And did you also test a reset/restart of the node after flashing and setup of wifi?

[micropet]

Self-compiled.
The wifi settings are still saved because the device was still online until yesterday.
Reset and poweroff was done.

Oh, after about 15 times Poweroff it works.
I have to watch that now.

[TD-er]

That's really strange. Maybe it is trying to fast and deciding to give up too soon?

[TD-er]

What version did you compile? 'normal' or one of the others?
The normal uses core 2.4.0, which fixes some issues wrt. wifi.
You can see the used core version in the info page.

[micropet]

This one:

Firmware
Build | 20101 - Mega (core 00000000)
GIT version | (custom)
Plugins | 71 [Normal] [Testing] [Development]
Build Md5 | 4d44355f4d44355f4d44355f4d44355f
Md5 check | fail !
Build time | Apr 13 2018 11:26:14
Binary filename | ThisIsTheDummyPlaceHolderForTheBinaryFilename...

At the moment it is running.
I'll try another Wemos D1 right away

Is Md5 check | fail OK?

[TD-er]

Yep, since you don't "sign" your builds with the proper MD5sum, like we do with the daily builds.

The 71 plugins indicate "dev" build, but "core 0000..." looks like staging version of core. (Arduino ESP8266 core 2.4.x)
If you could try the pre built version of "normal" version. That one uses core 2.4.0
The dev and test versions are built with core 2.3.0, since the 2.4.x version uses too much memory, what will lead to all kinds of issues. In the tests I ran yesterday, I had sometimes issues with saving settings, since the memory was full.

[micropet]

I think that the normal version does not have all the plugins I need.

MH-Z19, VEML6040, SDS011 ....

The Arduino IDE uses Core 2.4.0.
I have the ESP8266 sources from here:
https://github.com/esp8266/Arduino/commits/master

[TD-er]

I'm not sure about the VEML6040, but the other two are included in the normal version.
You can also add others by setting defines.
But I really have to look into the memory usage.

[v-a-d-e-r]

@TD-er : A lot of problems now with last night changes. Pls check PM in forum....

[TD-er]

I will later this evening.

[wdonker]

Same problem (as mentioned in post 1) with mega-20180414.
And when I reinstall 20180407 (which was ok before) the MQTT connection keeps failing.
The log complains about settings CRC so maybe 20180414 broke something there:

INIT : Booting version: mega-20180407
INIT : Warm boot #1
FS : Mounting...
FS : Mount successful, used 76555 bytes of 957314
CRC : program checksum ...OK
CRC : Settings CRC ...FAIL
CRC : SecuritySettings CRC ...OK

[micropet]

Nothing has changed here.
The device connects very slowly to the network and it takes a long time until an MQTT connect takes place.

The web server is also rarely reachable.

[TD-er]

How do you connect to the MQTT broker?
Hostname or IP?

[wdonker]

My ESP connects using IP.
I flashed an empty bin to clear the settings and reflashed 20180407. It's working ok now.

[TD-er]

And the same for the last version?
The CRC settings were corrupted (only the unused settings and the checksum) in the last few builds, which was corrected in the 20180413 build.
The problem was that there were some settings added at the position of the checksum. So the checksum was incorrect and save would corrupt the settings again.
In the last 2 builds, the checksum would be correct again and a simple save in those builds would make the checksum match again.