mirror of https://github.com/arendst/Tasmota.git
4dc210004a
Not all flag names were updated to match updates to Tasmota source in `support_features.ino`. I assume the changes to be uncontroversial, with the possible exception of:
While `USE_TUYA_DIMMER` arguably is a more descriptive name than `USE_TUYA_MCU` the former name is not found anywhere in Tasmota code, which has
```
#if defined(USE_LIGHT) && defined(USE_TUYA_MCU)
feature2 |= 0x00008000; // xdrv_16_tuyadimmer.ino
#endif
```
My assumption is that the actually used names "wins", to avoid user confusion, even if you could say that the name `USE_TUYA_MCU` is too broad for the actual feature. In principle, it would be more logical to create a new "real" `#define` name, but backwards compatibility and all that.... Makes sense?
I'm ok either way....
|
||
|---|---|---|
| .. | ||
| fw_HM10_cc2541 | ||
| fw_RfSensor_attiny85 | ||
| fw_ShellyDimmer_stm32 | ||
| fw_SonoffRfBridge_efm8bb1 | ||
| fw_SonoffZigbeeBridge_ezsp | ||
| fw_TasmotaClient_arduino | ||
| fw_TubeZigbee_efr32 | ||
| fw_Zigbee_cc2530 | ||
| logo | ||
| lv_gpio | ||
| mqtt-file | ||
| ota_server | ||
| templates | ||
| unishox | ||
| decode-config.md | ||
| decode-status.py | ||
| espupload.py | ||
| serial-plotter.py | ||