custom-components/ble_monitor 0.8.3-beta

0.8.3-beta - [BREAKING CHANGES]

on GitHub

Changes:

• events from binary sensors are processed in real-time, the state is updated immediately when a corresponding BLE message arrives

Breaking changes, read carefully

This update requires configuration changes from you. So please read carefully when upgrading to 0.8.x from 0.7.x (or lower). 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.