Page 1 of 1

ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 01:38
by psy0rz
After a brief pause, i'm back, and we've released v2.0.0-dev12: https://github.com/letscontrolit/ESPEas ... .0.0-dev12

From this point forward the 2.0.0 merge window is closed. This means only bugfixes will go into 2.0.0: All the other pull requests will be postponed to 2.1.0.

From now on I will focus only on fixing bugs for 2.0.0 and working towards a beta release of version 2.0.0.

A current list with bugs that need to be fixed before a 2.0.0 release can be found here: https://github.com/letscontrolit/ESPEasy/milestone/1

Theoretically its possible to create a separate 2.0.0 development branch so that we also can continue merging pull requests for 2.1.0 in the mega-branch, but we do not have enough resources for this. So instead, i'll only merge fixes and leave the other pull requests open for 2.1.0.

There's an extensive list of issues on github (https://github.com/letscontrolit/ESPEasy/issues): If you spot a 2.0.0 issue that doesnt have the correct milestone yet, leave a comment on github.

Edwin

Re: ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 08:17
by toffel969
Thanks for all your hard work

Re: ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 08:19
by grovkillen
Great work everyone involved!

Re: ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 08:40
by papperone
thanks! will install it immediately on my test modules to provide feedback on stability :)

Re: ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 09:49
by AndrewJ
Thanks to all who have worked hard to get this ready for release! A major milestone! 😁

Re: ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 13:02
by papperone
Just a small though on size and efficiency...

I agree that some plugins are too specific and should be flagged as such and not included in the standard firmware (like it happened with "_P070_NeoPixel_Clock.ino").
But looking at the current supported devices by the standard 2.0.0.dev12 I think there are below plugins which are the same if not less generic than the one above like "_P041_NeoClock.ino" which shoudl be flagged the same way to make sure the "core" set of plugins is quite generic, including general available sensors/devices rather than very specific ones.

It's only my 2cents as this is my personal view of how I see ESPEasy core modules...

Re: ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 13:07
by Shardan
Agree with papperone.

Good job guys.

Re: ESPEasy v2.0.0-dev12 released

Posted: 22 Sep 2017, 16:42
by ManS-H
Good job Edwin, thanks.

Re: ESPEasy v2.0.0-dev12 released

Posted: 23 Sep 2017, 14:43
by Martinus
Just noticed that the IR plugin is missing from the default set of plugins.
Seems to be the only plugin with this condition:
#ifdef PLUGIN_BUILD_NORMAL
and it's not set true in the main file.

Was there a reason to disable this plugin (it has been in the default set for a long time..)

Re: ESPEasy v2.0.0-dev12 released

Posted: 23 Sep 2017, 14:47
by psy0rz
papperone wrote:
22 Sep 2017, 13:02
Just a small though on size and efficiency...

I agree that some plugins are too specific and should be flagged as such and not included in the standard firmware (like it happened with "_P070_NeoPixel_Clock.ino").
But looking at the current supported devices by the standard 2.0.0.dev12 I think there are below plugins which are the same if not less generic than the one above like "_P041_NeoClock.ino" which shoudl be flagged the same way to make sure the "core" set of plugins is quite generic, including general available sensors/devices rather than very specific ones.

It's only my 2cents as this is my personal view of how I see ESPEasy core modules...
yes i agree. i only started doing this recently because the number of plugins seems to be skyrocketting. :) maybe we should disable more plugins that are too specific.

Re: ESPEasy v2.0.0-dev12 released

Posted: 23 Sep 2017, 14:47
by psy0rz
Martinus wrote:
23 Sep 2017, 14:43
Just noticed that the IR plugin is missing from the default set of plugins.
Seems to be the only plugin with this condition:
#ifdef PLUGIN_BUILD_NORMAL
and it's not set true in the main file.

Was there a reason to disable this plugin (it has been in the default set for a long time..)
nope this is a bug. i'll look into it. "normal" plugins should be always compiled.

Re: ESPEasy v2.0.0-dev12 released

