ESPEasy32 or uPYEasy?

Message

tim · #1 Post by **tim** » 06 Mar 2018, 12:12

Started a new topic on my second question. I have a new Lolin ESP32 board. What can you guys advice for firmware. The ESPEasy32 or the upyEasy?

LisaM · #2 Post by **LisaM** » 06 Mar 2018, 18:12

What are you going to do with it? Purpose defines solution...

tim · #3 Post by **tim** » 08 Mar 2018, 14:52

I'm thinking of outdoor LED system with at least 4 zones to control. This could be 4 relais or PWM, 4 input buttons and a LUX sensor, maybe temp and hum sensor as well. I think the ESP32 is nice because of the many GPIO on that board. The board is ready for the future i believe. But now the firmware?

budman1758 · #4 Post by **budman1758** » 08 Mar 2018, 21:19

Both of the firmwares are in the experimental or beta stage. As far as features and ease of installing I would go with ESPEasy32 because its the same code basically as ESPEasy for the 8266 so most stuff might "just work" now. I have one running right now and have a dallas temp sensor and 2 OLED displays attached to it and its working well except for one small bug in the Framed OLED.
https://github.com/letscontrolit/ESPEasy/issues/1029

Having said that I know that uPYEasy will probably eventually have more feature support. I can be difficult to get running as of now tho.

Food for thought.

tim · #5 Post by **tim** » 09 Mar 2018, 10:14

I see that uPyEasy only has a few plugins and BH1750 LUX sensor is not listed. The ESPEasy32 looks to have more plugins, but the wiki says that the BH1750 does not work there also.

budman1758 · #6 Post by **budman1758** » 09 Mar 2018, 18:03

tim wrote: ↑09 Mar 2018, 10:14 I see that uPyEasy only has a few plugins and BH1750 LUX sensor is not listed. The ESPEasy32 looks to have more plugins, but the wiki says that the BH1750 does not work there also.

The plugins that are in the ESPEasy32 are there because it uses the exact same source code as ESPEasy does. Chances are most will "just work" All you can do at this point is experiment. I was surprised when the 2 OLED's I hooked up both worked. I want to try both firmwares but have yet to get uPYEasy to work. I'm a Windows guy and getting the flash software working has been a bit of a hassle. Still haven't fixed it.

Martinus · #7 Post by **Martinus** » 12 Mar 2018, 20:52

Difficult to give a solid advise on this, other then "better sit and wait" for things to settle.

In the long run, uPyEasy may be the better option, because it's based on microPython. Just a few personal observations on the underlying core

Arduino ESP32 core
================
- Looks like a smaller dev team than uPython
- No stable version and it may take a while before we get one
- Webserver will be build as ESP8266/ESP32 separate development, but i haven't found it yet
- lots of Arduino libraries are available, but like 100% avr compatible, 75% ESP8266 compatible, 25% (?) ESP32 compatible. May need a lot of work/time
- Runs in a single task thread on RTOS. (although you can use the power of RTOS, ESP Easy does not use it)
- Current plugin support may be better from the start, but i haven't checked any of them besides a few core plugins.
- Arduino 'language' is very popular and will likely stick for a long time.

MicroPython core
===============
- Seems already in a mature state
- larger dev team, more hardware platforms
- better support for sensors and other stuff
- Guess it's multi-threaded by design
- Python is very popular, guess it's also true for uPython.

Besides the core, uPyEasy has the advantage of being build from ground-up (take the good ideas from ESPEasy but a fresh code rebuild). ESPEasy has it's origin on Atmel Atmega328 platform and was designed with limitations from that era and developed in classic C with lots of tweaks to minimize to code size. The good news is that many devs have restructured the original ESPEasy code into a much better piece of work. And there's more to come.

Let's just see where we all are by the end of 2018.

@Tim: If you need more basic GPIO and a proven solution, you may be better off using ESP8266 and an MCP23017

sm0k0 · #8 Post by **sm0k0** » 12 Mar 2018, 21:17

Hi there,
4PWM + 4 Switches and 1 LDR i would go for the ESP8266 for the moment as Martinus already wrote, even without GPIO multiplexer a reliable solution until ESPEasy ESP32 support is ready2go.

regards
sm0k0

tim · #9 Post by **tim** » 26 Apr 2018, 16:01

Looks like not a lot of development on uPyEasy, so i will stick with ESPEasy.
I need the sernet plugin for RFLink and it's not there in uPyEasy

ESPEasy32 or uPYEasy?

ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Re: ESPEasy32 or uPYEasy?

Who is online