Version differences?

[oisisi]

I'd like to update a few boards and seem to be unable to find documentation on something that should be pretty obvious. I guess I am not searching properly.

Where are the more subtle differences between the binary builds documented? Flash size and hardware type are simple, but I need to find out if I need to roll my own ESP8266 binary to:

- receive IR
- use a BMX28x temperature, pressure, humidity sensor
- use a TSL2561 light sensor
- use a Neopixel-style RGB LED

In the past there was such a bin but now I can't figure out if the compiled ones fit. I know the IR part is mostly kept separate due to its size. But I can't find if the IRext files include the other plugins.

Would the current ESP_Easy_mega_20200721_minimal_IRext_ESP8266_4M2M.bin fit for my plugin needs and my Wemos D1 mini?

[TD-er]

This list is not entirely up-to date I'm afraid, but it is some start: https://espeasy.readthedocs.io/en/lates ... al-plugins

The file where it is all defined can be found here: https://github.com/letscontrolit/ESPEas ... gin_sets.h
This section is about the minimal IR ext: https://github.com/letscontrolit/ESPEas ... #L175-L189

[oisisi]

Thanks for the 'pointers'. I assumed the truth is in the code but I hoped for a more readable approach.

I gather that the sensors that I need to be supported are part of the Normal package, so "Normal with IR" should fit the bill. If I understand it correctly, "IRext" would also work but it would also include support for air conditioner IR control which makes the binary bigger. Then there is "IRext_no_rx" and this would not work since it only includes an IR emitter plugin.

The released binaries do not include 'Normal with IR" or "Normal with IRext" versions so my conclusion is to roll my own.

[TD-er]

You can also have a look at the "vagrant" build option.
That may make building a bit easier perhaps?
See the discussion here: https://github.com/letscontrolit/ESPEasy/issues/2594
And this part of the repository: https://github.com/letscontrolit/ESPEas ... ls/vagrant

[oisisi]

Interesting. My PlatformIO environment used to work properly in the past so that is the lesser challenge. I think I still need to put together the proper env stanza to have a build with my needed plugins.

[TD-er]

Just have a look at the pre_custom...py files here: https://github.com/letscontrolit/ESPEas ... /tools/pio
Just note the needed plugins and controllers and build a 'custom' env in PlatformIO.

[oisisi]

That's very helpful. As powerful PlatformIO is, it seems like a lot of ini files to edit. Thanks!

[oisisi]

Just note the needed plugins and controllers and build a 'custom' env in PlatformIO.

Just to confirm: I edit the respective "pre_custom" Python file, set "default_envs" to "custom_ESP8266_4M1M" in platformio.ini and let the build process run? (Building worked flawlessly, I just want to make sure my desired plugins were picked up.)

[TD-er]

You can force the default build envs, or just call the build process to build a specific env.
The result is the same though, only one is a bit less editing work if you pull new version of the code.