* 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
- DALI command `DaliGear` to set max found gear to speed up scan response
- DALI command `DaliGroup` to add gear to groups
- DALI command `DaliTarget` to set light control broadcast, group number or gear number
- DALI renamed commands `DaliCommission` to `DaliScan` and `DaliWeb` to `DaliLight`
- DALI set Tasmota light control as default
* New LWT on deepsleep
To allow better integration into HA LWT topic will report details of sleep status:
16:54:04.388 MQT: hm/tele/ESP_3284D1/LWT =
{"Sleep":{"Time":"2023-07-17T16:55:03","Sleep":1689612844,"Wakeup":1689612903}}
* Revert LWT back to non JSON
Send DeelSleep on LWT
Send Deepsleep parameters on topic DeepSleep
* Setting default for batteryLevel
* Enable BatteryPercentSet
Changing the battery level e.g. by rule
* Added Battery % to status message
* added battery_level_percent
* Added battery % support in STATE message
* Enable setting battery level
101 is reserved for power-plug. No battery Level reported
* Setting default for battery Level
101 is reserved for power plug
0..100 normal battery values
* Revert back LWT to Offline
Removed "DeepSleep" LWT status until further decision is made. Current implementation is technical sufficient for HA to detect a battery powered device
* Added discovery message after deepsleep change
* Added discovery for battery and deepsleep
Changing default for DisplayMode from 1 to 0. Users are getting confused by the display doing something they did not ask for (and not being aware of DisplayMode). This got worse with LVGL/HASPmota displays becoming common, with users having much less reason to dive into the old DisplayXxxxx commands. And it may even be hard to see that it is even a display of time/date causing the display to flicker.
Changing default for DisplayDimmer from 10% to 50%. The low brightness of 10% is not always easy to see, especially in daylight. 50% is generally better, while not going "full blast" with 100%.
