undefined | Better HN

0 pointseternityforest2y ago0 comments

You'd just have to have IDs repeat, and software that could tell the difference based on signal strength. If you have two on the same ID that have different RSSI, show them as two tags.

You'd have to do some guesswork though to figure out what's going on but it would be better than nothing, and you might be able to get the size down below what CR2032 allows.

0 comments

2 comments · 1 top-level

lxgr2y ago· 1 in thread

But why only send a single byte if you can send a full UUID within a rounding error of the same resource usage?

If you want it to be compatible with most smartphones, you'll need Bluetooth LE anyway, and that already uses at least 10 bytes on header fields for broadcast packets.

eternityforestOP2y ago

I suppose it is effectively a rounding error unless you change the actual protocol.

I wouldn't be surprised if there was some trivial way for the manufacturers to add ultra low speed non-bluetooth data to the Bluetooth chips though, so you could have 2400 baud IDs with microwatts of power.

But it's probably not worth it since I suspect the real power drain on airtags comes from the high update rates and maybe the 2 way communication.

j / k navigate · click thread line to collapse