Let's Control It

Yes! We start the year with lucky number 13, this should be a good one.

You can download it here: https://github.com/letscontrolit/ESPEas ... .0.0-dev13

I want to ask everyone to use the "voting" feature of github to let us know which features or issues are important to you. You can use the +:) button on the first comment to give the issue a thumbs up. This helps us to prioritize things a lot.

Issues that need to be fixed for a stable v2.0.0 release: https://github.com/letscontrolit/ESPEasy/milestone/1

ALL the issues: https://github.com/letscontrolit/ESPEasy/issues

Happy new year!

Edwin

Happy New Year and ..
Congrats to Edwin and ESP Easy contributors

psy0rz wrote: ↑02 Jan 2018, 23:34 Issues that need to be fixed for a stable v2.0.0 release: https://github.com/letscontrolit/ESPEasy/milestone/1

Very nice, good work! Looking forward to testing .

I don't quite understand why the KRACK fix is not prioritized?
Given that all communication to/from ESPEasy can be eavesdropped and is not encrypted in itself (e.g. MQTT username+password, webpage login password etc.) I think a fix should have a higher focus.

mrwee wrote: ↑03 Jan 2018, 13:01

psy0rz wrote: ↑02 Jan 2018, 23:34 Issues that need to be fixed for a stable v2.0.0 release: https://github.com/letscontrolit/ESPEasy/milestone/1

Very nice, good work! Looking forward to testing .

I don't quite understand why the KRACK fix is not prioritized?
Given that all communication to/from ESPEasy can be eavesdropped and is not encrypted in itself (e.g. MQTT username+password, webpage login password etc.) I think a fix should have a higher focus.

I suspect we are waiting for libraries to be updated and tested before implementing them into ESP Easy.

ok. Just noticed that Tasmota & Espurna have updated, so I assumed that it was ok to update ESPEasy as well.

We cannot fix that bug i think, the fix needs to be done in the arduino/esp core libraries.

Also if you patch your accesspoint you should be fine i think? Thats what i did with my unifi accesspoints.

Correct me if i'm wrong and if we CAN do something about KRACK.

From what I've read (https://www.krackattacks.com/#patch-client-and-ap):

Is it sufficient to patch only the access point? Or to patch only clients?

Currently, all vulnerable devices should be patched. In other words, patching the AP will not prevent attacks against vulnerable clients. Similarly, patching all clients will not prevent attacks against vulnerable access points. Note that only access points that support the Fast BSS Transition handshake (802.11r) can be vulnerable.

That said, it is possible to modify the access point such that vulnerable clients (when connected to this AP) cannot be attacked. However, these modifications are different from the normal security patches that are being released for vulnerable access points! So unless your access point vendor explicitly mentions that their patches prevent attacks against clients, you must also patch clients.

and under "Arduino": https://github.com/kristate/krackinfo#v ... e-complete: (Don't know what they actually mean )

EspressIf fixed its ESP8266 SDK in upstream (see also row "Espressif Systems" in this table below); SDK Fix is on the way

From an general perspective, I'd rather that my Wi-Fi devices were patched, than my AP vendor implements counter-measurements. But I also acknowledge the fact that a lot of devices, never will be patched as they're either End-of-life, (too) cheap or it's just not a focus from the company (e.g. Broadlink who does not seem to care). I can either live with that knowledge/risk or buy new devices.

But since I've now got ~30 ESPEasy based devices running, spread around the garden & our house, they're much more subject to the "outside" than the IR blaster in the basement.

Ah thanks for that information. So its just a matter of waiting until espressive has updated their libraries.

AFAIK, the KRACK issue has been solved already a while ago in the SDK and it's now part of Arduino Core 2.4.0 release that has recently changed to stable release (2 days ago)

It's this closed issue on github:
https://github.com/esp8266/Arduino/issues/3725

I didn't run any tests on stable 2.4.0 but have run a module on 2.4.0.RC2. I remember that there was a HUGE drop in available RAM, especially during web handling functions.
That could potentially be a real showstopper for ESP Easy running on 2.4.0.

Martinus wrote: ↑03 Jan 2018, 19:18 AFAIK, the KRACK issue has been solved already a while ago in the SDK and it's now part of Arduino Core 2.4.0 release that has recently changed to stable release (2 days ago)

