0.8.1 - [BREAKING CHANGES] mitemp_bt moves to ble_sensor

Breaking changes, read carefully

This update requires configuration changes from you. So please read carefully when upgrading to 0.8.1 (and higher). You can also follow this link for instructions to convert your configuration to the new format.

Our custom component mitemp_bt was designed as a so called sensor platform, which is in Home Assistant language a platform under the sensor integration. Home Assistant however has made an architecture decision in ADR 0007, which basically says that mitemp_bt should be a integration on its own.

So, we decided to make this change and, as it will be a breaking change anyways, we also decided to think about the name of the integration. During time we started to add more and more sensors, not only Xiaomi Mi Temperature sensors, what the name mitemp_bt suggests. We decided that ble_monitor would be a better name to reflect the capablities of our integration. The full name will become Passive BLE Monitor integration.

Note that your sensor names are most likely also renamed. Look for sensors that start for ble (e.g. ble_temperature_livingroom). We strongly recommend to use the new name option (before updating to 0.8+) to easily rename and find your sensors.

In short, if you have the minimal configuration, you will have to change your configuration.yaml

Old configuration

sensor:
  - platform: mitemp_bt

New configuration

ble_monitor:

When you are using one of the following parameters, the configuration has changed compared to the old situation.

• sensor_names
• sensor_fahrenheit
• encryptors
• whitelist

If you use one of these parameters, make sure you read the following
instructions to convert your configuration to the new format.

0.8.1-beta - [BREAKING CHANGES] Move to integration level

Breaking changes, read carefully

This update requires configuration changes from you. So please read carefully when upgrading to 0.8.1 (and higher). You can also follow this link for instructions to convert your configuration to the new format.

Our custom component mitemp_bt was designed as a so called sensor platform, which is in Home Assistant language a platform under the sensor integration. Home Assistant however has made an architecture decision in ADR 0007, which basically says that mitemp_bt should be a integration on its own.

So, we decided to make this change and, as it will be a breaking change anyways, we also decided to think about the name of the integration. During time we started to add more and more sensors, not only Xiaomi Mi Temperature sensors, what the name mitemp_bt suggests. We decided that ble_monitor would be a better name to reflect the capablities of our integration. The full name will become Passive BLE Monitor integration.

Note that your sensor names are most likely also renamed. Look for sensors that start for ble (e.g. ble_temperature_livingroom). We strongly recommend to use the new name option (before updating to 0.8+) to easily rename and find your sensors.

In short, if you have the minimal configuration, you will have to change your configuration.yaml

Old configuration

sensor:
  - platform: mitemp_bt

New configuration

ble_monitor:

When you are using one of the following parameters, the configuration has changed compared to the old situation.

• sensor_names
• sensor_fahrenheit
• encryptors
• whitelist

If you use one of these parameters, make sure you read the following
instructions to convert your configuration to the new format.

0.8.0-beta - [BREAKING CHANGES] Configuration at device level

BREAKING CHANGES

The configuration options have been restructured in 0.8.0. This will allow us to further develop the component in the future and add more options at the level of the sensor device. To make this possible, it was needed to restructure the configuration input. Part of the options have been moved to a new devices option, which has sub-options at device level.

• encryptors
• sensor_names
• sensor_fahrenheit
• whitelist

If you use these options, please follow instructions here to modify your configuration.

Note that not changing your configuration will result in failure of the component to load.

More info about the new options can be found here

0.7.7 - Add support for Fahrenheit sensors

• Add support for sensors that send their temperature data in Fahrenheit. The LYWSD03MMC with custom firmware will send temperature data in Fahrenheit after changing the display to Fahrenheit. Use the new sensor_fahrenheit option for these sensors to get the correct data in Home Assistant.
• sensor_names configuration is now case insensitive
• improved debug logging when using sensor_names option

0.7.7-beta - Adds support for Fahrenheit sensors

This beta release adds support for sensors that send their temperature data in Fahrenheit. The LYWSD03MMC with custom firmware will send temperature data in Fahrenheit after changing the display to Fahrenheit. Use the sensor_fahrenheit option for these sensors to get the correct data in Home Asssitant.

0.7.6 - Battery support LYWSD02

This release adds battery level support for LYWSD02 sensors. Your sensor needs to be updated to firmware 1.1.2_00085 (or later) to support reporting the battery level.

0.7.5 - Fix typo in formaldehyde sensor

Fix typo in formaldehyde sensor (by @MarpleA)

0.7.4 - Code optimization

This time, only some code optimization, reducing the number of lines of python code with about 20%.

• Adding a MeasuringSensor class which is used for all measuring sensors, to shorten the python code (won't affect users)
• Adding device_class Illuminance to illuminance sensors (will change the icon to default Home Asssistant icon)
• Using default unit of measurements from Home Assistant constants (won't affect users)

Changes were based on a small part of the changes as proposed in beta 0.7.1 by @Magalex2x14, further developed by me (@Ernst79).

0.7.4 - beta Code optimization

This time, only some code optimization, reducing the number of lines of python code with about 20%.

• Adding a MeasuringSensor class which is used for all measuring sensors, to shorten the python code (won't affect users)
• Adding device_class Illuminance to illuminance sensors (will change the icon to default Home Asssistant icon)
• Using default unit of measurements from Home Assistant constants (won't affect users)

Changes were based on a small part of the changes as proposed in beta 0.7.1 by @Magalex2x14 further developed by me (@Ernst79).

0.7.3 - Fixing python 3.9 compatibility

This release fixes a bug when running this component in Python 3.9. (fix by @tirkarthi).