sl_bt_evt_gatt_server_user_write_requestGATT Server

Indicates that a remote GATT client is attempting to write a value of an attribute into the local GATT database, where the attribute was defined in the GATT database XML file to have the type="user".

Data Structures
struct	sl_bt_evt_gatt_server_user_write_request_s
	Data structure of the user_write_request event.

Macros
#define	sl_bt_evt_gatt_server_user_write_request_id   0x020a00a0
	Identifier of the user_write_request event.

Detailed Description

Indicates that a remote GATT client is attempting to write a value of an attribute into the local GATT database, where the attribute was defined in the GATT database XML file to have the type="user".

The parameter att_opcode informs which attribute procedure was used to write the value. If the att_opcode is gatt_write_request (see gatt_att_opcode), the application needs to respond to this request by using the sl_bt_gatt_server_send_user_write_response command within 30 seconds, otherwise further GATT transactions are not allowed by the remote side. If the value of att_opcode is gatt_execute_write_request, it indicates that this is a queued prepare write request received earlier and now the GATT server is processing the execute write. The event sl_bt_evt_gatt_server_execute_write_completed will be emitted after all queued requests have been processed.

---

Data Structure Documentation

◆ sl_bt_evt_gatt_server_user_write_request_s