It's this closed issue on github:
https://github.com/esp8266/Arduino/issues/3725

I didn't run any tests on stable 2.4.0 but have run a module on 2.4.0.RC2. I remember that there was a HUGE drop in available RAM, especially during web handling functions.
That could potentially be a real showstopper for ESP Easy running on 2.4.0.

Oooo, I hope it is within reasonable limits, if not we'd have to ditch the update I guess.

What a good news !!!

I am not able to compile the last dev by my own with Arduino IDE :

"make": executable file not found in %PATH%

Tried many different libraries and different board version

Somebody has an idea because I'm dry...

Someone already tested to build 2.4.0 RC-somewhat and ran into some issues.
also if I remember correctly, 2.4.0 leaves less RAM to work with.

Just some feedback:
dev13 has greatly improved stability of my ESP running as P1 smart meter interface. On dev12 it rebooted once or twice a day and now it is running for 2,5 days without reboot.
Also the P1 event handling time is much less than before.
This was my only ESP that spontanously rebooted; I have others running dev12 for almost 3 months without reboots.
Thank you!

Hmm great to hear, but from a programmer perspective, I am curious what may have changed that affects this.
How do you interface to the P1 smart meter? Are you using software serial?

I use the P044_P1WifiGateway which was changed in dev13 but I've no idea if that could be the causel

There are still some serious crash issues with dev13 and older, and MQTT. We're fixing that now.

Maybe a very stupid question, but ... what is the difference between V2.0.13 etc and a mega release?
I thought mega releases were no longer made?

BertB wrote: ↑10 Jan 2018, 17:38 Maybe a very stupid question, but ... what is the difference between V2.0.13 etc and a mega release?
I thought mega releases were no longer made?

Mega is the project name for v2.0.0 and it's also the name of the master branch. "v2.0" the name of the branch that is the code submitting branch, where all the development goes into. When "v2.0" reach a okay level it is merged with "mega" and a devXX compilation is made. Nightly build is a new approach where the "v2.0" branch is compiled each night IF new code is added.

I hope it makes sense. @psy0rz correct me if I'm wrong.

So, if I understand correctly, I can continue using the V2 versions.
V2 contains all the goodies developed in mega ... correct?

Thanks for explaining

Yes

grovkillen wrote: ↑10 Jan 2018, 17:51

BertB wrote: ↑10 Jan 2018, 17:38 Maybe a very stupid question, but ... what is the difference between V2.0.13 etc and a mega release?
I thought mega releases were no longer made?

Mega is the project name for v2.0.0 and it's also the name of the master branch. "v2.0" the name of the branch that is the code submitting branch, where all the development goes into. When "v2.0" reach a okay level it is merged with "mega" and a devXX compilation is made. Nightly build is a new approach where the "v2.0" branch is compiled each night IF new code is added.

I hope it makes sense. @psy0rz correct me if I'm wrong.

No thats not correct, but things changed quite a few times so i understand the confusion.

TL;DR: mega=unstable and has all the new features and fixes. v2.0=next upcoming stable v2.0.0 release. (no new features since Oct 12 2017)


mega: This is where all the new development and new features go in. Other projects would call this "unstable" or "development". It has the newest features, but is totally untested since new stuff is added all the time. (Normally this should be called "master", but I think we keep it "mega" now, otherwise we break a lot of links and stuff)

v2.0: At a certain points in time we make a "copy" (actually a "branch") of mega and try to fix all the bugs to get a stable release out. We've done this at Oct 12 2017 and called it the v2.0 branch. Fixes that are done here are also "merged" back into mega from time to time so that we dont have to do stuff twice. (this is why we use git, it can do most of these merges automaticly) So the v2.0 branch did not get any real new features since Oct 12 2017, only fixes.