Posted: 26 Sep 2017, 16:03
by mrwee
Having flashed an Sonoff S20 from scratch, I encounter
Error while reading/writing config.dat in 926
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?

Re: ESPEasy v2.0.0-dev12 released

Posted: 27 Sep 2017, 23:01
by TD-er
psy0rz wrote:
23 Sep 2017, 14:47
papperone wrote:
22 Sep 2017, 13:02
Just a small though on size and efficiency...

I agree that some plugins are too specific and should be flagged as such and not included in the standard firmware (like it happened with "_P070_NeoPixel_Clock.ino").
But looking at the current supported devices by the standard 2.0.0.dev12 I think there are below plugins which are the same if not less generic than the one above like "_P041_NeoClock.ino" which shoudl be flagged the same way to make sure the "core" set of plugins is quite generic, including general available sensors/devices rather than very specific ones.

It's only my 2cents as this is my personal view of how I see ESPEasy core modules...
yes i agree. i only started doing this recently because the number of plugins seems to be skyrocketting. :) maybe we should disable more plugins that are too specific.
Or perhaps merge similar plugins, like the Bosch BMx280 temperature sensors (a pull request I already made).
Another thing that is somewhat bothering me, is the webserver "plugin", which is handling strings in memory of up to 10 kByte. That's heap fragmentation waiting to happen.

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 00:07
by psy0rz
psy0rz wrote:
23 Sep 2017, 14:47
Martinus wrote:
23 Sep 2017, 14:43
Just noticed that the IR plugin is missing from the default set of plugins.
Seems to be the only plugin with this condition:
#ifdef PLUGIN_BUILD_NORMAL
and it's not set true in the main file.

Was there a reason to disable this plugin (it has been in the default set for a long time..)
nope this is a bug. i'll look into it. "normal" plugins should be always compiled.
fixed in commit 20b95c4

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 00:08
by psy0rz
mrwee wrote:
26 Sep 2017, 16:03
Having flashed an Sonoff S20 from scratch, I encounter
Error while reading/writing config.dat in 926
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?

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 09:10
by mrwee
psy0rz wrote:
28 Sep 2017, 00:08
mrwee wrote:
26 Sep 2017, 16:03
Having flashed an Sonoff S20 from scratch, I encounter
Error while reading/writing config.dat in 926
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'.

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 10:48
by grovkillen
mrwee wrote:
28 Sep 2017, 09:10
I'm using 'ESPEasy_v2.0.0-dev12_normal_1024.bin' flashed with an FTDI adapter & 'FlashESP8266.exe'.
Is the programmer a original FTDI one or a copy? The newer drivers are making clones/copies garbaging the flash even though it says "ok".

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 11:01
by TD-er
grovkillen wrote:
28 Sep 2017, 10:48
mrwee wrote:
28 Sep 2017, 09:10
I'm using 'ESPEasy_v2.0.0-dev12_normal_1024.bin' flashed with an FTDI adapter & 'FlashESP8266.exe'.
Is the programmer a original FTDI one or a copy? The newer drivers are making clones/copies garbaging the flash even though it says "ok".
What version of the drivers are causing this? And what version is still working?
Or is it once being used with newer drivers, the clones are defective forever?

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 12:34
by mrwee
grovkillen wrote:
28 Sep 2017, 10:48
mrwee wrote:
28 Sep 2017, 09:10
I'm using 'ESPEasy_v2.0.0-dev12_normal_1024.bin' flashed with an FTDI adapter & 'FlashESP8266.exe'.
Is the programmer a original FTDI one or a copy? The newer drivers are making clones/copies garbaging the flash even though it says "ok".
Good question. How do I tell? I've programmed ~20 ESP's (Sonoff Basic, POW, TH10/TH16, H801) with this programmer and the S20 with v2.0.0-dev12 works fine besides this error message (I've flashed 3 x S20 with 2.0.0-dev12, they all behave this way).
I've fiddled around with different settings, and if I e.g. remove a very simple rule, then it sometimes stops with this error. An S20 with early v2 espeasy does not have this problem, so my assumption is that it's something introduced with dev12.

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 14:01
by grovkillen
Regarding drivers, I'm not sure since I have only used official FTDI (got them at work). But I would say the last year. I believe that they alter the FW in the clone as well (don't quote me on that one though).

