Passive BLE Monitor integration

nikfo953 · December 16, 2021, 11:47am

Thnx, will switch to other topic/thread.

kordys · December 21, 2021, 4:52pm

Hi guys,

first of all, thanks a lot for this integration!

I went through the discussion history and didn’t find any examples of the HA automation scripts.

Let’s say I have the Yeelight dimmer that exposes the state in a complex way - ‘rotate left 6 steps’. From my point of view, I find it quite difficult to parse this value to use in the automation script.

Have you ever considered providing a set of partial sensors like e.g. type of the action, number of repeats… I know there are some attributes available, but I didn’t find them useful for my case.

The sample use case can be to change the music volume based on the dimmer rotation.

Thanks a lot for any hint/example/note.

Ernst · December 23, 2021, 12:45pm

Why can’t you use the attributes. You can set a trigger on a state change and use the attributes to perform an action.

stain3565 · December 24, 2021, 9:58pm

Struggling a bit. Not too technical with Home Assistant and bluetooth.

Have 3 Qingping Motion and Light Sensors (CGPR1).

Originally added yaml entries, one example below:

ble_monitor:
  bt_interface: 'DC:11:11:11:11:11'
  bt_auto_restart: False
  active_scan: False
  discovery: True
  period: 60
  use_median: False
  decimals: 1
  log_spikes: False
  restore_state: False
  report_unknown: False
  devices:
    # sensor
    - mac: '58:2D:99:99:99:99'
      name: 'Qingping01'
      #encryption_key: '217C568CF5D22808DA20181502D84C1B'
      #temperature_unit: C
      #decimals: 2
      use_median: False
      restore_state: default

It found the sensor in Home assistant but no values in the parameters’

I then tried using the UI way

I think some details were remembered from prev Yaml but it did recognise the mac address. Same result though:


ble illuminance 582D34609BE1  Unavailable
ble illuminance Qingping01   Unknown
ble light Qingping01   No light
ble motion Qingping01   Clear

I realise there may be an encryption issue but I really don’t understand what I need to do with Xiaomi Clouds Token Extractor. Not even sure what should show in the Xiaomi Cloud for my sensors, if anything (nothing currently even though cloud appears to be linked to my account - it opened a page with a new account number when I connect using Xiaomi credentials)

diletone · December 25, 2021, 5:24am

Thanks guys for your hard work on this project. Im having some trouble with bringing the sensors into HA.

I have everything configured per documentation but cannot see sensors in HA. bluetoothctl list shows the correct mac for my controller (TP Link 500). The sensors Im trying to add are Govee 5075 and 5179. The only thing I have missing is the encryption key. Is one required for these sensors?

Ernst · December 25, 2021, 9:08am

Govee sensors need active_scan to be enabled, did you check that setting?

Ernst · December 25, 2021, 9:13am

@stain3565 first thing to check, is the sensor connected to MiHome? If it is, you should be able to get your encryption key with the xiaomi cloud token extractor (It’s required). If not connected to MiHome, than you won’t need the encryption key.

stain3565 · December 25, 2021, 11:46am

@Ernst Thanks for the reply. I have them connected to android Xiaomi Home (is that the same thing?). If I need xiaomi cloud token extractor, I will add it although, as usual in Home Assistant ssh, I have things missing such as pip3 and python3 so not sure how to install. If I do manage to get around this (no idea how yet), do I need to add any extra code?

Ernst · December 25, 2021, 12:41pm

Yes, that’s the same thing.

Xiaomi cloud token extractor is available as a windows exe file, so you can just run it from a PC. It’s just logging in to the xiaomi cloud, so no need to run it on your raspberry. The exe can be downloaded here:

