0.7.2 - Apply sensor names directly in configuration.yaml

Release notes

• Added option to configure sensor names in configuration.yaml, see the sensor_names option. Note that when you use or change this option, it will create new entities. This means that you will have to update your lovelace cards, automations and/or scripts that use the entity_id. Note that you can still rename sensors afterwards from the UI. After the change, you can manually delete the old entities from the Developer Tools.
• Added the mac address to the attributes of the sensors
• New sensors will be named according to a new convention: mi_sensortype_mac (e.g. sensor.mi_temperature_A4C1382F86C)(default) or mi_sensortype_sensor_name (e.g. sensor.mi_temperature_livingroom) (with sensor_names option). Your current sensors with the short nameing (e.g. mi_t_A4C1382F86C) or manually modified names won't be renamed, unless you use the sensor_names option.

0.7.2 - beta Add option for sensor names in config

• Added option to configure sensor names in configuration.yaml, see the sensor_names option. Note that when you use or change this option, it will create new entities. This means that you will have to update your lovelace cards, automations and/or scripts that use the entity_id. Note that you can still rename sensors afterwards from the UI. After the change, you can manually delete the old entities from the Developer Tools.
• Added the mac address to the attributes of the sensors
• New sensors will be named according to a new convention: mi_sensortype_mac (e.g. sensor.mi_temperature_A4C1382F86C)(default) or mi_sensortype_sensor_name (e.g. sensor.mi_temperature_livingroom) (with sensor_names option). Your current sensors with the short nameing (e.g. mi_t_A4C1382F86C) or manually modified names won't be renamed, unless you use the sensor_names option.

0.6.13 - Custom Telink firmware support for LYWSD03MMC sensors

Added support for LYWSD03MMC sensors with custom Telink firmware (by @benkarro). For more information about Telink firmware, see this github page. You can remove the encryption key after flashing the custom firmware.

0.6.12 - Add support for MHO-C303

Add support for MHO-C303 Xiaomi BLE sensor / alarm-clock (by @znanev )

0.6.11 - Add support for MHO-C401

Add support for MMC MHO-C401 Smart BT Thermometer Hygrometer (by @znanev );

0.6.10 - AssertionError fix part 2

Handle missing AssertionError when HA is still in startup. Complements the previous fix in 0.6.9. (@jbalague)

0.6.9 - AssertionError fix

Fix for AssertionError when HA is still in startup (#93) by @mcm69

0.7.1-beta Real-time BLE ADV processing

The logic of the component was almost completely revised in order to implement the processing of BLE ADV messages in real-time. This change makes it possible for the correct implementation of sensors of the "switching" type (switches, proximity sensors), the state of which will now be updated immediately upon receipt of the corresponding message (previously the state was updated only after the time specified in the 'period' option). The principle of processing data from "measuring" sensors has remained the same (averaging all received readings during the 'period' seconds).

Yes, this change has a price (a bit more CPU load), but I seem to have managed to reduce the difference to a paltry one.
In addition, many other improvements have been made. Here are the most significant of them:

• Data processing from several bt-interfaces occurs in one thread (instead of a separate thread for each bt-interface, now the component creates only one additional thread), in the future I expect to make the component completely asynchronous;
• Sensor entities in HA are now created immediately upon arrival of the first message, and not after the time specified in the 'period' option;
• Simplified the process of implementing support for new sensors;
• The report_unknown option takes precedence over the whitelist option;

0.6.8 - whitelist option and Xiaomi Smart Repellent support

• 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;

0.6.8-beta - Xiaomi Mija Mosquito Repellent WX08ZM support

• 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;