> That will be accurate at the tuple space, but not down to the nearest centimeter
Yes, you're right. Sorry, I didn't mean to imply centimeter-level precision anywhere. I said "high precision" because I compare it to GPS and not RTT (which was not common when I started this project). Unlike FIND, any nearest-centimeter precision requires specialized hardware (to be available on Android P in the future! [1]).
The FIND system fills a niche where you might need room-level or sub-room level precision without having to install anything except an app on your phone or computer.
> any mass between the marker and the tracked device will throw off readings
Its true that individual readings will be affected by varying obstacles (doors/people), and this will throw off location classification if you have very few signal generating devices in the vicinity. However, generally places will see Bluetooth/WiFi coming from their neighbors in all directions so it would be hard to attenuate all signals simultaneously. The machine learning is pretty robust too, so if one of the readings get thrown off because there are still several others that can compensate.
[1]: https://developer.android.com/preview/features.html#rtt