Add docs about reporting and optimistic mode (Koenkk#2519)

* Add reporting docs

* Add settings.md with optimistic

* Delete docs/guide/usage/reporting.md

* update (#1)

* Update mqtt_topics_and_messages.md

* Update devices-groups.md

* Delete docs/guide/usage/settings.md

* Update devices-groups.md

* Update mqtt_topics_and_messages.md

---------

Co-authored-by: Koen Kanters <[email protected]>

Author: trapacska

docs/guide/configuration/devices-groups.md

@@ -111,8 +111,11 @@ Allows preventing certain attributes from ending up in the cache.
 This prevents attributes from being published when the value did not change.
 
 **`optimistic`**  
-Publish optimistic state after set, e.g. when a brightness change command succeeds Zigbee2MQTT assumes
-  the brightness of the device changed and will publish this (default `true`).
+The optimistic mode is a feature that influences how the state of a device is handled in the absence of updates. When optimistic mode is enabled for a device and the last sent command was successful, it updates the device state accordingly, even before receiving confirmation from the device itself (default `true`).
+
+Enabled: If you send a command to turn on a light and the command was succesful, for example, Zigbee2MQTT will immediately update its internal state to reflect that the light is on. If the command fails, the state is not updated.
+
+Disabled: Zigbee2MQTT will only update its internal state after the device reports the new state, regardless wether the command was succesful or not.
 
 **`filtered_optimistic`**  
 Same as the `filtered_attributes` option but only applies to the optimistic published

docs/guide/usage/mqtt_topics_and_messages.md

@@ -384,7 +384,28 @@ See [Binding](./binding.md).
 
 #### zigbee2mqtt/bridge/request/device/configure_reporting
 
-Allows to send a Zigbee configure reporting command to a device. Refer to the Configure Reporting Command in the [ZigBee Cluster Library](https://github.com/Koenkk/zigbee-herdsman/blob/master/docs/07-5123-08-Zigbee-Cluster-Library.pdf) for more information. Example payload is `{"id":"my_bulb","cluster":"genLevelCtrl","attribute":"currentLevel","minimum_report_interval":5,"maximum_report_interval":10,"reportable_change":10}`. In this case the response would be `{"data":{"id":"my_bulb","cluster":"genLevelCtrl","attribute":"currentLevel","minimum_report_interval":5,"maximum_report_interval":"10","reportable_change":10},"status":"ok"}`.
+Allows to send a Zigbee configure reporting command to a device. Zigbee devices often have attributes that can report changes in their state, such as temperature, humidity, battery level, etc. Attribute reporting allows these devices to automatically send updates when there is a change in the values of these attributes.
+One example is when you change brightness of a bulb with its remote instead of Zigbee2MQTT, the state becomes out of sync.
+By setting up reporting for the bulb it will send notifications to Zigbee2MQTT about the brightness change and can update state in Zigbee2MQTT.
+
+It is a good practice to keep a balance between staying updated with relevant information and conserving energy, especially in the case of battery-powered devices.
+
+Refer to the Configure Reporting Command in the [ZigBee Cluster Library](https://github.com/Koenkk/zigbee-herdsman/blob/master/docs/07-5123-08-Zigbee-Cluster-Library.pdf) for more information. Example payload is `{"id":"my_bulb","cluster":"genLevelCtrl","attribute":"currentLevel","minimum_report_interval":5,"maximum_report_interval":10,"reportable_change":10}`. In this case the response would be `{"data":{"id":"my_bulb","cluster":"genLevelCtrl","attribute":"currentLevel","minimum_report_interval":5,"maximum_report_interval":"10","reportable_change":10},"status":"ok"}`.
+
+Parameters
+
+**Minimum reporting interval** (minimum_report_interval)
+In other words: how long after the attribute changes on the device should it send an update.
+A value of 0 means: send an update as soon as the attribute (e.g.: temperature) changes.
+
+**Maximum reporting interval** (maximum_report_interval)
+In other words: how frequently shall the device send a report if there is no change in the attribute constantly. 
+A value of 60 means: if the bulb is off for 30 minutes, it still sends 30 updates (every 60 seconds) even if there was no any attribute changes(e.g.: it was not turned on or off).
+
+**Minimum reporting change** (reportable_change)
+The Minimum Reporting Change is like telling your device to speak up only when something significant happens. 
+If you set a minimum reporting change of 1 degree for a temperature sensor, it means the sensor won't bother you with updates unless the temperature changes by at least 1 degree.
+It's a way to filter out minor fluctuations and focus on important changes in the environment.
 
 To disable reporting set the `maximum_report_interval` to `65535`.