ESP Easy development status

Announcements from the Staff

Moderators: rtenklooster, Voyager, BertB, Stuntteam

Message
Author
psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#51 Post by psy0rz » 21 Feb 2017, 11:57

Change requests should perhaps go on the issue tracker on github. (https://github.com/letscontrolit/ESPEasy/issues)

Support requests and discussion should stay on the forum.
Please support ESPEasy development via Patreon or buy us a coffee.

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#52 Post by psy0rz » 03 Mar 2017, 00:17

Ok i just finshed a lot of tutorials, explaining everything about platformio and github.

They are at the bottom of this page: http://www.letscontrolit.com/wiki/index ... evelopment
Please support ESPEasy development via Patreon or buy us a coffee.

krikk
Normal user
Posts: 118
Joined: 28 Feb 2017, 07:57
Location: Austria
Contact:

Re: ESP Easy development status

#53 Post by krikk » 03 Mar 2017, 08:14

great tutorials, would have saved me a few hours if they where published a few days earlyer :D

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#54 Post by BertB » 05 Mar 2017, 10:38

@psy0rz
Great tutorial, works out fine, until you write about Smart Code Linter. Perhaps I installed it without knowing what I was doing.
May be this has nothing to do with my current problem, which is that nothing happens (well, Atom seizes to respond) after:

Building the correct version

Press F7 and you will get an overview of possible versions you can build:

I am working on a 64 bit windows 7 pc and could use some help.

krikk
Normal user
Posts: 118
Joined: 28 Feb 2017, 07:57
Location: Austria
Contact:

Re: ESP Easy development status

#55 Post by krikk » 06 Mar 2017, 08:37

smart code linter does not work because we are useing .ino files, it's in the FAQ of platformio... really annoying

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#56 Post by BertB » 06 Mar 2017, 13:08

@krikk
Okay .. so I removed github and atom completley from my pc and walked through the setup procedures again.
With Linter disabled and Clang (is that safe?) for a later remind.

Still the same problem. When I press F7, i get a pop-up saying that the editor is not reponding ...
Atom.png
Atom.png (255.66 KiB) Viewed 47350 times

krikk
Normal user
Posts: 118
Joined: 28 Feb 2017, 07:57
Location: Austria
Contact:

Re: ESP Easy development status

#57 Post by krikk » 06 Mar 2017, 19:09

did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#58 Post by BertB » 06 Mar 2017, 19:43

krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
Yas, I did.
You have no problems here?

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#59 Post by BertB » 06 Mar 2017, 20:15

krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
I am a step further, I had to choose a board and now the editor starts but I do not get the options.
This is what I get
Atom2.png
Atom2.png (176.19 KiB) Viewed 47299 times

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#60 Post by BertB » 06 Mar 2017, 23:08

BertB wrote: 06 Mar 2017, 20:15
krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
I am a step further, I had to choose a board and now the editor starts but I do not get the options.
This is what I get
Atom2.png
Somehow I managed to get the choice to select the Wemos D1 mini, but now Atom says it cannot compile because there is nothing in the .../ESPEasy/src folder

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#61 Post by psy0rz » 07 Mar 2017, 14:15

BertB wrote: 06 Mar 2017, 23:08
BertB wrote: 06 Mar 2017, 20:15
krikk wrote: 06 Mar 2017, 19:09 did you also remove all user directories after uninstall, so that you really start on a fresh base.

http://docs.platformio.org/en/latest/id ... formio-ide <-- uninstall instructions...

if this does not help, sorry i am also new to platformio :)
I am a step further, I had to choose a board and now the editor starts but I do not get the options.
This is what I get
Atom2.png
Somehow I managed to get the choice to select the Wemos D1 mini, but now Atom says it cannot compile because there is nothing in the .../ESPEasy/src folder
Did you open the ESPEasy folder in Atom, or did you open the src folder directly? (you should open the ESPEasy folder)
Please support ESPEasy development via Patreon or buy us a coffee.

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#62 Post by BertB » 07 Mar 2017, 14:46

