I don't know how accurate beacons are but I recently visited the Greenwich museum in Greenwich, the Museum of Musical Instruments in Brussels, In Flanders Field

I don't know how accurate beacons are but I recently visited the Greenwich museum in Greenwich, the Museum of Musical Instruments in Brussels, In Flanders Fields Museum in Ypres, and Casa Mila in Barcelona. All of which had audio tours using numbers (punch the number on some device they hand you) and all of them were fairly crowded and dense. If they were using beacons and the beacons had a range or more than about 1 to 1.5 meters I'd imagine a lot of conflicting inputs. I suppose good UX design could mitigate that showing all the options from all nearby beacons. I guess it just has me wondering is this a solution in search of a problem. Reading the article it also sounds like lots of poorly designed software. The author complained about pairing being a chore but it seems like with some good software you'd just put up any beacon, scan it, then pick what it corresponds to. If that beacon disappears or breaks just pick any beacon out of sack of beacons, place, scan, pick what it corresponds to. That seems like it should be a trivial 5 second operation. Am I missing something? I shouldn't care what the id is. I only care that it's unique to every other beacon (which the software can tell me the moment I scan it). I don't care about major or minor numbers. Just put any beacon anywhere, scan, pick what it corresponds to. Done.