This round’s GazeTags research summary covers a camera-free, infrared-beam approach to object awareness. Bluetooth Low Energy (BLE) beacons are the broadcast-based cousin of that idea — simpler to build, already supported by every phone and most microcontrollers, and a genuinely useful primitive for an interactive installation that needs to know “is this specific thing nearby” without any vision pipeline at all.
Two formats, two audiences
iBeacon (Apple’s format) and Eddystone (Google’s, open-spec) both broadcast a small, repeating BLE advertisement packet that any nearby device can read — no pairing, no connection, just passive listening.
- iBeacon is the better choice when iOS compatibility matters: it broadcasts a UUID, major, and minor value that an iOS app can register to listen for in the background, even when not actively running.
- Eddystone comes in several sub-formats — Eddystone-UID (an identifier, like iBeacon) and Eddystone-URL (broadcasts a literal URL, which any nearby phone’s OS-level beacon scanner can surface as a notification, Android especially). Eddystone-URL is the cleanest option if you want a tag that, when approached, offers to open a web page with no app required at all — directly useful for gallery or exhibition signage.
A minimal beacon with CircuitPython
Adafruit’s BLE beacon guide is the fastest path to a working Eddystone transmitter: the adafruit_ble and adafruit_ble_eddystone CircuitPython libraries broadcast your board’s MAC address as an Eddystone UID, or a URL of your choosing (keep it under 18 characters, or shorten it with a URL-shortener service first — the Eddystone-URL encoding scheme only has room for a compact URL, not an arbitrary one). This runs on any CircuitPython-capable board with a BLE radio.
On the ESP32, with Arduino
If your stack is Arduino rather than CircuitPython, ESP32 boards can broadcast either format directly: iBeacon, Eddystone-URL, or Eddystone-UID, all from the same chip with no extra radio hardware. The tradeoff versus CircuitPython is more boilerplate — you’re constructing the raw advertisement packet bytes yourself rather than calling a beacon-specific library function — but it gives you full control over advertising interval and transmit power, which matters once you’re tuning a real installation’s detection range.
Why this belongs next to a camera-free gaze system
GazeTags and a BLE beacon solve adjacent but different problems: GazeTags tells a wearer what’s in front of their head; a beacon tells any nearby listener that a specific tagged thing is close by, with no directionality at all. For an installation that just needs “visitor’s phone is near this sculpture” or “this prop has been picked up,” a beacon is the simpler, cheaper building block — and unlike a camera, it works in the dark, through fabric, and raises none of the same privacy questions.