Hi. Thanks for the reponse. I am desperately trying to get things up and running, cause I have a lot of ideas, however this kind of programming techniques, I am not familiar with. So please forgive me for asking many stupid questions.

Before I first managed to get any reponse to the F7 keystroke, I had to choose a board with the initialize or update button.
My working folder is /Documents/ESPEasy. In it are:
.git
.pioenvs
lib (with only readme.txt)
MiniProExtender
src (with some files starting with a . (dot)
and a lot of 'normal' ESPEasy stuff.

Then, after selecting ESPEasy.ino and the proper board and pressing F7, I got:
[03/07/17 14:41:34] Processing d1_mini (platform: espressif8266, board: d1_mini, framework: arduino)

Verbose mode can be enabled via `-v, --verbose` option
Collected 23 compatible libraries
Looking for dependencies...
Project does not have dependencies
Error: Nothing to build. Please put your source code files to 'C:\Users\Bert\Documents\ESPEasy\src' folder

[ERROR] Took 1.50 seconds
Environment d1_mini [ERROR]
[ERROR] Took 1.50 seconds

[SUMMARY]
Environment nodemcuv2 [SKIP]
Environment esp12e [SKIP]
Environment nanoatmega328 [SKIP]

So, I moved the 'normal'ESPEasy files to the src folder.
Then, after pressing F7 again:

[03/07/17 14:44:44] Processing d1_mini (platform: espressif8266, board: d1_mini, framework: arduino)

Verbose mode can be enabled via `-v, --verbose` option
Converting ESPEasy.ino
Collected 23 compatible libraries
Looking for dependencies...
Library Dependency Graph

|-- <Servo(esp8266)> v1.0.2
|-- <Wire> v1.0
|-- <ESP8266WiFi> v1.0
|-- <ESP8266WebServer> v1.0
| |-- <ESP8266WiFi> v1.0
Compiling .pioenvs\d1_mini\src\ESPEasy.ino.o
Archiving .pioenvs\d1_mini\libFrameworkArduinoVariant.a
Compiling .pioenvs\d1_mini\FrameworkArduino\Esp.o
Compiling .pioenvs\d1_mini\FrameworkArduino\FS.o
C:/Users/Bert/Documents/ESPEasy/src/ESPEasy.ino:157:26: fatal error: PubSubClient.h: No such file or directory
#include <PubSubClient.h>
^
compilation terminated.
Compiling .pioenvs\d1_mini\FrameworkArduino\HardwareSerial.o
*** [.pioenvs\d1_mini\src\ESPEasy.ino.o] Error 1

[SUMMARY]
Environment nodemcuv2 [SKIP]
Environment esp12e [SKIP]
[ERROR] Took 3.48 seconds
Environment d1_mini [ERROR]
[ERROR] Took 3.48 seconds
Environment nanoatmega328 [SKIP]

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#63 Post by BertB » 07 Mar 2017, 14:53

After that, I copied al the downloaded library files to the lib folder.
After hitting F7 again, I got:

[03/07/17 14:50:16] Processing d1_mini (platform: espressif8266, board: d1_mini, framework: arduino)

Verbose mode can be enabled via `-v, --verbose` option
Converting ESPEasy.ino
Collected 44 compatible libraries
Looking for dependencies...
Library Dependency Graph

|-- <Wire> v1.0
|-- <IRremoteESP8266>
|-- <PubSubClient> v2.6
|-- <Json> v5.6.4
|-- <ESP8266WebServer> v1.0
| |-- <ESP8266wifi-master>
| |-- <ESP8266WiFi> v1.0
|-- <LiquidCrystal_I2C>
| |-- <Wire> v1.0
|-- <ESP8266WiFi> v1.0
|-- <ESP8266wifi-master>
|-- <Servo(esp8266)> v1.0.2
Compiling .pioenvs\d1_mini\src\ESPEasy.ino.o
Archiving .pioenvs\d1_mini\libFrameworkArduinoVariant.a
Compiling .pioenvs\d1_mini\FrameworkArduino\Esp.o
Compiling .pioenvs\d1_mini\FrameworkArduino\FS.o
Compiling .pioenvs\d1_mini\FrameworkArduino\HardwareSerial.o
In file included from C:/Users/Bert/Documents/ESPEasy/src/ESPEasy.ino:153:0:
lib\ESP8266wifi-master/ESP8266WiFi.h:23:26: fatal error: avr/pgmspace.h: No such file or directory
#include <avr/pgmspace.h>
^
compilation terminated.
*** [.pioenvs\d1_mini\src\ESPEasy.ino.o] Error 1

[SUMMARY]
Environment nodemcuv2 [SKIP]
Environment esp12e [SKIP]
Environment nanoatmega328 [SKIP]
[ERROR] Took 4.46 seconds
Environment d1_mini [ERROR]
[ERROR] Took 4.46 seconds

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#64 Post by BertB » 07 Mar 2017, 14:57

By the way,

I do not get your list after hitting F7, but this:
Atom3.png
Atom3.png (166.39 KiB) Viewed 48960 times

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#65 Post by psy0rz » 07 Mar 2017, 15:01

BertB wrote: 07 Mar 2017, 14:46 Before I first managed to get any reponse to the F7 keystroke, I had to choose a board with the initialize or update button.
Then something went wrong. You shouldn't need to initialize. (initializing creates or updates your platformio.ini, but we've already created a platformio.ini for you with all the nice options you should see in the F7 list)

