ESPEasy v2.0.0-dev12 released

[mrwee]

Well. After playing around this evening I've found:

1) Tried with another flasher (Silicon Labs CP210x USB to UART Bridge). Same result for 2.0.0-dev12 as with the FTDI adapter.
2) Tried to downgrade to 2.0.0-dev11 OTA. Flashing failed.
3) Using flasher, I loaded 2.0.0-dev11 onto one S20 and did the same config as I had before. I could not provoke it to fail.
4) Tried OTA upgrade to 2.0.0-dev12. Flashing failed.

Guess I'll just stay with dev11 for now. Let me know if I can be of any assistance in troubleshooting the problem.

[Shardan]

OTA on a 1MBit ESP-01 will always fail!

The existing ESPEasy-2.0.0-dev11 and the new 2.0.0-dev12 added together is more then 1024KB.

As OTA has to download the binary completely befor it starts flashing there's just not enough memory for that.

See https://letscontrolit.com/wiki/index.php/ESPEasy the "2.0+ firmware on 1MB modules" chapter.

[mrwee]

OTA on a 1MBit ESP-01 will always fail!

The existing ESPEasy-2.0.0-dev11 and the new 2.0.0-dev12 added together is more then 1024KB.

As OTA has to download the binary completely befor it starts flashing there's just not enough memory for that.

See https://letscontrolit.com/wiki/index.php/ESPEasy the "2.0+ firmware on 1MB modules" chapter.

ok. That I should have spotted. Sorry for that. I (now) understand the OTA restrictions, but both should be able to flash from scratch on a 1MB module?

[ensingg]

I've read about a new feature for uploading files in dev12.

Can someone tell me how it works?

[Shardan]

ok. That I should have spotted. Sorry for that. I (now) understand the OTA restrictions, but both should be able to flash from scratch on a 1MB module?

The 1024-Binaries should definitely work on a 1MB module.
Be aware there are some ESP-01 (V3) modules that might cause trouble due to changed pinouts.
If i remember right this was mentioned somewhere in the forum already.

I'll see if i can test the 1024 binariy on ESP-01 this weekend

Regards
Shardan

[mrwee]

ok. That I should have spotted. Sorry for that. I (now) understand the OTA restrictions, but both should be able to flash from scratch on a 1MB module?

The 1024-Binaries should definitely work on a 1MB module.
Be aware there are some ESP-01 (V3) modules that might cause trouble due to changed pinouts.
If i remember right this was mentioned somewhere in the forum already.

I'll see if i can test the 1024 binariy on ESP-01 this weekend

Regards
Shardan

ok, so 2.0.0-dev12 should work on an Sonoff S20? Then I think something happened between dev11 and dev12, causing this issue.

[LisaM]

I've read about a new feature for uploading files in dev12.

Can someone tell me how it works?

Where did you see that

[ensingg]

https://github.com/letscontrolit/ESPEas ... .0.0-dev12

