It won’t work the way you want unless someone writes a smartapp for it. The problem is the edge case where you’re standing right at the limit of what can be detected.
For both the zigbee presence Fob and the phone-based presence detection in smartthings there’s a kind of “debounce” logic built into the hub where it ignores momentary fluctuations in the connected/not connected/connected/not connected sequence.
So let’s say the boundary for connecting the Bluetooth tile to the hub was right at your door mat.
You get to the mat, and whatever subscribes to the presence of the tile says OK there you are.
Your neighbor is walking by and says hello. You turn to wave at them, and you just took your tile out of range again. So now for a presence standpoint it looks like you left again.
Even if you don’t move at all, somebody could move in the house (human bodies block Bluetooth) and suddenly it looks like you went away again.
There are various ways of dealing with this edge case issue. Like I said, the most typical is some kind of Debounce logic. But a tag which is used for “find me” applications doesn’t typically come with the debounce logic because the assumption is the searcher is trying to move closer to it anyway. So that logic would have to be added in some way.
I’m not saying it’s impossible, just that simply adding a Bluetooth antenna to the hub isn’t enough to turn the tile device into a practical presence indicator.
I use I beacons now for presence, and don’t need a Bluetooth antenna in the hub to make it work. I use the IFTTT maker channel. There’s also an oby version just coming out which has a more direct smartthings integration.
Although they cost more, I prefer Ibeacons to tiles for this purpose because they have some additional features, like being able to modulate the signal strength, which lets me set the region size, something I can’t do with tiles.