Can you remove the ESPEasy directory completely, clone again with Github desktop, and then open it again with Atom and press F7.

If it hangs again when you pressed F7, wait a while (30 seconds or so) and then an error will pop up. Please create a screenshot of that.

Edwin
Please support ESPEasy development via Patreon or buy us a coffee.

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#66 Post by BertB » 07 Mar 2017, 19:47

I did as you suggested.
This is the result.
Atom4.png
Atom4.png (32.59 KiB) Viewed 48926 times

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#67 Post by psy0rz » 15 Mar 2017, 01:53

In the meanwhile i also fixed building in Arduino IDE again and updated the wiki.

Use at least v2.0.0-dev7 and the changes i made here: https://www.letscontrolit.com/wiki/inde ... are_Upload
Please support ESPEasy development via Patreon or buy us a coffee.

AndrewJ
Normal user
Posts: 229
Joined: 14 Feb 2017, 12:38

Re: ESP Easy development status

#68 Post by AndrewJ » 19 Mar 2017, 18:33

Hi, and thanks for all the good work! I really like ESPeasy and have it on several nodemcu modules. I'm now trying to install it on a Sonoff switch.
I'm running Windows 10 and most of my experience is with the Arduino IDE rather than platformio.

A couple of questions about the Arduino IDE tutorial, as it applies on windows 10 ...
- Is it a specific intention to use Arduino IDE v. 1.6.12? When I followed the link to the main software page, it shows 1.8.1 as the current version. I decided to go ahead with that one (I used the Windows installer option). It wanted to uninstall my previous version so I said yes to that.
- It then installed the IDE in c:\Program files (x86) in a folder named simply Arduino. I'm unsure if this is the folder to rename with P230 at the end and create the folder named Portable, or is it somewhere else?
Please could you clarify a bit? Thanks in advance.
Andrew.

Shardan
Normal user
Posts: 1156
Joined: 03 Sep 2016, 23:27
Location: Bielefeld / Germany

Re: ESP Easy development status

#69 Post by Shardan » 19 Mar 2017, 19:53

AndrewJ wrote: 19 Mar 2017, 18:33 Hi, and thanks for all the good work! I really like ESPeasy and have it on several nodemcu modules. I'm now trying to install it on a Sonoff switch.
I'm running Windows 10 and most of my experience is with the Arduino IDE rather than platformio.

