I observed that the definition of command names became mangled with commit 2bc5f682b0 due to vertical bar not being placed where it should. With no bar after `D_CMND_CPU_FREQUENCY`, the command name became concatenated with the next `D_CMND_SETSENSOR` with the "funny" effect that command name `CpuFrequencySetSensor` got matched with `&CmndSetSensor`
The reason for it not being matched with `&CmndCpuFrequency` is that there is a bar too many before the `Info` command name, as previous command name lines all finish with `"|"`. Hence an extra command table entry was created, meaning that the mismatch "only" affected command names `Info`, `TouchCal`, `TouchThres`, `CpuFrequency` and `SetSensor`.
Issue is only for ESP32, as both mishaps happened in a block conditional on `#ifdef ESP32`.
Arguably, it could make sense to have all the lines with command names start with `"|"` as a consistent way of formatting the lines without the special case of ending `"|"` to be omitted for the very last command name line, but I wanted to only make minimal changes
* Add V9240 driver
* Addendum to previous commit
* Add driver code similar to the prototype
* they are talking to each other
* Added implementation of calibration commands
* continued work of calibration
* Maybe it works.
* Post-merger control
* Change driver number 34 to 25
* Correction of other comments
* Removed duplicate code
* Adjusting the calibration procedure according to the behavior stated here. To the extent possible.
https://tasmota.github.io/docs/Power-Monitoring-Calibration/#calibration-procedure
* Removed added trailing whitespaces
* Fixing several small issues.
* Allow acl in mqtt
Acl in mqtt needs user name if 'use_identity_as_username' is not true. It also seems that login in mqtt don't accept an user with an empty password, then reenabled both
* Add new define for mosquitto
Keep compatibility with AWS_IOT
* Better approach to custom client certificate
Don't duplicate defined check. Let USE_MQTT_AWS_IOT automatically set USE_MQTT_CLIENT_CERT and use latter in all code
* with mosquitto user and password may be empty
When mosquitto 'use_identity_as_username' option is enabled password and user are not used
- CHange Display removed PWM control of backlight GPIO for universal display regression from v14.1.0
- Fix Display DisplayMode adds a display device while not configured
- Fix GUI intermittent exception on screen updates due to flash access