Having trouble getting LYWSD03MMC working, would appreciate some help

First thing: thank you SO much for all your hard work on this!

I’ve managed to get my bind_key’s using @vevsvevs 's customized Android app (see pairings.txt attached) pairings.txt

I’ve add the following to my sensors section of my configuration.yaml:

  - platform: mitemp_bt
    encryptors:
      'A4:C1:38:9A:70:D3': '47a343db0e1aede32f5aa350c91d3b88'
      'A4:C1:38:4B:DD:9A': '025ff01e304006e67e2f83dd59f536f0'
      'A4:C1:38:3E:A9:2A': '10217911862739af9accecc28539a349'
      'A4:C1:38:50:05:91': 'e6f906ebfa60a5f27140b0d9c4efefea'

Is the syntax and indentation correct? Your readme seems to show 11 spaces for each mac:bind_key pair but if I don’t use 2 spaces the yaml parser complains about incorrect indentation.

The component seems to be working as I see in the HA log that it warns about using a custom mitemp and also when I turn on the debug logging it is outputting the right extra lines, however it doesnt seem to find any Xiaomi devices:

2020-03-22 16:40:12 DEBUG (SyncWorker_4) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1827 hci events, 0 xiaomi devices.
2020-03-22 16:41:13 DEBUG (SyncWorker_17) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1872 hci events, 0 xiaomi devices.
2020-03-22 16:42:14 DEBUG (SyncWorker_6) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1797 hci events, 0 xiaomi devices.
2020-03-22 16:43:15 DEBUG (SyncWorker_2) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1827 hci events, 0 xiaomi devices

I have a USB bluetooth dongle, hci0 is working fine, and when I run “sudo hcitool lescan” I can see data packets from LYWSD03MMC devices. (Cant run it since adding the component tho, as the hci0 interface is in use)

I ran a btmon for ~20 minutes and have zipped the log file and attached. problem.zip

Anything look off in any of my syntax? Any pointers on where its going wrong?

Thanks, Sunny

[SunnyM-ha]

Thanks again!

[Magalex2x14]

Or simply refuse to check RSSI, and give it as is. I added this check long time ago when the component dig through hcidump file (as another step of checking the integrity of the package). Yes, I will do so.