A couple of questions about the Arduino IDE tutorial, as it applies on windows 10 ...
- Is it a specific intention to use Arduino IDE v. 1.6.12? When I followed the link to the main software page, it shows 1.8.1 as the current version. I decided to go ahead with that one (I used the Windows installer option). It wanted to uninstall my previous version so I said yes to that.
- It then installed the IDE in c:\Program files (x86) in a folder named simply Arduino. I'm unsure if this is the folder to rename with P230 at the end and create the folder named Portable, or is it somewhere else?
Please could you clarify a bit? Thanks in advance.
Andrew.
Well, i'm not an expert and running Win7 but i'll try to answer your questions as good as possible.
At first: If you do a installer based installation you might run into problems when compiling old ESP-Sources (R14x)
or possibly sketches for other platforms - the configurations conflict, even if you make a second "portable" installation.
I've removed all stadard installations and made two independend portable installations, it works.

If you use the win-installer, the Arduino IDE is registered with windows - do not rename the "Arduino" folder, as this will cross the registering.
A regular installation with installer is not portable, the HowTo was written with a portable installation in mind.
i suppose you don't need a "portable" folder with that.
Install the ESP8266 Boards as described in the HowTo.
Download the source zip if you didn't already.
Unpack it to a folder of your choice on your harddisk.
Cupy the libs fromt he source to the "c:\programs(x86)\arduino\libraries" folder.
Rename the "src" folder to "ESPEasy" (Watch capitals!)
Start the IDE and open the "ESPEasy.ino" file.
Scroll down in the source code and make a choice which plugin set should be installed:

Code: Select all

/build all the normal stable plugins
//#define PLUGIN_BUILD_NORMAL

//build all plugins that are in test stadium
#define PLUGIN_BUILD_TESTING

//build all plugins that still are being developed and are broken or incomplete
//#define PLUGIN_BUILD_DEV
I selected the "Testing" built by removing the "//". Just uncomment only one of the choices.
Select your board or ESP-Type with the IDE's board manager.
Set the SPIFFS size as described in the HowTo (1 MB for the NodeMCU with ESP12E)

Now you may start compilation.
Use the "Ctrl + Alt + S" (export compiled binary) to create a bin file.
The .bin file is created in the same folder the ESPEasy.ino is located.
Due to my experience flashing with the Arduino IDE results in failing boot of the ESP.
I've used the esptool from the source files successfully.

Anyways, this discussion should be moved to the ESPMega board of the forum as it is not staff related.

Hope that helps.

Regards
Shardan
Regards
Shardan

AndrewJ
Normal user
Posts: 229
Joined: 14 Feb 2017, 12:38

Re: ESP Easy development status

#70 Post by AndrewJ » 20 Mar 2017, 08:17

Thanks for the clear and comprehensive reply. Now I get it, I should have downloaded the zip file (not used the Windows Installer!).
Tried it the way you said and it's working, compiled and uploaded to my Sonoff Switch.
Thank you!
(and sorry for posting on the wrong board)

Andrew

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#71 Post by BertB » 26 Mar 2017, 15:22

psy0rz wrote: 15 Mar 2017, 01:53 In the meanwhile i also fixed building in Arduino IDE again and updated the wiki.

Use at least v2.0.0-dev7 and the changes i made here: https://www.letscontrolit.com/wiki/inde ... are_Upload
I have gone through the setup all over again and now I see the fault is maybe somewhere in my interaction with Github.
When I am at letscontrolit/ESPEasy, I see:
Github org.png
Github org.png (88.29 KiB) Viewed 49344 times
And after Fork:
Github Fork.png
Github Fork.png (69.88 KiB) Viewed 49344 times
I think the Forking is not actually been done.

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#72 Post by psy0rz » 26 Mar 2017, 16:59

the file structure looks like the naster branch, although github says mega-branch for some reason.

github should always fork all the branches i assume.
Please support ESPEasy development via Patreon or buy us a coffee.

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#73 Post by BertB » 26 Mar 2017, 20:58

