Yes, tried the ble_monitor: method without any luck.
Finished. Parsed: 3 hci events, 0 xiaomi devices.
This one is the one with the most hci events.
Tomorrow I’ll try to plug a bluetooth usb dongle to this proxmox VM instead of using the host builtin bluetooth and see what happens.
What is weird, is that from the hassio SSH & terminal plugin, if I type bluetoothctl scan on I see those devices
If you are not impatient, then you better not try the fork, otherwise you will have to deal with breaking changes later. An external dongle should help you temporarily solve your situation. In the meantime, I made a decision to force the solutions to this problem, postponing the rest of the tasks…
This morning, I’ve tried the fork you linked me, with builtin bluetooth, with usb bluetooth. Still no luck, right now i’m using a spare ESP32 I had lying around and it works perfectly.
When you have an error during updating in HACS from 0.7.x to 0.8.x (Error: No content to download), try to uninstall the component, restart home assistant and install it again. It is most likely a sync issue in HACS due to the folder change.
I’m trying to configure my new Cleargrass (Qingping) CGD1 clocks with this ble_monitor integration but I’m not being able to get any info out of those pretty clocks.
Trying to upfront answer to any upcoming questions, I configured the CGD1 device with the mac address and encryption_key I got out of the Qingping+ android mobile app (from the qingping.log file the app generates).
I also tried to get those information out of the Telink Flasher app, but as I click on the Do Activation button I get the Not connected error
Log:
17:39:53: Searching for devices
17:40:07: TypeError: device.watchAdvertisements is not a function
17:40:07: Reconnect 1 from 5
17:40:14: Connected
17:40:16: Not connected
17:40:23: Not connected
Just for additional info, if I change the discovery: False option to True , I can see the details of my LYWSD02 sensors details, but not the CGD1 ones.
Attempting to connect a new HHCCJCY01. Using internal bluetooth on RPi 4 Hassio, sensor laying directly next to the RPI. I get the following on both 8.1 and 8.2-beta:
2020-11-16 15:26:23 DEBUG (SyncWorker_7) [custom_components.ble_monitor.sensor] HCIdump threads count = 1
2020-11-16 15:26:23 DEBUG (SyncWorker_7) [custom_components.ble_monitor.sensor] 0 encryptors mac:key pairs loaded.
2020-11-16 15:26:23 DEBUG (SyncWorker_7) [custom_components.ble_monitor.sensor] whitelist: []
2020-11-16 15:26:23 DEBUG (SyncWorker_7) [custom_components.ble_monitor.sensor] 0 whitelist item(s) loaded.
2020-11-16 15:26:24 DEBUG (SyncWorker_7) [custom_components.ble_monitor.sensor] update_ble called
2020-11-16 15:26:24 DEBUG (SyncWorker_7) [custom_components.ble_monitor.sensor] First run, skip parsing.
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] update_ble called
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] Discovering Bluetooth LE devices
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] Time to analyze...
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] Getting data from HCIdump thread
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] Spawning HCIdump thread(s).
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] HCIdump thread: Init
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] HCIdump thread: Init finished
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] Starting HCIdump thread for hci0
2020-11-16 15:27:24 DEBUG (Thread-9) [custom_components.ble_monitor.sensor] HCIdump thread: Run
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] HCIdump threads count = 1
2020-11-16 15:27:24 DEBUG (SyncWorker_23) [custom_components.ble_monitor.sensor] 0 HCI Events parsed, 0 BLE ADV messages processed for 0 known device(s).
2020-11-16 15:27:24 ERROR (Thread-9) [custom_components.ble_monitor.sensor] HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
Indeed I was able to add them to the MiHome app v5.8.42, it was easely discovered and configured, but I wasn’t able to add it to the old MiHome v5.0.0 , it did not discover it (probably because by then this devices did not exist).
That’s why I used the Qingping+ app since it discovers it and records information in the qingping.log file that I believe is the correct one (maybe I’m wrong)
Edit: it appears I might have disabled bt during my Razberry v2 module set up. I might need to explore a different z-wave controller or research other options.
