AWN BLE Bench

Start the beacon in nRF Connect
Devices only speak BLE while they hear it. This page cannot advertise, so nRF Connect does.

Open nRF Connect

Step by step: set up nRF Connect (first time only)

Tap Copy UUID above, then Open nRF Connect. The Play Store opens: tap Install, or Open if it's already installed.
Tap the Advertiser tab at the top. Swipe left if you don't see it.
Tap the + button. A "New advertising packet" form opens.
Display name: type AWN beacon. It's only a label, so any name works.
Options: leave every checkbox unchecked, including Connectable, Scannable and Adv. Extension.
Set the speed and power. Your phone shows one of these two layouts:
- Interval box: type 160 (that's 100 ms). Tx Power Level box: type 1.
- Or Advertising mode: choose LOW LATENCY. TX power: choose HIGH.
Under Advertising data, tap ADD RECORD and choose Service UUID.
Long-press the UUID field, choose Paste, and tap OK. Check that it matches the UUID shown above exactly.
Leave Scan response data empty and tap OK to save.
Turn on the switch next to AWN beacon. If it asks how long to advertise, choose Until manually turned off.
Power-cycle the AWN within about 1 m (3 ft) of the phone. Its light should go to a steady 50 % within a few seconds.
Come back to this page and tap Find device.

Next time: nRF Connect remembers the beacon. Just open the Advertiser tab and turn AWN beacon on.
Fixture not reacting? Make sure the switch is still on, since Android sometimes turns it off. Then move closer and power-cycle again.
Changed Range in ⚙ settings? The UUID changes too. Edit the record in nRF Connect and paste the new UUID.

Find the device
Chrome lists only AWNs in diagnostic mode that hear the beacon, so the nearest fixtures are the ones listed. Chrome labels each one "Unknown or unsupported device" because the fixture advertises no name; the page cannot change that label. Pick one; it connects and the control screen opens.

AWN BLE bench

Load

Settings & diagnostics

Beacon options

Discovery

Device

Comms log