Okay ... so I went kamikaze and deleted my repository.
After that, I forked ESPEasy again and now things start to work.

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#74 Post by BertB » 02 Apr 2017, 14:43

@psyOrz
I thougt I understood how to work with github, but it seems I am still lost.
I managed to make my own fork of the letscontrolit repository and I was successful to compile it using github desktop and Atom.
Now I see there has been some changes, but when I click the Fork button they are not copied to my repository.
Is that normal?

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#75 Post by BertB » 12 Apr 2017, 14:03

How can I update my forked repository with the changes made in the letscontrolit/ESPEasy repository?

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#76 Post by psy0rz » 12 Apr 2017, 23:41

BertB wrote: 12 Apr 2017, 14:03 How can I update my forked repository with the changes made in the letscontrolit/ESPEasy repository?

I'm not sure how to do it with git desktop. (but its possible)

I usually use the commandline and do something like git pull or git pull origin mega.

There is probably some help on github.com on how to do it with git desktop. If you find out how we should update the wiki.
Please support ESPEasy development via Patreon or buy us a coffee.

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#77 Post by BertB » 04 May 2017, 18:50


Martinus

Re: ESP Easy development status

#78 Post by Martinus » 30 May 2017, 21:38

After running R148 for months, i decided to just take a go with the latest github release and take it into production use. All unit's could be upgraded using OTA without a single glitch.
Did not have to dismount a single unit...

Yes of course, i had to reconfigure all unit's from scratch because the mega version uses a different config format, but it took less than 30 minutes to do so for all unit's.

Seem to run fine after two days:
V200_Upgrade.png
V200_Upgrade.png (56.42 KiB) Viewed 48289 times
Although i'm no longer responsible for lead development, i would suggest to all developers/contributors to 'pause' new features for a while and focus on round-up of the current edition to replace the old R120. What do you think?

User avatar
grovkillen
Core team member
Posts: 3621
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: ESP Easy development status

#79 Post by grovkillen » 30 May 2017, 22:27

+1 for that. Just fix the issues relating none working features. We need all the things working at R120 to still work for 2.0.0.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#80 Post by psy0rz » 31 May 2017, 01:11

I agree, we should focus on fixing bugs the coming month so we can move on and finally release a beta of v2.0. :)

Having all all the devs help with the awesome new features is like giving free candy to a kid. Its just too good not to take. ;)

jkdesign, krikk, can you put the new features on hold for a while, so we dont get merge conflicts on long standing pull requests? ill try to focus on bugfixing the coming weeks. (had a few busy last weeks so i didnt have enough time to make good progress)

Martinus, let us know how stable it runs on all your gadgets :)
Please support ESPEasy development via Patreon or buy us a coffee.

Shardan
Normal user
Posts: 1156
Joined: 03 Sep 2016, 23:27
Location: Bielefeld / Germany

Re: ESP Easy development status

#81 Post by Shardan » 31 May 2017, 08:16

Martinus wrote: 30 May 2017, 21:38 Although i'm no longer responsible for lead development, i would suggest to all developers/contributors to 'pause' new features for a while and focus on round-up of the current edition to replace the old R120. What do you think?
+1 for that

On long term it will be necessary to come to a development scheme similiar to the way the linux kernel is developed.

A very raw layout might be:
1. Collecting - gathering new features for the next release.
2. Freezing, coding and testing. The list of new features is closed, coding and testing.
3. Beta, release candidate...
4. Release of a new version.

At the moment steps 1...3 are done same time.
Following my experience that will not work for unlimited time without issues.

Regards
Shardan
Regards
Shardan

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#82 Post by psy0rz » 31 May 2017, 12:15

its more like we kept hanging too long at step 1. but im new here and it takes a few months to get "settled" in a new project an community, so to speak :)

now its time for step 2 indeed.
Please support ESPEasy development via Patreon or buy us a coffee.

themanfrommoon
Normal user
Posts: 48
Joined: 23 May 2017, 21:38
Location: Malente / Germany

Re: ESP Easy development status