Until now we've called a v2.0 builds something like v2.0-dev13, but i'm changing it to nightly builds as well. So the next build will be something like v2.0-20181003 and will be released automatically every night if there are changes. This makes it easier for people to test stuff. Especially since arduino core 2.4.0 gives us a whole bunch of new issues. (Our releases are still using 2.3.x via travis/platformio, i'm not sure if it will automaticly switch to 2.4.0 at some point)

Eventually the v2.0 branch will be stable and we will make a official real release, which will be v2.0.0. That will be the first stable ESP release in a longggg time since martinus copied the a RXXX release and called it "mega". (because it required hardware that had 1Mb flash or more)

After v2.0.0 is released we will repeat all this by creating a new copy from mega and calling it the v2.1 branch. (And perhaps release bugfix releases for v2.0.0 called v2.0.1 or something)

It has been a bumpy road but we're getting there.

Thanks for the information

np do you know a nice and proper place on the wiki where this explanation should be? perhaps you can add it

psy0rz wrote: ↑10 Jan 2018, 18:30 np do you know a nice and proper place on the wiki where this explanation should be? perhaps you can add it

Yes that is something we need to add Consider it on my table!

grovkillen wrote: ↑10 Jan 2018, 20:00 Yes that is something we need to add Consider it on my table!

From what I can tell around here methinks you must have a very large table!

budman1758 wrote: ↑10 Jan 2018, 20:39

grovkillen wrote: ↑10 Jan 2018, 20:00 Yes that is something we need to add Consider it on my table!

From what I can tell around here methinks you must have a very large table!

Haha, I try to give some back to community that have me ESP Easy.

As @psy0rz mentioned. We have now let go of the devXX release scheme and started to do nightly builds of the v2.0 branch as well. If you want stable pre-releases you should go with the "v2.0-YYYYMMDD" releases, for cutting edge features you should go with the "mega-YYYYMMDD" releases.

https://github.com/letscontrolit/ESPEasy/releases

Hello @Grovkillen, @psy0rz,
Thanks for that clarification, I too was unsure what the different versions were about, and that makes it clear.

I looked at the page you linked to, and I think that the same clarification would be useful on that page. For example, use the words "stable" and "cutting edge" as description next to the V2.0 and Mega releases?

I second that. Many thanks for this explanation.

Hi, just flashed OTA with version ESPEasy_mega-20181003, see startup screen, but no Connect button to go to next screen?

(Apple Mac - Safari)

And pressing enter in the place where you enter your password, doesn't work?

Helaas geen reactie met enter na invoer password
Hoe dit te omzeilen?
(ESP_Easy_mega-20181008_normal_ESP8266_4096)

Note:
Old firmware: R120
new firmware: ESP_Easy_mega-20181008_normal_ESP8266_4096
Problem after update firmware old -> new: No button "connect" on connecting page.
Solution:
upgrade again with the same firmware (ESP_Easy_mega-20181008_normal_ESP8266_4096)
with the command: 192.168.4.1/update
Problem solved.

MZSch wrote: ↑10 Oct 2018, 22:45 Note:
Old firmware: R120
new firmware: ESP_Easy_mega-20181008_normal_ESP8266_4096
Problem after update firmware old -> new: No button "connect" on connecting page.
Solution:
upgrade again with the same firmware (ESP_Easy_mega-20181008_normal_ESP8266_4096)
with the command: 192.168.4.1/update
Problem solved.

Can you add an issue about this on GitHub?
Alvast bedankt

Done
https://github.com/letscontrolit/ESPEasy/issues/1890

Hi,
Are there .bin files available for v2.0.0. I can't seem to find them, the only ones I can find are mega .bin's.

Regards
Sailesh

Here is dev13
https://github.com/letscontrolit/ESPEas ... .0.0-dev13

From this URL you can deduce older versions, like
https://github.com/letscontrolit/ESPEas ... 2.0.0-dev7

dev-13 was last "stable" version for me.
I am running about 10 floor heating thermostats with this version.
WIth complex rules ( Rules1.txt full, Rules2.txt half full ), receiving events from Domoticz etc, without any problem from 11/2017.
Except random rebooting.
Actual "mega" versions do not handle sequences quick incoming events properly ( sometimes missed ).
A month ago i switch 6 of my nodes to V2.0 version and all works like at _dev13,
BUT MORE MORE MORE FASTER.

So I can recommend switching to this version.

I am not at home now to look at my ESPeasy version, but I think it is last V2.0 I found:

https://github.com/letscontrolit/ESPEas ... 0-20180322

Thank you both.. I give v2.0 a shot based on your recommendation.

Using the flasher you can list all released versions.