README.md and info.md updated with whitelist option
@@ -197,6 +197,31 @@ sensor:
(boolean)(Optional) This option is needed primarily for those who want to request an implementation of device support that is not in the list of [supported sensors](#supported-sensors). If you set this parameter to `True`, then the component will log all messages from unknown Xiaomi ecosystem devices to the Home Assitant log. **Attention!** Enabling this option can lead to huge output to the Home Assistant log, do not enable it if you do not need it! Details in the [FAQ](https://github.com/custom-components/sensor.mitemp_bt/blob/master/faq.md#my-sensor-from-the-xiaomi-ecosystem-is-not-in-the-list-of-supported-ones-how-to-request-implementation). Default value: False
+#### whitelist
+
+By default, the component creates entities for all detected supported sensors. However, situations may arise when you need to limit the list of sensors. For example, when you receive data from neighboring sensors, or data from part of your sensors are received using other equipment, and you would not want to see entities you do not need. To resolve this issue, simply list the MAC-addresses of the sensors you need in the `whitelist` option:
+
+```yaml
+sensor:
+ - platform: mitemp_bt
+ whitelist:
+ - '58:C1:38:2F:86:6C'
+ - 'C4:FA:64:D1:61:7D'
+```
+
+data from sensors with other addresses will be ignored.
+In addition, all addresses listed in the `encryptors` option will be automatically whitelisted.
+If you have no sensors other than those listed in `encryptors`, then just set `whitelist` to `True`:
+
+```yaml
+sensor:
+ - platform: mitemp_bt
+ encryptors:
+ 'A4:C1:38:2F:86:6C': '217C568CF5D22808DA20181502D84C1B'
+ 'A4:C1:38:D1:61:7D': 'C99D2313182473B38001086FEBF781BD'
+ whitelist: True
+```
+
## FREQUENTLY ASKED QUESTIONS
Still having questions or issues? Please first have a look on our [Frequently Asked Questions (FAQ) page](faq.md) to see if your question is already answered. There are some useful tips also.
