Skip to content

Releases: custom-components/ble_monitor

0.6.7-beta: whitelist option

27 Apr 01:50
Compare
Choose a tag to compare
Pre-release
  • 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 neighboring 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.

0.6.6 - tighter filtering of received data

26 Apr 16:41
c3e1a82
Compare
Choose a tag to compare

Actually, Mija object ID (data type field) must be two bytes long.

So far, the old algorithm checking only one byte of these two has been sufficient.
However, there was a precedent that revealed the insufficiency of this approach - #64.

0.6.6-beta - tighter filtering of received data

19 Apr 17:41
Compare
Choose a tag to compare

Actually, Mija object ID (data type field) must be two bytes long.

So far, the old algorithm checking only one byte of these two has been sufficient.
However, there was a precedent that revealed the insufficiency of this approach - #64.

I have aligned the code, but this change may lead to a refusal to receive data from some sensors that violate this rule.

Public beta test required!

0.6.5 - support for JQJCY01YM Xiaomi Honeywell Formaldehyde Sensor

12 Apr 13:10
Compare
Choose a tag to compare
  • support for JQJCY01YM Xiaomi Honeywell Formaldehyde Sensor
    (about 50 messages per minute total: temperature + humidity + formaldehyde + battery level)

  • decimals: 1 by default (instead of decimals: 2)

  • some multithreading optimizations

For JQJCY01YM owners: since the formaldehyde sensor returns values ​​in the range from 0 to 1.5 mg / m3 with a resolution of 0.01, the number of decimal places for the formaldehyde sensor is forced to 3 (in case of enabled rounding).

0.6.4-beta: support for JQJCY01YM sensor

06 Apr 08:37
Compare
Choose a tag to compare
  • support for JQJCY01YM sensor Xiaomi Honeywell Formaldehyde Sensor
    (about 50 messages per minute total: temperature + humidity + formaldehyde + battery)

  • decimals: 1 by default (instead of decimals: 2)

  • some multithreading optimizations

For JQJCY01YM owners: since the formaldehyde sensor returns values ​​in the range from 0 to 1.5 mg / m3 with a resolution of 0.01, it is necessary to force at least two decimal places in case of rounding. So far I decided to try 3.

0.6.3 - resolving some compatibility issues

23 Mar 09:40
Compare
Choose a tag to compare
  • Refusal to check RSSI value to workaround strange positive numbers for some BT-dongles #57
  • A small delay in the parser was introduced to reduce the CPU load on slow machines (like Raspberry Pi Zero)

The problem with positive RSSI caused the component to discard all data packets.
If you tried to install the component, but did not get the result for unclear reasons, then it may make sense to try this version (I do not exclude that case #57 might not be unique).

0.6.2 - ClearGrass (Qingping) CGD1 alarm clock support

11 Mar 22:02
Compare
Choose a tag to compare
  • ClearGrass CGD1 alarm clock support ("encryptor")

0.6.2-beta - initial ClearGrass CGD1 alarm clock support

10 Mar 21:13
Compare
Choose a tag to compare
  • initial ClearGrass CGD1 alarm clock support
  • minor optimizations

0.6.1 - report_unknown to info log level

08 Mar 19:31
f5977a9
Compare
Choose a tag to compare

The output produced by the component when the report_unknown option is enabled is redirected to the info loglevel. This will facilitate the implementation of support for new sensors. And expands possible usecases. Details about the new option in README and FAQ.

0.6.0 - encrypted BLE ADV payload support and more

08 Mar 13:58
ed9c479
Compare
Choose a tag to compare

Changes since 0.5.7

  • encrypted BLE ADV payload decryption implemented
  • added new option encryptors to describe the correspondence between the mac-address of the sensor broadcasting encrypted adverts and the encryption key
  • LYWSD03MMC support ("encryptor")
  • added new option report_unknown designed to enable logging of all BLE ADV messages from unsupported Xiaomi ecosystem devices
  • error "Attribute hass is None for Entity..." fixed
  • fix for VegTrug Grow Care Garden sensor
  • other minor bugfixes and improvements