#83 Post by themanfrommoon » 31 May 2017, 21:20

Did somebody fix the following reported bug?

https://www.letscontrolit.com/forum/vie ... f=6&t=3126

Thanks and best regards,
Chris

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: ESP Easy development status

#84 Post by LisaM » 01 Jun 2017, 00:08

Martinus wrote: 30 May 2017, 21:38 Although i'm no longer responsible for lead development, i would suggest to all developers/contributors to 'pause' new features for a while and focus on round-up of the current edition to replace the old R120. What do you think?
And break the development in two: core/non-core with each having it's own focus / development cycle. Focus of core part should be stability and not new features, while the non-core part (sensors) can focus on new features relying on the core for stability...

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: ESP Easy development status

#85 Post by BertB » 05 Jun 2017, 11:59

+1 here too.
I am running the latest build (-dev10) on two devices and -dev8 on 8 others for a month now. Works like a charm.

Martinus

Re: ESP Easy development status

#86 Post by Martinus » 10 Jun 2017, 16:20

I think that the only right way is to split the project between stable and unstable. The stable versions will only get bugfixes (and maybe new features that have really been proven solid)
They could also be labeled Production and Experimental.

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#87 Post by psy0rz » 12 Jun 2017, 14:49

Martinus,

The common way to do this is with branches: As soon as we have a stable 2.0 release we should create a 2.0-branch. This will be the production branch in which we only commit the bugfixes, and create versions 2.0.1, 2.0.2 etc.

Development can then continue in the "development" branch, until we decide its time for a 2.1.0 release. (which at that point also will become a bugfix branch, and perhaps we can then make 2.0.x obsolete)

This will make porting bugfixes between the development and production versions much easier, because we can let git do most of the work.

Currently our development branch is "mega", but perhaps its better to switch this back to "master" at some point, since this is also more common.

Sounds good?
Please support ESPEasy development via Patreon or buy us a coffee.

Martinus

Re: ESP Easy development status

#88 Post by Martinus » 17 Jun 2017, 17:01

psy0rz wrote: 12 Jun 2017, 14:49 Martinus,

The common way to do this is with branches: As soon as we have a stable 2.0 release we should create a 2.0-branch. This will be the production branch in which we only commit the bugfixes, and create versions 2.0.1, 2.0.2 etc.

Development can then continue in the "development" branch, until we decide its time for a 2.1.0 release. (which at that point also will become a bugfix branch, and perhaps we can then make 2.0.x obsolete)

This will make porting bugfixes between the development and production versions much easier, because we can let git do most of the work.

Currently our development branch is "mega", but perhaps its better to switch this back to "master" at some point, since this is also more common.

Sounds good?
Sounds good. I'm cleaning up the current issue list, moved some stuff from bug to enhancement and added the 2.1.0 milestone.
It's time to focus on bugs with the 2.0.0. milestone and get a beta version out...
(if we leave more room for enhancement in 2.0.0. we just never get there anyway...)

So we now have to decide on untagged issues if we can tackle those in 2.0.0. or the 2.1.0 milestone.

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: ESP Easy development status

#89 Post by psy0rz » 19 Jun 2017, 21:59

Yeah i saw you've been busy. Very nice. :D

So far, if i tagged it with 2.0.0 it meant i really wanted it to be fixed before that version can be released. These are probably only bugs that are fixable without adding a lot of new code.

Stuff that is not tagged with a mile stone is "to be decided"/"dont know"/"didnt read yet". We probably should scan all the issues to make sure we tagged everything that needs to be tagged for 2.0.0.

Maybe we should make a habbit of tagging ALL issues with a milestone? Perhaps we should create a special "other" milstone for stuff we dont know what to do with, or stuff that doesnt belong to a milestone. (like wiki documentation in some cases)
Please support ESPEasy development via Patreon or buy us a coffee.

User avatar
grovkillen
Core team member
Posts: 3621
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: ESP Easy development status

#90 Post by grovkillen » 06 Aug 2017, 11:24