How do you tell if you have a clone or not? Simple, what price you pay? Less than $15 or so and you'll have bought a clone. I don't think many genuine FTDI is sold through AliExpress or Ebay.

If you have been able to flash an earlier FW version (dev7 or so) and got it working correct you might want to try the OTA FW update to bump that without the use of a programmer... just as an test?

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 20:27
by 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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 28 Sep 2017, 22:06
by 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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 09:39
by mrwee
Shardan wrote:
28 Sep 2017, 22:06
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?

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 11:34
by ensingg
I've read about a new feature for uploading files in dev12.

Can someone tell me how it works?

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 13:04
by Shardan
mrwee wrote:
29 Sep 2017, 09:39
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

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 13:10
by mrwee
Shardan wrote:
29 Sep 2017, 13:04
mrwee wrote:
29 Sep 2017, 09:39
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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 13:17
by LisaM
ensingg wrote:
29 Sep 2017, 11:34
I've read about a new feature for uploading files in dev12.

Can someone tell me how it works?
Where did you see that :?:

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 13:20
by ensingg
https://github.com/letscontrolit/ESPEas ... .0.0-dev12

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

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 13:28
by 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

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 14:48
by LisaM
ensingg wrote:
29 Sep 2017, 13:20
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

Re: ESPEasy v2.0.0-dev12 released

Posted: 29 Sep 2017, 14:53
by ensingg
I just types what you see on the first screen.

Re: ESPEasy v2.0.0-dev12 released

Posted: 04 Oct 2017, 17:12
by psy0rz
LisaM wrote:
29 Sep 2017, 14:48
ensingg wrote:
29 Sep 2017, 13:20
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. :)

Re: ESPEasy v2.0.0-dev12 released

Posted: 04 Oct 2017, 17:13
by psy0rz
Shardan wrote:
29 Sep 2017, 13:28
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?

Re: ESPEasy v2.0.0-dev12 released

Posted: 04 Oct 2017, 17:15
by psy0rz
psy0rz wrote:
04 Oct 2017, 17:13
Shardan wrote:
29 Sep 2017, 13:28
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 :)

Re: ESPEasy v2.0.0-dev12 released

Posted: 04 Oct 2017, 17:54
by grovkillen
psy0rz wrote:
04 Oct 2017, 17:15
ah our awesome wiki
:mrgreen:

Re: ESPEasy v2.0.0-dev12 released

Posted: 04 Oct 2017, 17:58
by papperone
psy0rz wrote:
04 Oct 2017, 17:15
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 :o

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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 04 Oct 2017, 19:52
by 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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 31 Oct 2017, 12:57
by 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?
mrwee wrote:
28 Sep 2017, 09:10
psy0rz wrote:
28 Sep 2017, 00:08
mrwee wrote:
26 Sep 2017, 16:03
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'.

Re: ESPEasy v2.0.0-dev12 released

Posted: 02 Nov 2017, 20:41
by mrwee
HansV wrote:
31 Oct 2017, 12:57
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?
mrwee wrote:
28 Sep 2017, 09:10
psy0rz wrote:
28 Sep 2017, 00:08


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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 13 Nov 2017, 04:15
by 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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 13 Nov 2017, 12:26
by grovkillen
Please report on GitHub.

Re: ESPEasy v2.0.0-dev12 released

Posted: 13 Nov 2017, 19:04
by 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

:D

Re: ESPEasy v2.0.0-dev12 released

Posted: 13 Nov 2017, 19:59
by 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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 13 Nov 2017, 21:16
by 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.

Re: ESPEasy v2.0.0-dev12 released

Posted: 14 Nov 2017, 22:23
by 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.