AWN BLE bench

starting…
1
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
      

      In nRF Connect: Advertiser → + → Add record → Complete List of 128-bit Service UUIDs → paste →
        Connectable off · Advertising extension off · 100 ms · TX high → toggle ON. Then power-cycle the AWN; its load goes to a steady 50 %.
    

  

  

    
2

    

      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.
      

      
    

  







  

    

      —

      connecting…
    

    
  


  
Load

  

    
    
    
    
    
    
  

  

    
  

  


  

    On / Off / 50 % / Warm / Cool / slider write the Diagnostic Load Control characteristic, which exists only on firmware built from
    feature/diagnostic-load-control. On older firmware they fail with "no Load Control characteristic"; Breathe (Select) and
    Steady 50 % (in ⚙ Settings) work on every build.
  






  
Settings & diagnostics

  

    
checking Web Bluetooth…


    
Beacon options

    

      
      
      
      
      
      
    

    
    

    Range sets the RSSI a fixture must hear the phone at before it answers. Changing it changes the UUID; paste the new one into nRF Connect.

    
Discovery

    

    

    
Device

    
—

    
no advertisement yet

    

      
      

    

    

      firmware's diagnostic "active" state: 50 % @ 3000 K; also stops Breathe

    

      
      
      accepted but a no-op in current firmware (gatt-common-helper.cpp: "Vestigial")
    

    


    
Comms log