ABR100

BRY100 / ABR100 is a professional BLE 5.1 relay. BRY100 is the non-encrypted variant; ABR100 is the encrypted variant with AES128 secure communication.

Connect to the ABR100 BLE relay over Bluetooth. After connection, the master device must complete the Encryption Authorization process within 10 seconds, or the relay will disconnect. Once authorized, relay output can be controlled using AT commands.

After connecting to the ABR100 by Bluetooth, the master device must perform the Encryption Authorization process. The authorization timeout is 10 seconds — if authorization is not completed in time, the relay actively disconnects.

• AT@SET=5# — disable relay; NC pin switches to COM pin.
• AT@SET=6# — enable relay; NO pin switches to COM pin.

BLE advertisement payload layout:

• Device type 0xF0 — ABR100.
• Frame 0x01 — “AT DEV” advertisement.
• Version — software version format R01A02V03.
• Encrypt — whether communication is encrypted; ABR100 defaults to AES128.

Relay output state values in advertisement:

• 0 — Relay NC
• 1 — Relay NO
• 2 — Gradual NC process
• 3 — Gradual NO process
• 4 — Enable output duration

Before communication commands, authorization is required. After authorization succeeds, data exchange uses AES-128 encryption.

The ABR100 secures communication by combining AES-128 encryption with an identity authorization process. In this process, the other device is the master and ABR100 is the slave. All control commands are dynamically encrypted using AES. Refer to the Assistant Telematics BLE AES Encryption Protocol document for AES details.

Encryption authorization process:

• Step 1 — Master request: The master sends AT@SET=10,Authority Vector# encrypted by AES-128. The Authority Vector is 32 bytes of hex ASCII data generated randomly by the master. Example: AT@SET=10,00112233445566778899AABBCCDDEEFF#
• Step 2 — Relay verification and response: When the slave receives the command, it decrypts using the initially defined key and vector to obtain the Authority Vector as the reply encrypting vector. It encrypts @SET:10,0# + New Vector and sends it back. A 16-byte random number is appended directly after the plaintext in each response; it serves as the vector for future communication and is encrypted together with the plaintext.
• Step 3 — Master verification: The master decrypts the response using the Authority Vector. If the format is correct, authorization succeeds. The master extracts the New Vector from the slave for subsequent control commands.

Exception synchronization: If a vector mismatch occurs between master and slave, the master can resend AT@SET=10 encrypted by the initial key and vector to re-trigger authorization and re-synchronize the vector. The slave can respond to the authorization command at any time.

All commands use ASCII characters. Each command ends with #. Parameters are separated by commas and may use characters 0–9, A–Z, a–z.

Disable relay — AT@SET=5#

Response: @SET:5,0# (result code per error codes table).

Enable relay — AT@SET=6#

Response: @SET:6,0#

Gradual enable relay — AT@SET=7,<first phase>,<cycle time>,<step time>#

Example: AT@SET=7,1,10,1# — Response: @SET:7,0#

Gradual disable relay — AT@SET=8,<first phase>,<cycle time>,<step time>#

Example: AT@SET=8,1,10,1# — Response: @SET:8,0#

Enable output duration — AT@SET=9,<enable state>,<active duration>,<inactive duration>,<toggle times>#

Example: AT@SET=9,1,10,1# — Response: @SET:9,0#

Encryption authorization — AT@SET=10,<Authority Vector>#

Example: AT@SET=10,00112233445566778899AABBCCDDEEFF# — Response: @SET:10,0#

Get version information — AT@GET=2#

Response: @GET:2,0,<software version># (version up to 6 characters). Example: @GET:2,0,000101#

Get relay state — AT@GET=3#

Response: @GET:3,0,<relay state># where relay state is:

• 0 — Relay NC
• 1 — Relay NO
• 2 — Gradual NC process
• 3 — Gradual NO process
• 4 — Enable output duration

Example: @GET:3,0,0#

Preparation:

• BRY100 / ABR100: Ensure the device can broadcast and be discovered by the phone; it is better to know the device's Bluetooth address.
• Software: Install the GRToolbox App — https://www.goodix.com/en/software_tool/grtoolbox
• Firmware: Contact support@iot-at.com to get the latest firmware *.bin file and save it on your mobile phone.

Upgrade procedure:

• Open the App and enable Bluetooth permissions on your phone.
• Find the target device by its Bluetooth address or device name, and click Connect.
• After a successful connection, click the rocket icon to enter the upgrade interface.
• Choose Copy Mode, enter Copy Address 01040000, select the firmware *.BIN file, and press Update.
• Wait until the firmware update completes successfully.