custom-components/ble_monitor 0.6.8

0.6.8 - whitelist option and Xiaomi Smart Repellent support

on GitHub

new whitelist option:

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 neighbouring 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:

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:

sensor:
  - platform: mitemp_bt
    encryptors:
      'A4:C1:38:2F:86:6C': '217C568CF5D22808DA20181502D84C1B'
      'A4:C1:38:D1:61:7D': 'C99D2313182473B38001086FEBF781BD'
    whitelist: True

Default value: False.

changes to implement support for sensors broadcasting switch state and consumable resource;

The entity class of the binary sensor and the entity name of the consumable sensor are assigned automatically depending on the type of specific device.

Due to the fact that this component has a periodic nature of the operation, the state of the binary sensor will arrive with some delay. For example, if your period option is one minute (by default this is the case), and the state of the sensor has changed by 30 seconds of the period, then the state of the binary sensor entity in HA will change only after the remaining 30 seconds have passed.

Xiaomi Mija Mosquito Repellent WX08ZM support #70;