Different versions of MQTT Plugin in same binary version

[Rampler]

Hi together,
i am a little bit confused...
MQTT Plugin differs in:
ESP_Easy_mega_20230513_collection_F_ESP8266_4M1M.bin
and
ESP_Easy_mega_20230513_normal_ESP8266_4M1M.bin.

Is this intented ?
Collection F:

SZ.png (31.12 KiB) Viewed 2125 times

Normal:

HMUART3.png (31.21 KiB) Viewed 2125 times

regards Klaus

[Ath]

The Collection builds on ESP8266 use the LIMIT_BUILD_SIZE compile-time flag, to reduce the binary size so we can fit in more plugins, at the cost of some features. As these features in the MQTT Import plugin take quite some space, we had to decide to leave them out for the LIMIT_BUILD_SIZE builds (also in Minimal and recently Climate for ESP8266, though I'm not sure if that includes the MQTT Import plugin at all).

There are several ways around this:
- Create a Custom build, as documented here
- Use an ESP32 device
--- either with 4 MB flash then pick the same Collection build you are currently using
--- or with 16 MB Flash, then install the MAX build, that includes all available plugins and features

[Rampler]

Thanks for clarifing this ..
New for me was, that there are two different versions of MQTT Plugins depending from which collection i use.
I wouldn't have been suprised if the MQTT plugin missed at all.

regards Klaus

[TD-er]

It is not like there are 2 versions.
But some features have been wrapped in flags like this:
#ifndef LIMIT_BUILD_SIZE
...
#endif

These can then be set at compile time and thus are simply left out in order to reduce the build size.