SightofSilence (1):
Add files via upload (#493)

[Shardan]

I don't have S20 at hand so i can't test atm.

If i find some time this weekend i'll test with ESP-01 and possibly a Sonoff basic which is technically equivalent to the S20

[LisaM]

https://github.com/letscontrolit/ESPEas ... .0.0-dev12

SightofSilence (1):
Add files via upload (#493)

I see no such thing as upload... https://github.com/letscontrolit/ESPEasy/pull/493

[ensingg]

I just types what you see on the first screen.

[psy0rz]

https://github.com/letscontrolit/ESPEas ... .0.0-dev12

SightofSilence (1):
Add files via upload (#493)

I see no such thing as upload... https://github.com/letscontrolit/ESPEasy/pull/493

somebody used a wrong commit message, it should read 'Renamed and rearranged "Devices:" on info-page'.

no new upload features, however with tools->flash you can already upload stuff.

[psy0rz]

I don't have S20 at hand so i can't test atm.

If i find some time this weekend i'll test with ESP-01 and possibly a Sonoff basic which is technically equivalent to the S20

shouldnt the ESP8285 version of the firmware be used for a sonof device?

[psy0rz]

I don't have S20 at hand so i can't test atm.

If i find some time this weekend i'll test with ESP-01 and possibly a Sonoff basic which is technically equivalent to the S20

shouldnt the ESP8285 version of the firmware be used for a sonof device?

ah our awesome wiki says the 1mb normal version should be ok indeed. https://www.letscontrolit.com/wiki/inde ... P_Hardware

[grovkillen]

ah our awesome wiki

[papperone]

ah our awesome wiki says the 1mb normal version should be ok indeed. https://www.letscontrolit.com/wiki/inde ... P_Hardware

I think the major issues is that recent Sonoff units (and apparently I've heard recent Wemos D1 mini unit as well) have a different flash chip and if the flash process is done in QIO mode (like we all have been doind so far) will end up in a non working module. The solution is to flash those modules in DIO mode; as well it seems that flashing in DIO mode will in theory free up 2 more GPIOs (9 and 10) but while 10 is reported to work perfectly, 9 is causing ESP8266 reboot (investigation lead to think it's due to some connection track to the flash no needed but still there in the PCB).
As well I've read other users reported that older Sonoff are behaving weird if flashed in DIO mode

Long story short, we should plan a new version of the flash tool that has the option to choose flash mode, either QIO or DIO.

[mrwee]

For my problem with the S20 I think the device is 'as-usual' as espeasy boots & works pretty normal. It seems like when I put configuration on the device, then the error occurs. But only with dev12, not dev11.

[HansV]

As far as I can see TaskValueSet randomly triggers a reboot condition.

I am running dev-12 (4Mb version) on a NodeMCU. Directly after a reboot I initiate a default value (using rule 1).

Code: Select all

On System#Boot do
 TaskValueSet 3,1,0 // Zet de 1e param van dummy task #3 op 0
endon

As far as I can see this is always the trigger for the message "FS : Error while reading/writing config.dat in 926".

Then the device will either reboot directly again, or will keep working for a random time (the highest number I have seen in uptime is 736).

Code: Select all

Oct 28 14:01:22 ESP Unit: 1 : WD   : Uptime 288 ConnectFailures 0 FreeMem 18944
Oct 28 14:01:52 ESP Unit: 1 : WD   : Uptime 288 ConnectFailures 0 FreeMem 18968
Oct 28 14:02:15 ESP Unit: 1 : DS   : Temperature: 31.62 (28-ff-f1-f8-80-17-5-91)
Oct 28 14:02:15 ESP Unit: 1 : EVENT: CV-In#Temperature-In=31.62
Oct 28 14:02:15 ESP Unit: 1 : ACT  : event InlaatTemperatuurOK
Oct 28 14:02:15 ESP Unit: 1 : EVENT: inlaattemperatuurok
Oct 28 14:02:15 ESP Unit: 1 : ACT  : event PompKanAan
Oct 28 14:02:15 ESP Unit: 1 : EVENT: pompkanaan
Oct 28 14:02:15 ESP Unit: 1 : ACT  : TaskValueSet 3,1,1
Oct 28 14:02:30 ESP Unit: 1 : WIFI : Connected! IP: 192.168.11.153 (Nodemcu-CV-ketel_1)
Oct 28 14:02:31 ESP Unit: 1 : EVENT: System#Boot
Oct 28 14:02:31 ESP Unit: 1 : ACT  : TaskValueSet 3,1,0
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : WD   : Uptime 0 ConnectFailures 0 FreeMem 19032

Each reboot takes place directly after executing a TaskValueSet command

Some more info:
- The device that is giving the problems:
* new nodeMCU, flashed with ESPEasy v2.0.0-dev12
* 2 x DS18b20
* 700 mAh poweradapter
I have currently 10 ESPEasy devices active (4 x NodeMCU, 4 x Sonoff S20, 1 x Wemos D1, 1 x Sonoff Basic), all running ESPEasy v2.0.0-dev12.
Only the device running a task that executes TaskValueSet does randomly reboot, all others are very stable.

Any hints to solve this?

Having flashed an Sonoff S20 from scratch, I encounter in the weblog. I've gone over the config again and again but cannot see anything wrong. How can I find the config.dat data structure to locate the problem?

which firmware did you use exactly?

I'm using 'ESPEasy_v2.0.0-dev12_normal_1024.bin' flashed with an FTDI adapter & 'FlashESP8266.exe'.

[mrwee]

As far as I can see TaskValueSet randomly triggers a reboot condition.

I am running dev-12 (4Mb version) on a NodeMCU. Directly after a reboot I initiate a default value (using rule 1).

Code: Select all

On System#Boot do
 TaskValueSet 3,1,0 // Zet de 1e param van dummy task #3 op 0
endon

As far as I can see this is always the trigger for the message "FS : Error while reading/writing config.dat in 926".

Then the device will either reboot directly again, or will keep working for a random time (the highest number I have seen in uptime is 736).

Code: Select all

Oct 28 14:01:22 ESP Unit: 1 : WD   : Uptime 288 ConnectFailures 0 FreeMem 18944
Oct 28 14:01:52 ESP Unit: 1 : WD   : Uptime 288 ConnectFailures 0 FreeMem 18968
Oct 28 14:02:15 ESP Unit: 1 : DS   : Temperature: 31.62 (28-ff-f1-f8-80-17-5-91)
Oct 28 14:02:15 ESP Unit: 1 : EVENT: CV-In#Temperature-In=31.62
Oct 28 14:02:15 ESP Unit: 1 : ACT  : event InlaatTemperatuurOK
Oct 28 14:02:15 ESP Unit: 1 : EVENT: inlaattemperatuurok
Oct 28 14:02:15 ESP Unit: 1 : ACT  : event PompKanAan
Oct 28 14:02:15 ESP Unit: 1 : EVENT: pompkanaan
Oct 28 14:02:15 ESP Unit: 1 : ACT  : TaskValueSet 3,1,1
Oct 28 14:02:30 ESP Unit: 1 : WIFI : Connected! IP: 192.168.11.153 (Nodemcu-CV-ketel_1)
Oct 28 14:02:31 ESP Unit: 1 : EVENT: System#Boot
Oct 28 14:02:31 ESP Unit: 1 : ACT  : TaskValueSet 3,1,0
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : FS   : Error while reading/writing config.dat in 926
Oct 28 14:02:31 ESP Unit: 1 : WD   : Uptime 0 ConnectFailures 0 FreeMem 19032

Each reboot takes place directly after executing a TaskValueSet command

Some more info:
- The device that is giving the problems:
* new nodeMCU, flashed with ESPEasy v2.0.0-dev12
* 2 x DS18b20
* 700 mAh poweradapter
I have currently 10 ESPEasy devices active (4 x NodeMCU, 4 x Sonoff S20, 1 x Wemos D1, 1 x Sonoff Basic), all running ESPEasy v2.0.0-dev12.
Only the device running a task that executes TaskValueSet does randomly reboot, all others are very stable.

Any hints to solve this?

which firmware did you use exactly?

I'm using 'ESPEasy_v2.0.0-dev12_normal_1024.bin' flashed with an FTDI adapter & 'FlashESP8266.exe'.

I'm getting the "Error while reading/writing config.dat in 926" with just:

on onoff#push=1 do
if [relay#Switch]=1
gpio,12,0
else
gpio,12,1
endif
endon

in my rules . See it on different devices.

[kociubin]

I'm getting the "Error while reading/writing config.dat in 926" with just:

on onoff#push=1 do
if [relay#Switch]=1
gpio,12,0
else
gpio,12,1
endif
endon

Same here. Getting ""Error while reading/writing config.dat" for every rule that has an if statement. I'm running a bunch for Wemos D1's and ESP-12's.

[grovkillen]

Please report on GitHub.

[vader]

Had the same. Just make a reset and config the ESP from scratch (no config restore to be sure!). After that:

Rule:
on Button#State do
if [Button#State]=1
event switchon
else
event switchoff
endif
endon

[Submit]

Log:
197926 : FILE : Saved config.dat
197951 : FILE : Saved security.dat

[Shardan]

I've configured a "blank" ESP-12E for my dust sensor prototype with 2.0.0-DEV12 TESTING, sources Oct.25. '17.
No issues even with a lot of rules.

[mrwee]

I'm able to reproduce this across different ESP8266 based products: Sonoff Basic, Sonoff S20, Sonoff TH16 & Wemos D1 mini pro.
My settings are:
- Various names for the device, e.g. "Garden light east"
- Different Unit ID's (e.g. 95, 128, 136)
- Static IP address
- OpenHAB MQTT with IP address
- NTP server set to IP addess
- Two devices configured: Button & Relay GPIO's

To me it seems like when the rule(s) become too long, the error occurs. I cannot reproduce at all with dev11.

Edit: Most tests have been performed with freshly flashed devices. Have also tried the 'reset' command, and starting all-over. Same result.

[mrwee]

This rule:

On System#Boot do //When the ESP boots, do
publish %sysname%/sysname,%sysname%
publish %sysname%/IP,%ip%
publish %sysname%/relay/Switch,[relay#Switch]
timerSet,1,60 //Set Timer 1 for the next event in 30 seconds
endon

On Rules#Timer=1 do //When Timer1 expires, do
publish %sysname%/relay/Switch,[relay#Switch]
timerSet,1,60 //Resets the Timer 1 for another 30 seconds
endon

results in the 'FS : Error while reading/writing config.dat in 926" error on one Sonoff TH10, but not on another TH10. Settings are identical (besides the obvious IP, device ID etc.).

If I change it to:

On System#Boot do //When the ESP boots, do
publish %sysname%/sysname,%sysname%
publish %sysname%/IP,%ip%
publish %sysname%/relay/Switch,[relay#Switch]
endon

then it works.

If I change it to:

on onoff#push=1 do
if [relay#Switch]=1
gpio,12,0
else
gpio,12,1
endif
endon

I get the error on the same module, but not the other.

If I change it to:

on onoff#push=1 do
endon

then no error.

Seems to me, that it could be related to the size of the rule.