Log in with your xiaomi account (the same you use when you logged in into the Xiaomi app and choose the right server (most people use the china server)

stain3565 · December 25, 2021, 9:56pm

@Ernst Thanks. Got the data. Just one final question (I hope). The data returned does not give me a mac address so I cannot match the data to my 3 devices. How can I recognise which tokens\encryption to use?

Update: No need now. Just a little trial and error with trying each against a mac address and things are looking better. Fingers crossed and thanks again

diletone · December 26, 2021, 1:50am

Yes active scan is enabled. My adapter is a BT 5.0 dongle, could this be the issue.

'Controller E8:48:B8:C8:20:00 (public)
Name: homeassistant
Alias: homeassistant
Class: 0x00000000
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d053C
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
’

matfra · December 26, 2021, 6:36pm

A bit late to reply to your message but I just got a dimmer YLKG08YL yesterday and spent some time trying to integrate it in HA (to control volume in my case). Here is what I have so far. It worknot perfect but fairly reactive.

It seems that there are 3 likely actions:

the dimmer is pressed, or rotated once (easy)
the dimmer is slowly turned multiple times in the same direction
the dimmer is very quickly turned multiple times in the same direction

The 3rd case can be treated by extracting the number of steps but I chose to ignore that.
In the later case, an automation only based on a state change won’t be enough so we need

automations.yaml

- id: '1640458542829'
  alias: livingroom_dimmer_volume_down
  description: ''
  trigger:
  - platform: template
    value_template: '{{int(state_attr(''sensor.ble_dimmer_ydim1'', ''last packet id'')|default(int(states(''input_number.ydim1_last_packet_id'')),
      true)) > int(states(''input_number.ydim1_last_packet_id''))}}

      '
  condition:
  - condition: state
    entity_id: sensor.ble_dimmer_ydim1
    state: rotate left
    attribute: last type of press
  action:
  - service: input_number.set_value
    target:
      entity_id: input_number.ydim1_last_packet_id
    data:
      value: '{{ int(state_attr(''sensor.ble_dimmer_ydim1'', ''last packet id''))
        }}'
  - service: media_player.volume_down
    target:
      entity_id: media_player.big_speakers
  mode: single

configuration.yaml

ble_monitor:
  devices:
    - mac: 'F8:24:41:C8:**:**'
      name: ydim1
      encryption_key: 01250e00b199***************
      reset_timer: 1

input_number:
  ydim1_last_packet_id:
    initial: 0
    min: 0
    max: 255

Andrea_Ciullini · December 30, 2021, 5:56pm

Hello,

I have a Xiaomi Mi temperature device.
I did all the steps described but no entity discovered.
This is my log:

2021-12-30 18:49:35 DEBUG (MainThread) [custom_components.ble_monitor] Initializing BLE Monitor integration (YAML): {'devices': [{'mac': 'A4:C1:38:76:2A:2C', 'name': 'Sala', 'encryption_key': '2d662f68d7f8887f4f9ea29da35b1e3d', 'consider_home': 180, 'use_median': 'default', 'restore_state': 'default', 'tracker_scan_interval': 20, 'reset_timer': 35, 'track_device': False, 'decimals': 'default'}], 'period': 60, 'report_unknown': 'Off', 'discovery': True, 'use_median': False, 'hci_interface': [], 'restore_state': False, 'batt_entities': True, 'bt_interface': ['30:52:CB:F4:B6:57'], 'bt_auto_restart': False, 'log_spikes': False, 'decimals': 1, 'active_scan': False, 'is_flow': False, 'ids_from_name': True}
2021-12-30 18:49:36 DEBUG (MainThread) [custom_components.ble_monitor.config_flow] async_step_import: {'devices': [{'mac': 'A4:C1:38:76:2A:2C', 'name': 'Sala', 'encryption_key': '2d662f68d7f8887f4f9ea29da35b1e3d', 'consider_home': 180, 'use_median': 'default', 'restore_state': 'default', 'tracker_scan_interval': 20, 'reset_timer': 35, 'track_device': False, 'decimals': 'default'}], 'period': 60, 'report_unknown': 'Off', 'discovery': True, 'use_median': False, 'hci_interface': [], 'restore_state': False, 'batt_entities': True, 'bt_interface': ['30:52:CB:F4:B6:57'], 'bt_auto_restart': False, 'log_spikes': False, 'decimals': 1, 'active_scan': False, 'is_flow': False, 'ids_from_name': True}
2021-12-30 18:49:36 DEBUG (MainThread) [custom_components.ble_monitor.config_flow] async_step_user: {'devices': '--Devices--', 'period': 60, 'report_unknown': 'Off', 'discovery': True, 'use_median': False, 'hci_interface': [], 'restore_state': False, 'batt_entities': True, 'bt_interface': ['30:52:CB:F4:B6:57'], 'bt_auto_restart': False, 'log_spikes': False, 'decimals': 1, 'active_scan': False, 'is_flow': False, 'ids_from_name': True}
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] Initializing BLE Monitor entry (config entry): <homeassistant.config_entries.ConfigEntry object at 0x7f9f74ce5510>
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] async_setup_entry: domain {'devices': [{'mac': 'A4:C1:38:76:2A:2C', 'name': 'Sala', 'encryption_key': '2d662f68d7f8887f4f9ea29da35b1e3d', 'consider_home': 180, 'use_median': 'default', 'restore_state': 'default', 'tracker_scan_interval': 20, 'reset_timer': 35, 'track_device': False, 'decimals': 'default'}], 'period': 60, 'report_unknown': 'Off', 'discovery': True, 'use_median': False, 'hci_interface': [], 'restore_state': False, 'batt_entities': True, 'bt_interface': ['30:52:CB:F4:B6:57'], 'bt_auto_restart': False, 'log_spikes': False, 'decimals': 1, 'active_scan': False, 'is_flow': False, 'ids_from_name': True}
2021-12-30 18:49:39 INFO (MainThread) [custom_components.ble_monitor] Available Bluetooth interfaces for BLE monitor: ['30:52:CB:F4:B6:57 (hci0)']
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] async_setup_entry: {'devices': [{'mac': 'A4:C1:38:76:2A:2C', 'name': 'Sala', 'encryption_key': '2d662f68d7f8887f4f9ea29da35b1e3d', 'consider_home': 180, 'use_median': 'default', 'restore_state': 'default', 'tracker_scan_interval': 20, 'reset_timer': 35, 'track_device': False, 'decimals': 'default'}], 'period': 60, 'report_unknown': 'Off', 'discovery': True, 'use_median': False, 'hci_interface': [0], 'restore_state': False, 'batt_entities': True, 'bt_interface': ['30:52:CB:F4:B6:57'], 'bt_auto_restart': False, 'log_spikes': False, 'decimals': 1, 'active_scan': False, 'is_flow': False, 'ids_from_name': True}
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] HCI interface is [0]
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] Spawning HCIdump thread
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] HCIdump thread: Init
2021-12-30 18:49:39 INFO (MainThread) [custom_components.ble_monitor] Attention! Option report_unknown is enabled for Off sensors, be ready for a huge output
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] 1 encryptors mac:key pairs loaded
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] sensor whitelist: []
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] 0 sensor whitelist item(s) loaded
2021-12-30 18:49:39 DEBUG (MainThread) [custom_components.ble_monitor] 0 device tracker(s) being monitored
2021-12-30 18:49:39 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: Run
2021-12-30 18:49:39 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: connected to hci0
2021-12-30 18:49:40 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: start main event_loop
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] Starting binary sensor entry startup
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] BLE binary sensors updater initialization
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] BLE binary sensors updater initialized
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] Binary sensor entry setup finished
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.sensor] Starting measuring sensor entry startup
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.sensor] BLE sensors updater initialization
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.sensor] BLE sensors updater initialized
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.sensor] Measuring sensor entry setup finished
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] Binary entities updater loop started!
2021-12-30 18:49:42 DEBUG (MainThread) [custom_components.ble_monitor.sensor] Entities updater loop started!
2021-12-30 18:50:42 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] 0 MiBeacon BLE ADV messages processed for 0 binary sensor device(s) total. Priority queue = 0
2021-12-30 18:50:43 DEBUG (MainThread) [custom_components.ble_monitor.sensor] 0 BLE ADV messages processed for 0 measuring device(s)
2021-12-30 18:50:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: main event_loop stopped, finishing
2021-12-30 18:50:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: Scanning will be restarted
2021-12-30 18:50:43 DEBUG (Thread-3) [custom_components.ble_monitor] 2 HCI events processed for previous period
2021-12-30 18:50:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: Run
2021-12-30 18:50:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: connected to hci0
2021-12-30 18:50:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: start main event_loop
2021-12-30 18:50:48 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] 0 BLE ADV messages processed last 60 seconds for 0 device tracker device(s)
2021-12-30 18:51:42 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] 0 MiBeacon BLE ADV messages processed for 0 binary sensor device(s) total. Priority queue = 0
2021-12-30 18:51:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: main event_loop stopped, finishing
2021-12-30 18:51:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: Scanning will be restarted
2021-12-30 18:51:43 DEBUG (Thread-3) [custom_components.ble_monitor] 2 HCI events processed for previous period
2021-12-30 18:51:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: Run
2021-12-30 18:51:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: connected to hci0
2021-12-30 18:51:43 DEBUG (MainThread) [custom_components.ble_monitor.sensor] 0 BLE ADV messages processed for 0 measuring device(s)
2021-12-30 18:51:43 DEBUG (Thread-3) [custom_components.ble_monitor] HCIdump thread: start main event_loop
2021-12-30 18:51:48 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] 0 BLE ADV messages processed last 60 seconds for 0 device tracker device(s)

Can you help me please?