I wish we could have status of how many user there's out there but one indication is the number of stars on github. We have reached 500+ now over the weekend and if I remember correctly we have risen from 400 stars in just about a month. Great! :)

https://github.com/letscontrolit/ESPEasy/stargazers
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: ESP Easy development status

#91 Post by LisaM » 06 Aug 2017, 11:51

grovkillen wrote: 06 Aug 2017, 11:24 I wish we could have status of how many user there's out there but one indication is the number of stars on github. We have reached 500+ now over the weekend and if I remember correctly we have risen from 400 stars in just about a month. Great! :)

https://github.com/letscontrolit/ESPEasy/stargazers
I'm not surprised, i have looked long and hard to find anything simular to ESPEasy (8266 + wifi) and so far i haven't found it.It's like a HA Server for IOT devices and in that sense it's unique AND the first...

User avatar
grovkillen
Core team member
Posts: 3621
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: ESP Easy development status

#92 Post by grovkillen » 06 Aug 2017, 12:02

Yes, your point is probably a good reason of the popularity. Thanks! 👍😎
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

User avatar
toffel969
Normal user
Posts: 469
Joined: 03 Jan 2017, 10:58
Location: Germany

Re: ESP Easy development status

#93 Post by toffel969 » 09 Aug 2017, 18:17

LisaM wrote: 06 Aug 2017, 11:51
grovkillen wrote: 06 Aug 2017, 11:24 I wish we could have status of how many user there's out there but one indication is the number of stars on github. We have reached 500+ now over the weekend and if I remember correctly we have risen from 400 stars in just about a month. Great! :)

https://github.com/letscontrolit/ESPEasy/stargazers
I'm not surprised, i have looked long and hard to find anything simular to ESPEasy (8266 + wifi) and so far i haven't found it.It's like a HA Server for IOT devices and in that sense it's unique AND the first...
+1 to that. Before esp easy my homes automation plans always remained dreams. With esp easy it's a matter of few hours to build, implement and debug a node. Awesome!
Domoticz on Raspi 2 -- 14 ESP units (hacked Sonoff,NodeMCUs, Wemos, self-built units) running with RC140- Mega 2.0.0 dev8

randytsuch
Normal user
Posts: 33
Joined: 05 Jun 2017, 05:32

Re: ESP Easy development status

#94 Post by randytsuch » 09 Aug 2017, 21:21

toffel969 wrote: 09 Aug 2017, 18:17
LisaM wrote: 06 Aug 2017, 11:51
grovkillen wrote: 06 Aug 2017, 11:24 I wish we could have status of how many user there's out there but one indication is the number of stars on github. We have reached 500+ now over the weekend and if I remember correctly we have risen from 400 stars in just about a month. Great! :)

https://github.com/letscontrolit/ESPEasy/stargazers
I'm not surprised, i have looked long and hard to find anything simular to ESPEasy (8266 + wifi) and so far i haven't found it.It's like a HA Server for IOT devices and in that sense it's unique AND the first...
+1 to that. Before esp easy my homes automation plans always remained dreams. With esp easy it's a matter of few hours to build, implement and debug a node. Awesome!
+2. Although I'm not as fast, takes me more than a few hours lol
But seriously I've been able to do so much with not much money because of ESP Easy, where I would have spend hundreds of dollars for commercial solutions.

Martinus

Re: ESP Easy development status

#95 Post by Martinus » 10 Aug 2017, 10:32

Has anyone noticed that today it's been a full year after we published R120 stable.

Although this could ask for a small celebration, it also indicates that we have not been able to release the next stable within a reasonable time frame...

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: ESP Easy development status

#96 Post by LisaM » 10 Aug 2017, 11:00

Martinus wrote: 10 Aug 2017, 10:32 Has anyone noticed that today it's been a full year after we published R120 stable.

Although this could ask for a small celebration, it also indicates that we have not been able to release the next stable within a reasonable time frame...

