Releases: custom-components/ble_monitor
0.5.7 - VegTrug Grow Care Garden support added
- VegTrug Grow Care Garden support added (plant sensor, similar to MiFlora HHCCJCY01)
0.5.6 - service release
- Some optimizations and fixes.
- FAQ was supplemented with details about the features of this component and some methods of increasing the coverage area were also added.
0.5.5 - multiple interfaces and battery entities
Changes since 0.5.3
New configuration options:
- batt_entities (boolean)(Optional) Default value: False
By default, the battery information will be presented only as a sensor attribute called battery level.
If you set this parameter to True
, then the battery sensor entity will be additionally created
(sensor.mi_batt_ <sensor_mac_address>).
- hci_interface (positive integer or list of positive integers)(Optional) Default value: 0
Prior to this release, this option supported specifying only one interface.
Now it is possible to specify a list of interfaces. Data will be collected from all specified interfaces simultaneously.
For example:
sensor:
- platform: mitemp_bt
hci_interface:
- 0
- 1
Beta testing: Work with multiple interfaces simultaneously
Added the ability to specify a list for a hci_interface
option, that is, now it is possible to collect data from several interfaces simultaneously:
- platform: mitemp_bt
hci_interface:
- 0
- 1
Beta testing: Separate entities for the battery
New option added:
batt_entities
(boolean)(Optional) By default, the battery information will be presented only as a sensor attribute called battery level
. If you set this parameter to True
, then the battery sensor entity will be additionally created - sensor.mi_batt_ <sensor_mac_address>
. Default value: False
0.5.3 moved to master branch
Changes since 0.4
The component does not use external utilities anymore, we get access to data directly from python, from a separate tread.
New configuration options:
- active_scan: False
- hci_interface: 0 (integer number, 0 as default for hci0, 1 for hci1 and so on)
Deprecated configuration options:
- hcidump_active is deprecated and must be removed from
configuration.yaml
)
NB:
Since the component now uses direct access to the HCI interface, python must have the appropriate rights, see paragraph 1 of the HOW TO INSTALL section
In addition, we began to collect Frequently Asked Questions. Please read it before creating a new issue.
0.4.3 - service release
This is a service release that simplifies the process of implementing sensor support with a different set of measurements.
FlowerPot support
Added support for HHCCPOT002 sensor (FlowerPot, RoPot, broadcasts moisture and conductivity, 1 reading per minute, no battery info). #28
release 0.4.1 - small fix
Messages "Unknown sensor type" moved to debug level, preventing log overflow under certain conditions. #17
Other Xiaomi sensors support
Changes since 0.3.0:
In addition to LYWSDCGQ, added support for the following Xiaomi sensors (please check updated README.md):
- LYWSD02 (rectangular body, E-Ink)
- CGG1 (round body, E-Ink)
- HHCCJCY01 (MiFlora)
Attributes added:
- RSSI in dBm (Received Signal Strength Indicator)
- Device type
Fixed:
- Now the component correctly terminates the subprocesses, there are no more zombies when restarting HA.
- Improved malformed (or unknown?) messages detection.