Yeah, I appreciate the effort the team expends in getting things like this working and I can see it may be useful, but I turned it off when I got to 2,400 entries in my known_devices.yaml
So it does the same thing low energy scanning no need for the bluetooth to be activated congratulation i did not made this post to start an argument about tech but more to help people who want help
The random Mac address appears to be an issue / feature (depending on how you look at it) of BLE. Unless thereās an option to disable it, youāre a bit stuck.
I think pairing the device to your Google home should allow it to find the real address. I canāt test it myself unfortunately.
You canāt use the config options of one component with another like that. Only the config options listed in the googlehome: doc are valid for the googlehome: componentā¦ Iām surprised it passes validation
Yes they are definitely not clear, and the new changes have been implemented without any real testing. And is now unusable in its current state. So the more constructive input/reports we can make on GitHub the better. Because this component has a lot of potential and am greatful it exists. It just needs some refinement! (Stop the known_devices.yaml from being 60k + on lines!) Firstā¦
Since i set all my devices to track only LE option 2 my know device file stopped being overpopulated and the tracking became faster and more accurate even on the rssi reading.
I have the same issue.
In history it look like thea are all present for 17 minutes and start at reguar intevall so it must be some kind of āmac-spamā
I tried that. Didnāt work for me. The real address is identified only if I manually force my phone to do a scan, then it broadcasts itās real BT mac address. Iām using a Pixel XL on Android 9.