I'm not worried about R120, rather then a new release for V1 i would want to have a release of V2 (mega)...
I've dev11 running in 7 places in my home, some running on Sonoff (basic, pow) and some on home made ESP boards. I also am readying V2 for two ElectroDragons.

I propose to promote the mega branch to master and release the next dev as ESPEasy R200 stable.

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: ESP Easy development status

#97 Post by LisaM » 11 Aug 2017, 13:16

With the ongoing development of ESP8266 MicroPython it's now in reach to rewrite ESPEasy in python. The ESP8266 hardware(with standard 8MB of flash memory on an ESP-01 module in Ali as latest record) is capable of supporting it although the minimum of 4MB should be required.
Performance test should be applied to verify if the performance is acceptable.

With using MicroPython, it would no longer be required to flash the ESP8266 other then to install MicroPython itself.ESPEasy python code should be in mainly two (fat) files: boot.py and main.py since micropython is using a fat filesystem after it becomes active. ESPEasy updates whould then mean to copy over some files and flash the firmware again. OTA, Serial and other update methods (with size limits) would no longer be required.
The rules section could become entirely python, giving a lot of additional options...
All pins except number 16 can be configured to trigger a hard interrupt if their input changes. You can set code (a callback function) to be executed on the trigger.
This will make ESPEasy a LOT easier, no need to run the loop() several times per second as we are currently doing...
Uart, i2c, spi, DHT and NeoPixels are all standard present in micropython.

Shardan
Normal user
Posts: 1156
Joined: 03 Sep 2016, 23:27
Location: Bielefeld / Germany

Re: ESP Easy development status

#98 Post by Shardan » 11 Aug 2017, 13:24

Be carefull with those ESP-01 with 8Mbyte shown at AliExpress.
It has shown that many of our chinese friends can't (or acidentally forgot to) differ between MBit and MByte
Every "8MByte" modul i tested showed up to be a 8MBit one....... in other words as a standard 1Mbyte type.

Give it a try.
Regards
Shardan

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: ESP Easy development status

#99 Post by LisaM » 11 Aug 2017, 15:21

Shardan wrote: 11 Aug 2017, 13:24 Be carefull with those ESP-01 with 8Mbyte shown at AliExpress.
It has shown that many of our chinese friends can't (or acidentally forgot to) differ between MBit and MByte
Every "8MByte" modul i tested showed up to be a 8MBit one....... in other words as a standard 1Mbyte type.

Give it a try.
Thx for the warning.
I don't need one at this point, the esp's with 4MB are good enough for me. If i need a lot of memory then i'll buy a wemos with 16MB.
Other option is to buy a pyboard for $15, it has a shitload of io-ports (30!), sd card and other ports and a LOT of flash/ram memory...
With micropython, ESPEasy is no longer bound to the ESP8266. ;)

Martinus

Re: ESP Easy development status

#100 Post by Martinus » 11 Aug 2017, 17:55

LisaM wrote: 11 Aug 2017, 13:16
All pins except number 16 can be configured to trigger a hard interrupt if their input changes. You can set code (a callback function) to be executed on the trigger.
This will make ESPEasy a LOT easier, no need to run the loop() several times per second as we are currently doing...
This is already in use for ESP Easy as well. Just look at the pulse counter plugin where interrupts are hooked up to callback functions. The main loop handles everything that is not interrupt based. But it remains a single threaded process so using something like RTOS would be better for this kind of projects.

But even when everything was irq based, beware that the ESP module can't access flash during irq handler and therefore all irq routines need to be stored in it's 32k instruction cache (IRAM). This is one of the major issues on the ESP8266 as well as it's limited 80k RAM that keeps us from building really powerful projects. Having 16MB flash is nice but this still doesn't mean that you can create huge projects for the ESP8266. Bottlenecks are RAM and IRAM and these can't be extended...

I think the LUA project has also struggled a lot with RAM issues... And so will likely any large interpreted environment suffer from the same RAM/IRAM limitations. Remember that the ESP8266 was actually never build with this in mind. Just a serial-wifi bridge...

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests