Page 1 of 1
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 28 Jul 2018, 11:38
by Tommmii
I have no need for I2C (for now
)
I just had a look at a recent nightly build, and it looks as if the "Switch input - Switch" and the "Analog input - internal" are both not included?
Does that seem right, or am I having a blonde moment ?
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 29 Jul 2018, 16:44
by TD-er
Not sure about the analog input.
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 29 Jul 2018, 17:18
by Tommmii
and the Switch input ?
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 29 Jul 2018, 17:56
by TD-er
Tommmii wrote: ↑29 Jul 2018, 17:18
and the Switch input ?
The switch input is present.
Currently the ESP32 builds have:
- OLED Framed
- INA219
- BMx280
- Dummy Device
- MQTT Import
- Pulse counter
- System Info
- Switch input.
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 07 Aug 2018, 09:56
by Tommmii
Is there a way to see in github which plugins are supported ?
Or can this only be seen after flashing the build into a device ?
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 07 Aug 2018, 22:17
by TD-er
Tommmii wrote: ↑07 Aug 2018, 09:56
Is there a way to see in github which plugins are supported ?
Or can this only be seen after flashing the build into a device ?
What is used where is defined in here:
https://github.com/letscontrolit/ESPEas ... gin_sets.h
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 08 Aug 2018, 12:51
by Tommmii
Perfect, cheers for this!
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 19 Oct 2019, 20:34
by JohnW
What is the difference between these builds:
custom_ESP8266_4M1M.bin
test_core_260_sdk222_alpha_ESP8266_4M1M.bin (test plugins + new SDK?)
test_ESP8266_4M_VCC.bin (includes test plugins)
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 19 Oct 2019, 21:55
by TD-er
JohnW wrote: ↑19 Oct 2019, 20:34
What is the difference between there builds:
custom_ESP8266_4M1M.bin
test_core_260_sdk222_alpha_ESP8266_4M1M.bin (test plugins + new SDK?)
test_ESP8266_4M_VCC.bin (includes test plugins)
See the README.txt also included in the ZIP you can download:
https://github.com/letscontrolit/ESPEasy/tree/mega/dist
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 20 Oct 2019, 16:05
by JohnW
TD-er wrote: ↑19 Oct 2019, 21:55
JohnW wrote: ↑19 Oct 2019, 20:34
What is the difference between there builds:
custom_ESP8266_4M1M.bin
test_core_260_sdk222_alpha_ESP8266_4M1M.bin (test plugins + new SDK?)
test_ESP8266_4M_VCC.bin (includes test plugins)
See the README.txt also included in the ZIP you can download:
https://github.com/letscontrolit/ESPEasy/tree/mega/dist
Unfortunately, I can't find info about "custom":
- normal_IR => "Normal" + IR receiver/transmitter plugins and library
- hard_xxxxx => Special builds for some off-the-shelf hardware.
- minimal_ESP82xx_1M_OTA => Minimum number of plugins and a limited set of controllers included to be able to perform a 2-step OTA on 1 MB flash nodes.
- normal_core_241 => "Normal" using core 2.4.1, since 2.4.2 has issues with PWM
- xxx_core_260_sdk2_alpha -> core 2.6.0 alpha version (under development) using SDK 2.2.1
- xxx_core_260_sdk222_alpha -> core 2.6.0 alpha version (under development) using SDK 2.2.2
- xxx_core_260_sdk3_alpha -> core 2.6.0 alpha version (under development) using SDK 3.0.0-dev (under development too)
Re: ESP Easy development "mega-201YMMDD" clearifications
Posted: 20 Oct 2019, 19:32
by TD-er
The custom one is using the Python script pre_extra_script.py
As you can see in that script, it is using a pre-defined set of plugins and controllers.
It is also used for people building their own using the (experimental) Vagrant build.