On board bluetooth, no dongle. I cancelled the order for one. It looks like it’s being a little finicky activating sometimes when I reboot the VM though… bringing one device up and the other showing as ‘unknown’.
Going to have to poke around and see why that is. It brought them both us immediately once I got it up and running though.
You said you got it to work and then it stopped working for both and then for either one and you went with the bluetooth dongle and it’s been perfect since?
Yes i gave up on the on board bluetooth because i tried it on 3 different physical machines with win 7 and win 10. win10 never worked win7 was the one that it found then lost. I think it is a windows thing not wanting to share the bluetooth stack. But who knows. Another drawback for me was that if virtual box had the bluetooth then windows couldn’t connect to any devices . Also it does take ha quite some time to really get stable scanning on my system about 3-5 min . it could be that you have one of the sensors near some interference like microwave cordless phone wifi anything on the 2.4 ghz range will mess with bluetooth. microwave ovens really wreak havoc. other bluetooth devices will stomp on weaker signals like sensors as well so maybe switch places with the better reporting sensor with the lesser one and see if the problem follows?
I am currently installing hassio on a galaxy s6 plus for remote tracking its very interesting and has tons of potential. Have fun !!
looking at sensor readings looks like you definitely have them in pretty different locations. lux and temp is quite different
Thank you for a highly informative series of posts!
I managed to get the ASUS BT400 USB dongle working using your instructions, it already runs and recognizes things as a device tracker, can’t wait to get back home and set up presence recognition with my phone 
Your welcome and glad we could help. Just a pointer with pd , through trial and error I have found that the best settings for quickest detection seems to be 3 seconds scan interval and 30 sec consider home with my setup.This settings does cause some erratic lock toggling sometimes if my wife is at the edge of the bt signal in the kitchen but if I use the recommended settings on the forums off increasing the consider home time to 5 min or more it seems to effect the discovery time when I approach my front door and doesn’t unlock before I reach it. Again just a suggestion on what works best for me, your milage may vary. 
PS.
Please post your findings with your dongle and settings here so that others can benefit from our testing.
Presence detection is a very time consuming, environment dependant and overall challenging part of home automation that to my knowledge has no one way that works for everyone but desperately needs one.
That’s awesome really glad it all worked out for you!
FYI , I found in my environment, that i get the best range and most reliable response with a usb ext cable connected to pc and dongle in other end so that i can place the dongle at a height of approx 3 ft from floor , anything lower or higher than that and signal decreases due to a matrix of wireless 2.4 ghz signals all over my house. of course you may not need this but if you do , it’s a lot easier than trying to teeter your device at the right angle and draping ten extension cords together to get the dongle in that sweet spot where you can have your door unlock just as you reach for the knob. and dang does that impress when it happens .lol
What I discovered was that purely by using my phone I had dark spots in my apartment…it is however true that I don’t use an extension cord for my BT adapter, which shares an area with the Conbee stick (so also 2.4 GHz) and my WiFi router.
I ordered some Tiles and will report how they work. At the moment I don’t have a smart lock, so it wouldn’t be a major problem if it says I’m home a few seconds before I actually reach the door, but do plan on getting one in the future and you’re right that it would be awesome to trigger at just the right moment 
So, here’s my experience so far with the Tiles:
I ended up not using (and uninstalling) the Bluetooth component in HA, the Tiles are BLE so I used the Bluetooth LE Tracker component (the official one)
I set the scan interval to 3 seconds as you mentioned above and get recognized as Home as soon as I turn the keys in the lock (and not before), so yay!
Away is being set 3 minutes after having exited the house (or 3 minutes after removing the Tile battery when I was testing)…I wonder if there is any way to configure this, although the current time might actually be OK, covering taking the trash out without marking me Away
My devices list got spammed with about 220ish BLE devices during the night, which, unless you have some idea regarding it, might require manual deletion from known_devices.yaml when I usually take my VM snapshots…not a huge deal since CPU, disk & RAM usage is steady even with all this scanning
Speaking of CPU usage, I’m running HA on an old i5 machine, so CPU load is 5% even after installing the BLE component, I had heard the Pi gets pretty hammered by that component
I was not able to keep my keys in the door lock (or very near the door) when home, since it triggers Away mode after a few mins (I guess it’s just far enough away from my server for BT to be spotty), however if I come in and leave them on a desk that is a bit better positioned, detection is impeccable (no Away notifications all night)
Overall very pleased so far, a bit more testing is required before adding my gf’s Tile to the system and using them in automations, but I seem to have found their “sweet spots” and if detection remains as reliable as it has been in the past 12 hours, it would be perfect
And yeah, after having tried GPS, WiFi, phone Bluetooth and combinations of these 3 for presence detection, unless things go horribly wrong in the next few days I highly recommend Tiles or any other BLE tracker that is likely to be kept in one place in the home…I have a BLE watch as well, but as opposed to the Tile, I do move around with it when at home, so it might not be optimal.
I had some oddities with the box. I ended up having the issues where it wouldn’t detect or properly use the bluetooth on the host Windows 10 desktop.
Since then I purchased the bluetooth dongle noted earlier in the post. It would connect to hassio fine every time but if I put the bluetooth tracker in the configuration.yaml file, the UI would never come up.
The device would boot and I could SSH or get to my //shares on the device to view things such as logs, config/yaml files just fine and then comment out the bluetooth tracker and sudo reboot now and it would come back up and the UI would work fine.
I’m kind of stumped as to why the UI won’t come up when I enable bluetooth trackers now though.
I tried removing any previously known devices in case maybe that was causing some hiccup in the UI.
Any suggestions as to why the UI wouldn’t come up and just show ‘reconnecting’ forever when I enable bluetooth trackers now?
Scratch my previous post. I was being an idiot and using the bluetooth_tracker which was completely unnecessary.
Since I removed that and added in my mac addresses in the sensors.yaml file (without ’ ’ around the MAC address) it has been working flawlessly.
Great information!!! Just to be clear, are you using the Tile Component for detection or the Bluetooth le Component? The reason i ask is that i never could get the Bluetooth le component to work for me. It always gave errors in the log and would not find any of the le devices so i gave up. If you are using the Bluetooth le tracker component, are you using the same Hassio installation method that i recommended earlier? If not which method are you using? I would really like to get Bluetooth le working because i have ran into a distance issue with regular Bluetooth and le usually has a much longer detection range .Thanks for the information!!
what did you do in order to resolve the issue ?
Well my setup has changed since having this issue but…
If you go up in the thread, there’s a link to a BT dongle that I ordered and after having that, it would pair to my VirtualBox everytime (settings on how it was added above too, specifics laid out by @msauto).
The main issue for me was that I put the bluetooth_tracker in my configuration.yaml, which wasn’t necessary. After I removed that my VM was much better at BT detection but it sometimes wouldn’t pick up consistently.
Since this post though, I’ve acquired a NUC and plugged the dongle into that and it’s always working 100% of the time. It’s been the best solution that I wish I would’ve went with from the start. I don’t have the expensive NUC, I have one of the skinny ones and it’s been amazing. I run Ubuntu server and run HA within docker. I also moved the NUC more central in my home so it picks up everything easier such as zwave, bluetooth, etc. It wasn’t entirely necessary but the NUC allowed me to be more flexible and I took advantage of it.
Completely forgot about your question, sorry for the late reply 
In any case, the Monitor script running on a Pi (and its Bluetooth) has been pretty much flawless since March 8, I’ve given up on the HA BLE trackers.
i’m currently running hassio on RP3+ and i planning to migrate to old mini PC on VM (virtualbox) that i have (i5 8giga ram).
my only question is there a way to retrieve data from Bluetooth devices like in a rp3?
i have 3 of Xiaomi BLE Temperature and Humidity sensor in my house and it be a waste not to be able to use them.
i tried same configuration but it wont poll any data.
i have both on board Bluetooth and external
log file:
2019-04-15 18:18:13 ERROR (MainThread) [homeassistant.components.device_tracker] Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml
2019-04-15 18:18:13 ERROR (MainThread) [homeassistant.components.device_tracker] Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml
2019-04-15 18:18:13 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform bluetooth_tracker
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/device_tracker/init.py”, line 184, in async_setup_platform
disc_info)
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/bluetooth_tracker/device_tracker.py”, line 81, in setup_scanner
for dev in discover_devices():
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/bluetooth_tracker/device_tracker.py”, line 59, in discover_devices
lookup_class=False, device_id=device_id)
File “/usr/local/lib/python3.7/site-packages/bluetooth/bluez.py”, line 26, in discover_devices
device_id = _bt.hci_get_route()
OSError: [Errno 97] Address family not supported by protocol
2019-04-15 18:18:44 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:18:44 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:18:45 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:18:45 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:18:45 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:18:45 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:19:15 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:19:15 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:19:15 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:19:15 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:19:15 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:19:15 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:19:46 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:19:46 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:19:46 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:19:46 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:19:46 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:19:46 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:20:17 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:20:17 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:20:17 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:20:17 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:20:17 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:20:17 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:20:48 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:20:48 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:20:48 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:20:48 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:20:48 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:20:48 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:21:18 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:21:18 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:21:18 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:21:18 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:21:18 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:21:18 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:21:49 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:21:49 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:21:49 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:21:49 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:21:49 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:21:49 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:22:20 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:22:20 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:22:20 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:22:20 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:22:20 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:22:20 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:22:50 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:22:50 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:22:50 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:22:50 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:22:50 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:22:50 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:23:21 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:23:21 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:23:21 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:23:21 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:23:21 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:23:21 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:23:52 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:23:52 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:23:52 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:23:53 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:23:53 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:23:53 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:24:23 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:24:23 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:24:23 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:24:23 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:24:23 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:24:23 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:24:53 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:24:53 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:24:53 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:24:53 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:24:53 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:24:53 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:25:24 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:25:24 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:25:24 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:25:24 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:25:24 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:25:24 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:25:55 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:25:55 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:25:55 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:25:55 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:25:55 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:25:55 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:26:26 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:26:26 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:26:26 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:26:26 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:26:26 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:26:26 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:26:57 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:26:57 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:26:57 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:26:57 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:26:57 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:26:57 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:27:27 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-04-15 18:27:27 WARNING (SyncWorker_2) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:27:27 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:27:27 WARNING (SyncWorker_4) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D1:EE:4B
2019-04-15 18:27:27 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:9F:77
2019-04-15 18:27:27 WARNING (SyncWorker_3) [homeassistant.components.mitemp_bt.sensor] Polling error
any idea?
When you check what USB devices are attached on your VM is it showing the BT adapter with a check mark?
Example below where to check that. (This isn’t HA but it’s a VM I use for something else)
Bluetooth is installed on the VM as well?
Do you have the sensors close to the box hosting the VM? Just to prevent any potential distance limitations?
I’m not too sure what else it could be, it seemed to work for me. Only other thing I have seen is that if something else is connected to that device with bluetooth, it will cause for it not to report back to HA but I doubt that’s the case for you but figured I’d throw it in there in case.
“Bluetooth is installed on the VM as well?” what do you mean? could you show me?
Not sure what your setup is exactly but for my NUC running Linux and HA in docker I had to make sure bluetooth was installed on Linux…
I also had to do this when I was running this on a VM since I was running linux on there as well.
sudo apt install bluetooth