Ernst · December 30, 2021, 7:04pm

It doesn’t receive any BLE advertisement, so I guess you have a reception issue. Please check this article in the FAQ for tips. I suspect an SSD drive blocking your Bluetooth radio reception?

ivannmb · December 30, 2021, 10:32pm

I’m trying to use this integration without local bluetooth.

It is working nice with EspHome, but unfortunelly I had thousends of this error in my logs:

HCIdump thread: OS error (hci0): [Errno 19] error while attempting to bind on interface 0: No such device
22:19:26 – (ERRO) Passive BLE monitor (custom integration) - mensagem ocorreu primeiro em 19:55:17 e repetiu-se 144 vezes.

Is it possible avoid this?

Thanks in advance!

Ernst · December 31, 2021, 5:46pm

Ah, that is something I didn’t think of. I’ll create a fix for that.

Cinamon · December 31, 2021, 7:17pm

Can you also add support for Oral-B and Switchbot Curtain to your component?

Ernst · December 31, 2021, 8:11pm

Oral-B support is added in the latest beta already (6.4.3-beta), will be released as final soon. For other devices, please open an issue on github with some BLE advertisements from the device. Instructions are in the FAQ how to get these BLE advertisements

Ernst · January 1, 2022, 7:31pm

Changes in 6.4.3

6.4.3 adds support for the following devices

Inkbird iBBQ thermometer (2 probes version) [1]
Oral-B toothbrush (7000 series)
b-parasite plant sensor

[1] If you have a 4 or 6 probe Inkbird iBBQ device, please let us know by opening a new issue, such that we can create support for these.

RadoZA · January 1, 2022, 10:19pm

Hi,
I used LYWSDCGQ with my BT5.0 USB dongle, and it worked great, but after some update I can’t get it work. I have already tried delete whole integration, add it again, but this integration can’t see my devices. I have tried again pair it in Xiaomi Home application (with success) .

my device is:
Bus 002 Device 006: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio

it is working and it can see my BT tempereature sensor 58:2D:34:37:xx:xx

root@nas:/HA# hcitool lescan
LE Scan ...
9C:19:C2:FD:E0:5C (unknown)
4B:CF:7F:A7:FB:D0 (unknown)
13:9B:82:E5:49:99 (unknown)
C1:8D:6E:46:CF:00 RK-G200S-E
C1:8D:6E:46:CF:00 (unknown)
45:D3:22:34:8D:AF (unknown)
45:D3:22:34:8D:AF (unknown)
58:2D:34:37:27:D0 (unknown)
58:2D:34:37:27:D0 MJ_HT_V1
FA:33:A9:E3:D6:4C (unknown)
4C:D2:80:14:6E:38 (unknown)
58:2D:34:37:24:46 (unknown)
58:2D:34:37:24:46 MJ_HT_V1
E9:AE:FC:32:7C:A0 (unknown)

BT permissions:

root@nas:/HA# getcap `readlink -f /usr/bin/python3`
/usr/bin/python3.9 cap_net_admin,cap_net_raw=eip

But it does not show anything in HA:

Here are my debug logs:

root@nas:/HA# grep "ble_monitor" home-assistant.log
2022-01-01 23:08:39 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-01-01 23:09:25 DEBUG (MainThread) [custom_components.ble_monitor.config_flow] async_step_user: None
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.config_flow] async_step_user: {'bt_interface': ['00:E0:4C:6A:FF:03'], 'bt_auto_restart': True, 'active_scan': True, 'discovery': True, 'use_median': False, 'period': 60, 'decimals': 1, 'log_spikes': False, 'restore_state': False, 'report_unknown': 'Off', 'devices': '--Devices--'}
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.config_flow] _create_entry: {'bt_interface': ['00:E0:4C:6A:FF:03'], 'bt_auto_restart': True, 'active_scan': True, 'discovery': True, 'use_median': False, 'period': 60, 'decimals': 1, 'log_spikes': False, 'restore_state': False, 'report_unknown': 'Off', 'devices': '--Devices--'}
2022-01-01 23:09:39 INFO (MainThread) [homeassistant.setup] Setting up ble_monitor
2022-01-01 23:09:39 INFO (MainThread) [homeassistant.setup] Setup of domain ble_monitor took 0.0 seconds
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] Initializing BLE Monitor entry (config entry): <homeassistant.config_entries.ConfigEntry object at 0x7feb3ba8a460>
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] async_setup_entry: domain {}
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] async_setup_entry: {'bt_interface': ['00:E0:4C:6A:FF:03'], 'bt_auto_restart': True, 'active_scan': True, 'discovery': True, 'use_median': False, 'period': 60, 'decimals': 1, 'log_spikes': False, 'restore_state': False, 'report_unknown': 'Off', 'devices': [], 'is_flow': True, 'hci_interface': [0]}
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] HCI interface is [0]
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] Spawning HCIdump thread
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] HCIdump thread: Init
2022-01-01 23:09:39 INFO (MainThread) [custom_components.ble_monitor] Attention! Option report_unknown is enabled for Off sensors, be ready for a huge output
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] 0 encryptors mac:key pairs loaded
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] sensor whitelist: []
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] 0 sensor whitelist item(s) loaded
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor] 0 device tracker(s) being monitored
2022-01-01 23:09:39 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: Run
2022-01-01 23:09:39 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: connected to hci0
2022-01-01 23:09:39 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.ble_monitor
2022-01-01 23:09:39 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.ble_monitor
2022-01-01 23:09:39 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.ble_monitor
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] Starting device tracker entry startup
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] BLE device tracker updater initialization
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] BLE device tracker updater initialized
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] Device Tracker entry setup finished
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] Starting binary sensor entry startup
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] BLE binary sensors updater initialization
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] BLE binary sensors updater initialized
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] Binary sensor entry setup finished
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.sensor] Starting measuring sensor entry startup
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.sensor] BLE sensors updater initialization
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.sensor] BLE sensors updater initialized
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.sensor] Measuring sensor entry setup finished
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] Device tracker updater loop started!
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] Binary entities updater loop started!
2022-01-01 23:09:39 DEBUG (MainThread) [custom_components.ble_monitor.sensor] Entities updater loop started!
2022-01-01 23:09:39 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: start main event_loop
2022-01-01 23:10:39 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] 0 BLE ADV messages processed last 60 seconds for 0 device tracker device(s)
2022-01-01 23:10:39 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] 0 MiBeacon BLE ADV messages processed for 0 binary sensor device(s) total. Priority queue = 0
2022-01-01 23:10:39 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: main event_loop stopped, finishing
2022-01-01 23:10:39 DEBUG (MainThread) [custom_components.ble_monitor.sensor] 0 BLE ADV messages processed for 0 measuring device(s)
2022-01-01 23:10:39 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: Scanning will be restarted
2022-01-01 23:10:39 DEBUG (Thread-20) [custom_components.ble_monitor] 2 HCI events processed for previous period
2022-01-01 23:10:39 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: Run
2022-01-01 23:10:39 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: connected to hci0
2022-01-01 23:10:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: start main event_loop
2022-01-01 23:11:40 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] 0 BLE ADV messages processed last 60 seconds for 0 device tracker device(s)
2022-01-01 23:11:40 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] 0 MiBeacon BLE ADV messages processed for 0 binary sensor device(s) total. Priority queue = 0
2022-01-01 23:11:40 DEBUG (MainThread) [custom_components.ble_monitor.sensor] 0 BLE ADV messages processed for 0 measuring device(s)
2022-01-01 23:11:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: main event_loop stopped, finishing
2022-01-01 23:11:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: Scanning will be restarted
2022-01-01 23:11:40 DEBUG (Thread-20) [custom_components.ble_monitor] 2 HCI events processed for previous period
2022-01-01 23:11:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: Run
2022-01-01 23:11:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: connected to hci0
2022-01-01 23:11:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: start main event_loop
2022-01-01 23:12:40 DEBUG (MainThread) [custom_components.ble_monitor.device_tracker] 0 BLE ADV messages processed last 60 seconds for 0 device tracker device(s)
2022-01-01 23:12:40 DEBUG (MainThread) [custom_components.ble_monitor.binary_sensor] 0 MiBeacon BLE ADV messages processed for 0 binary sensor device(s) total. Priority queue = 0
2022-01-01 23:12:40 DEBUG (MainThread) [custom_components.ble_monitor.sensor] 0 BLE ADV messages processed for 0 measuring device(s)
2022-01-01 23:12:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: main event_loop stopped, finishing
2022-01-01 23:12:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: Scanning will be restarted
2022-01-01 23:12:40 DEBUG (Thread-20) [custom_components.ble_monitor] 2 HCI events processed for previous period
2022-01-01 23:12:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: Run
2022-01-01 23:12:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: connected to hci0
2022-01-01 23:12:40 DEBUG (Thread-20) [custom_components.ble_monitor] HCIdump thread: start main event_loop

Any help ?
Thank You.