A scan on Bluetooth (although N/A for this situation) can't possibly give away any position. A scan of wifi might, if the device happens to pick up a wi-fi source that Google has already collected (by some means). Still not very relevant though - it would mean that location permission would be needed in order to use wi-fi at all, because how would it otherwise find the hotspot or access point you want to connect to.. other than having to enter the SSID manually every time. But we don't have to enable location tracking to do that.
To configure Chromecast though, 'google home' (which replaced the 'chromecast' application or whatever it was), takes you to Settings and unless you turn on location tracking it refuses to look for the dongle.
You now have to have that location tracking permission to scan wifi SSIDs, and it came about because spammy data stealing apps were using SSID maps to get rough location.
Not to say Google isn't evil because they certainly seem to be headed to hell while holding us in a hand basket, but this one is legit.
Yeah, I get that.. it's not unreasonable. However, why does Google Home force you to turn on location tracking in general, that's what I don't get.
It sounds like apps scanning for SSIDs could easily be handled by a specific permission for that. No need to enable location tracking (turning 'Location' "on" in Settings) for this. It doesn't make any sense (except for what it looks like: Google wants to get your location, by any means).
