BLE : BlueTooth Low Energy, designed for very low power operation. It supports multiple network topologies, including a point-to-point option used for data transfer, a broadcast option used for location services and a mesh option used for creating large-scale device networks. Only Server profile is available when FreeRTOS is activated List of application types, can be: - Transparent mode - Server profile - Client profile - Router profile List of application types, can be: - Transparent mode - Server profile - Client profile - Router profile You can enable this mode only if OTA mode is disabled You can enable this mode only if BT SIG Beacon and OTA modes are disabled You can enable this mode only if BT SIG Beacon and OTA modes are disabled You can enable this mode only if BT SIG Beacon and OTA modes are disabled You can enable this mode only if BT SIG Beacon and OTA modes are disabled Custom template Custom template can be enabled only if BT SIG Blood Pressure Sensor or BT SIG Health Thermometer Sensor or BT SIG Heart Rate Sensor or Custom P2P Server is(are) enabled Custom template can be enabled only if BT SIG Blood Pressure Sensor or BT SIG Health Thermometer Sensor or BT SIG Heart Rate Sensor or Custom P2P Server is(are) enabled Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined. Max size is 7 characters Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined Advertising information, user defined ex: 0x7257acd87a6c ex: 0x7257acd87a6c Shall be < 80ms Shall be &gt 20ms and &lt 10240ms Shall be &lt 80ms Shall be &lt 80ms Shall be &lt 80ms Shall be < 80ms Shall be &lt 100ms Shall be &gt 20ms and &lt 10240ms Shall be &lt 100ms Shall be &lt 100ms Shall be &lt 100ms Shall be &lt 100ms Shall be &lt 1s Shall be &lt 1s Shall be &lt 1s Shall be &lt 1s Shall be &lt 2.5s Shall be &lt 2.5s Shall be &lt 2.5s Shall be &lt 2.5s Pairing process management Pairing process management Define Bonding modes Possible values: - No-bonding mode(0x00) - Bonding mode(0x01) Define Bonding modes Define Fixed Pin option, if set to 1 then CFG_FIXED_PIN will be ignored Define Fixed Pin option, if set to 1 then CFG_FIXED_PIN will be ignored Any random value between 0 and 999999 Any random value between 0 and 999999 Encryption key maximum size Encryption key maximum size Encryption key minimum size Encryption key minimum size Define IO capabilities Possible values: - CFG_IO_CAPABILITY_DISPLAY_ONLY (0x00) - CFG_IO_CAPABILITY_DISPLAY_YES_NO (0x01) - CFG_IO_CAPABILITY_KEYBOARD_ONLY (0x02) - CFG_IO_CAPABILITY_NO_INPUT_NO_OUTPUT (0x03) - CFG_IO_CAPABILITY_KEYBOARD_DISPLAY (0x04) Define IO capabilities Activate/deactivate Define Man In The Middle(MITM) protection mode Possible values: - MITM protection not required (0x00) - MITM protection required (0x01) Activate/deactivate Define Man In The Middle(MITM) protection mode Define Secure Connections Support Possible values: - Secure Connections Paring not supported (0x00) - Secure Connections Paring supported but optional (0x01) - Secure Connections Paring supported and mandatory(0x02) Define Secure Connections Support Define MITM modes Possible values: - Keypress notification not supported (0x00) - Keypress notification supported (0x01) Define MITM modes P2P Server number L2CAP Connection Update request parameters used for test only with smart Phone L2CAP Connection Update request parameters used for test only with smart Phone Enable Debug Trace Enable Debug Trace. LPUART1 and CFG_HW_LPUART1_ENABLED shall be activated Enable Debug Trace. USART1 and CFG_HW_USART1_ENABLED and shall be activated Enable Debug Trace. One UART shall be activated Enable Debug Trace. USART1 shall be slected Enable Debug Trace. LPUART1 shall be slected UART choice for GUI UART shall be selected when Thread_Cli_Cmd is selected UART shall be selected when Thread_Cli_Cmd is selected UART shall be selected when Thread_Cli_Cmd is selected UART shall be selected when Thread_Cli_Cmd is selected UART shall be selected when Thread_Cli_Cmd is selected UART shall be selected when Thread_Cli_Cmd is selected UART shall be selected when Thread_Cli_Cmd is selected UART shall be selected when Thread_Cli_Cmd is selected UART choice for GUI UART shall be selected as it is mandatory for Transparent Mode UART shall be selected as it is mandatory for Transparent Mode UART shall be selected as it is mandatory for Transparent Mode UART shall be selected as it is mandatory for Transparent Mode UART shall be selected as it is mandatory for Transparent Mode UART shall be selected as it is mandatory for Transparent Mode UART shall be selected as it is mandatory for Transparent Mode UART shall be selected as it is mandatory for Transparent Mode UART choice for GUI UART choice for GUI Enable/Disable USB interface. Mandatory to be set to Enabled for Transparent Mode VCP Enable/Disable USB interface CFG_RTCCLK_DIVIDER_CONF: - Shall be set to either 0,2,4,8,16 - When set to either 2,4,8,16, the 1Hhz calendar is supported - When set to 0, the user sets its own configuration Define IO capabilities When set, this resets some hw resources to set the device in the same state than the power up The FW resets only register that may prevent the FW to run properly This shall be set to 0 in a final product When set, this resets some hw resources to set the device in the same state than the power up The FW resets only register that may prevent the FW to run properly This shall be set to 0 in a final product When set, this resets some hw resources to set the device in the same state than the power up The FW resets only register that may prevent the FW to run properly This shall be set to 0 in a final product Enable or disable traces in the BLE services Enable or disable traces in the BLE services. CFG_HW_USART1_ENABLED and or CFG_HW_LPUART1_ENABLED must be set as well as DBG_TRACE_UART_CFG When set to 1, the traces are Enable in the BLE services Enable or disable traces in application Enable or disable traces traces in application. CFG_HW_USART1_ENABLED and or CFG_HW_LPUART1_ENABLED must be set as well as CFG_DEBUG_TRACE_UART Enable or disable traces in application Enable or disable light traces in the THREAD and ZIGBEE services. CFG_HW_USART1_ENABLED and or CFG_HW_LPUART1_ENABLED must be set as well as CFG_DEBUG_TRACE_UART. In Zigbee applications, it forces the network mode to Centralized and the device role to Sleepy End Device, and a Sleepy End Device has to enable this full low power parameter. Enable or disable light traces in the THREAD services Low Power mode: When set to 1, the low power mode is Enable When set to 0, the device stays in RUN mode Low Power mode: When set to 1, the low power mode is Enable When set to 0, the device stays in RUN mode Enable or disable debugger, default value set to 1 Enable or disable debugger, disabled because CFG_FULL_LOW_POWER is enabled. Needs Sys Debug to be enabled as well. Enable or disable traces in the THREAD and Zigbee services Enable or disable debug traces in the THREAD and Zigbee services. CFG_HW_USART1_ENABLED and or CFG_HW_LPUART1_ENABLED must be set as well as CFG_DEBUG_TRACE_UART Disabled because CFG_FULL_LOW_POWER is enabled Enable or disable debug traces in the THREAD and Zigbee services. CFG_HW_USART1_ENABLED and or CFG_HW_LPUART1_ENABLED must be set as well as CFG_DEBUG_TRACE_UART Disabled because CFG_FULL_LOW_POWER is enabled Enable or disable debug traces in the THREAD and Zigbee services Enable or disable light traces Enable or disable light traces. CFG_HW_USART1_ENABLED and or CFG_HW_LPUART1_ENABLED must be set as well as CFG_DEBUG_TRACE_UART Enable or disable full traces Enable or disable full traces. CFG_HW_USART1_ENABLED and or CFG_HW_LPUART1_ENABLED must be set as well as CFG_DEBUG_TRACE_UART This setting shall be set to '1' if the device needs to support the Peripheral Role. In the MS configuration, both BLE_CFG_PERIPHERAL and BLE_CFG_CENTRAL shall be set to '1 This setting shall be set to '1' if the device needs to support the Peripheral Role. In the MS configuration, both BLE_CFG_PERIPHERAL and BLE_CFG_CENTRAL shall be set to '1 This setting shall be set to '1' if the device needs to support the Peripheral Role. In the MS configuration, both BLE_CFG_PERIPHERAL and BLE_CFG_CENTRAL shall be set to '1 This setting shall be set to '1' if the device needs to support the Central Role. In the MS configuration, both BLE_CFG_PERIPHERAL and BLE_CFG_CENTRAL shall be set to '1 This setting shall be set to '1' if the device needs to support the Central Role. In the MS configuration, both BLE_CFG_PERIPHERAL and BLE_CFG_CENTRAL shall be set to '1 This setting shall be set to '1' if the device needs to support the Central Role. In the MS configuration, both BLE_CFG_PERIPHERAL and BLE_CFG_CENTRAL shall be set to '1 Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) Device information ServiceOption: Supported(1) or Not Supported(0) BODY SENSOR LOCATION CHARACTERISTIC BODY SENSOR LOCATION CHARACTERISTIC ENERGY EXTENDED INFO FLAG ENERGY EXTENDED INFO FLAG Max number of RR interval values - Shall not be greater than 9 Max number of RR interval values - Shall not be greater than 9 Intermediate Temperature characteristic Intermediate Temperature characteristic Measurement Interval characteristic Measurement Interval characteristic Measurement Interval characteristicIndicate property Measurement Interval characteristicIndicate property Measurement Interval characteristicWrite property Measurement Interval characteristicWrite property Time Stamp Info Flag Time Stamp Info Flag Min Interval Value supported Min Interval Value supported Max Interval Value supported Max Interval Value supported Measurement Status info flag Measurement Status info flag Pulse Rate info flag Pulse Rate info flag User ID info flag User ID info flag Time Stamp Info Flag Time Stamp Info Flag Intermediate Cuff Pressure characteristic Intermediate Cuff Pressure characteristic Blood Pressure Feature characteristic Blood Pressure Feature characteristic Lower Pulse Rate supported Lower Pulse Rate supported Upper Pulse Rate supported Upper Pulse Rate supported Upper Pulse Rate supported Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE Enable or Disable traces from BLE The user may define the maximum number of virtual timers supported. It shall not exceed 255 The user may define the priority in the NVIC of the RTC_WKUP interrupt handler that is used to manage the wakeup timer. This setting is the preemptpriority part of the NVIC. The user may define the priority in the NVIC of the RTC_WKUP interrupt handler that is used to manage the wakeup timer. This setting is the subpriority part of the NVIC. It does not exist on all processors. When it is not supported on the CPU, the setting is ignored Define a critical section in the Timer server The Timer server does not support the API to be nested The Application shall either: a) Ensure this will never happen b) Define the critical section The default implementations is masking all interrupts using the PRIMASK bit The TimerServer driver uses critical sections to avoid context corruption. This is achieved with the macro TIMER_ENTER_CRITICAL_SECTION and TIMER_EXIT_CRITICAL_SECTION. When CFG_HW_TS_USE_PRIMASK_AS_CRITICAL_SECTION is set to 1, all STM32 interrupts are masked with the PRIMASK bit of the CortexM CPU. It is possible to use the BASEPRI register of the CortexM CPU to keep allowed some interrupts with high priority. In that case, the user shall re-implement TIMER_ENTER_CRITICAL_SECTION and TIMER_EXIT_CRITICAL_SECTION and shall make sure that no TimerServer API are called when the TIMER critical section is entered This value shall reflect the maximum delay there could be in the application between the time the RTC interrupt is generated by the Hardware and the time when the RTC interrupt handler is called. This time is measured in number of RTCCLK ticks. A relaxed timing would be 10ms When the value is too short, the timerserver will not be able to count properly and all timeout may be random. When the value is too long, the device may wake up more often than the most optimal configuration. However, the impact on power consumption would be marginal (unless the value selected is extremely too long). It is strongly recommended to select a value large enough to make sure it is not too short to ensure reliability of the system as this will have marginal impact on low power mode Interrupt ID in the NVIC of the RTC Wakeup interrupt handler It shall be type of IRQn_Type Enable or Disable LPUART1 (LPUART1 Mode must be set to Asynchronous with Hardware Flow Control set to CTS only) Please ensure that in ProjectManager Advanced Settings panel MX_LPUART1_UART_Init Not Generate Function call is ticked and that Vibility is unticked Enable or Disable LPUART1. This specific HW configuration is available only if LPUART1 is available and configured by CubeMX user interface. LPUART1 Mode must be set to Asynchronous with Hardware Flow Control set to CTS only Enable or Disable LPUART1 DMA TX To enable LPUART1 DMA TX, CFG_HW_LPUART1_ENABLED shall be enabled when available & you need to add relevant DMA request in LPUART1 DMA Settings panel Enable or Disable traces USART1 (USART1 Mode must be set to Asynchronous with Hardware Flow Control set to CTS only) Please ensure that in ProjectManager Advanced Settings panel MX_USART1_UART_Init Not Generate Function call is ticked and that Vibility is unticked Enable or Disable traces USART1. This specific HW configuration is available only if USART1 is configured by CubeMX user interface. USART1 Mode must be set to Asynchronous with Hardware Flow Control set to CTS only. Enable or Disable USART1 DMA TX To enable USART1 DMA TX, CFG_HW_USART1_ENABLED shall be enabled & you need to add relevant DMA request in USART1 DMA Settings panel List of advertising types, can be: - Undirected scannable and connectable(ADV_IND 0x00) - Directed non scannable(ADV_DIRECT_IND 0x01) - Scannable but non connectable(ADV_SCAN_IND 0x02) - Non connectable and no scan response (ADV_NONCONN_IND 0x03) - Scan response(SCAN_RSP 0x03) List of application types, can be: - Transparent mode - Server profile - Client profile - Router profile List of advertising types, can be: - Public address(PUBLIC_ADDR 0) - Random address (RANDOM_ADDR 1) - Resolvable private address (RESOLVABLE_PRIVATE_ADDR 2) - Non resolvable private address(NON_RESOLVABLE_PRIVATE_ADDR 3) List of application types, can be: - Transparent mode - Server profile - Client profile - Router profile Advertising policy for filtering (white list related), can be: - Process scan and connection requests from all devices, i.e. the White List is not in use.(NO_WHITE_LIST_USE 0x00) - Process connection requests from all devices and only scan requests from devices that are in the White List.(WHITE_LIST_FOR_ONLY_SCAN 0x01) - Process scan requests from all devices and only connection requests from devices that are in the White List (WHITE_LIST_FOR_ONLY_CONN 0x02) - Process scan and connection requests only from devices in the White List.(WHITE_LIST_FOR_ALL 0x03) List of application types, can be: - Transparent mode - Server profile - Client profile - Router profile Device name; default value is TEMPLATE Device name lenght; max value is 48bytes, default value is 8 (TEMPLATE length) Number of services; maximum is 5 Number of services; maximum is 5 Please enter a Service Long Name WARNING: this name must : - not start with "Please" - not be empty - contain only "a to z", "A to Z", "0 to 9" and "_" characters Please enter a Service Short Name WARNING: this name must : - not start with "Please" - not be empty - contain only "a to z", "A to Z", "0 to 9" and "_" characters Please enter a Service Characteristic Long Name WARNING: this name must : - not start with "Please" - not be empty - contain only "a to z", "A to Z", "0 to 9" and "_" characters Please enter a Service Characteristic Short Name WARNING: this name must : - not start with "Please" - not be empty - contain only "a to z", "A to Z", "0 to 9" and "_" characters Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Number of services; maximum is 5 Type of service, either Primary or Secondary Type of service UUID, 0x01 = 16 bits UUID, 0x02 = 128 bits UUID Contains the UUID (only 2 bytes are defined by the user for 16 or 128 bits UUID) Type of characteristic UUID, 0x01 = 16 bits UUID, 0x02 = 128 bits UUID Contains the UUID (only 2 bytes are defined by the user for 16 or 128 bits UUID) Number of bytes to be written or to notify (1 to 247) The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function The offset from which the attribute value has to be updated. Only active when CHAR_PROP_NOTIFY or CHAR_PROP_INDICATE is selected. Used in custom_stm.c aci_gatt_update_char_value function No security Need authentication to read Need authorization to read Link must be encrypted to read Need authentication to write Need authorization to write Link must be encrypted to write Do not notify events The application will be notified when a client writes to this attribute. An @ref EVT_BLUE_GATT_ATTRIBUTE_MODIFIED will be issued. The application will be notified when a write request, a write cmd or a signed write cmd is received by the server for this attribute. An @ref EVT_BLUE_GATT_WRITE_PERMIT_REQ will be issued. The application will be notified when a read request of any type is received for this attribute. An @ref EVT_BLUE_GATT_READ_PERMIT_REQ will be issued. Value depends of the number of characteristics with the property Notify or Indicate Value depends of the number of characteristics (nbOfChar) with the property Notify or Indicate(nbOfDescriptor) Max_Attributes_Records = 1 + 2*nbOfChar + nbOfDescriptor Value depends of the number of characteristics with the property Notify or Indicate Value depends of the number of characteristics (nbOfChar) with the property Notify or Indicate(nbOfDescriptor) Max_Attributes_Records = 1 + 2*nbOfChar + nbOfDescriptor Value depends of the number of characteristics with the property Notify or Indicate Value depends of the number of characteristics (nbOfChar) with the property Notify or Indicate(nbOfDescriptor) Max_Attributes_Records = 1 + 2*nbOfChar + nbOfDescriptor Value depends of the number of characteristics with the property Notify or Indicate Value depends of the number of characteristics (nbOfChar) with the property Notify or Indicate(nbOfDescriptor) Max_Attributes_Records = 1 + 2*nbOfChar + nbOfDescriptor Value depends of the number of characteristics with the property Notify or Indicate Value depends of the number of characteristics (nbOfChar) with the property Notify or Indicate(nbOfDescriptor) Max_Attributes_Records = 1 + 2*nbOfChar + nbOfDescriptor Value depends of the number of characteristics with the property Notify or Indicate Type of characteristic length in ble_defs.h. can be either CHAR_VALUE_LEN_CONSTANT(0x00) or CHAR_VALUE_LEN_VARIABLE(0x01) List of applications types, can be: - Full Thread Device with Command Line Interface(FTD_CLI) - Thread_Coap_GenericFull Thread Device with network configuration(FTD) - Minimal Thread Device with network configuration(MTD) Personal Area Network Identifier (PAN ID): an unsigned 16-bit value that specifies the PAN ID. WARNING!: The PAN ID MUST be different from 0xFFFF value which is reserved for broadcast PAN ID Value range : 0x0 to 0xFFFE 2.4 GHz channel as defined in Section 6.1.2.1 of [IEEE802154] List of Log level for Application, can be: - LOG_LEVEL_NONE (None) - LOG_LEVEL_CRIT (Critical) - LOG_LEVEL_WARN (Warning) - LOG_LEVEL_INFO (Info) - LOG_LEVEL_DEBG (Debug) List of Log level for Application, can be: - LOG_LEVEL_NONE (None) - LOG_LEVEL_CRIT (Critical) - LOG_LEVEL_WARN (Warning) - LOG_LEVEL_INFO (Info) - LOG_LEVEL_DEBG (Debug) Queue length of BLE Event This parameter defines the number of asynchronous events that can be stored in the HCI layer before being reported to the application. When a command is sent to the BLE core coprocessor, the HCI layer is waiting for the event with the Num_HCI_Command_Packets set to 1. The receive queue shall be large enough to store all asynchronous events received in between. When CFG_TL_MOST_EVENT_PAYLOAD_SIZE is set to 27, this allow to store three 255 bytes long asynchronous events between the HCI command and its event. This parameter depends on the value given to CFG_TL_MOST_EVENT_PAYLOAD_SIZE. When the queue size is to small, the system may hang if the queue is full with asynchronous events and the HCI layer is still waiting for a CC/CS event, In that case, the notification TL_BLE_HCI_ToNot() is called to indicate to the application a HCI command did not receive its command event within 30s (Default HCI Timeout). Queue length of BLE Event This parameter defines the number of asynchronous events that can be stored in the HCI layer before being reported to the application. When a command is sent to the BLE core coprocessor, the HCI layer is waiting for the event with the Num_HCI_Command_Packets set to 1. The receive queue shall be large enough to store all asynchronous events received in between. When CFG_TL_MOST_EVENT_PAYLOAD_SIZE is set to 27, this allow to store three 255 bytes long asynchronous events between the HCI command and its event. This parameter depends on the value given to CFG_TL_MOST_EVENT_PAYLOAD_SIZE. When the queue size is to small, the system may hang if the queue is full with asynchronous events and the HCI layer is still waiting for a CC/CS event, In that case, the notification TL_BLE_HCI_ToNot() is called to indicate to the application a HCI command did not receive its command event within 30s (Default HCI Timeout). This parameter should be set to fit most events received by the HCI layer. It defines the buffer size of each element allocated in the queue of received events and can be used to optimize the amount of RAM allocated by the Memory Manager. It should not exceed 255 which is the maximum HCI packet payload size (a greater value is a lost of memory as it will never be used) It shall be at least 4 to receive the command status event in one frame. The default value is set to 27 to allow receiving an event of MTU size in a single buffer. This value maybe reduced * further depending on the application. This parameter should be set to fit most events received by the HCI layer. It defines the buffer size of each element allocated in the queue of received events and can be used to optimize the amount of RAM allocated by the Memory Manager. It should not exceed 255 which is the maximum HCI packet payload size (a greater value is a lost of memory as it will never be used) It shall be at least 4 to receive the command status event in one frame. The default value is set to 27 to allow receiving an event of MTU size in a single buffer. This value maybe reduced * further depending on the application. List of Zigbee application type, can be: - Full Function Device (FFD) - Reduced Function Device with only End Device and Sleepy End Device available for lower energy consumption(RFD) List of Zigbee application type, can be: - Full Function Device (FFD) - Reduced Function Device with only End Device and Sleepy End Device available for lower energy consumption(RFD) Network configuration, can be: - Centralized - Distributed - Touchlink Network configuration, can be: - Centralized - Distributed - Touchlink List of application type, can be: - Coordinator (for FFD application only) - Router (for FFD application only) - End Device - Sleepy End Device List of application type, can be: - Coordinator (for FFD application only) - Router (for FFD application only) - End Device - Sleepy End Device Touchlink device can handle 2 capabilities in RFD application: - Router - End device, which allows Sleepy mode Touchlink device can handle 2 capabilities in RFD application: - Router - End device, which allows Sleepy mode Sleepy mode is available in RFD applications, except in Touchlink mode for router capability. It turns on the low power mode parameters. Sleepy mode is available in RFD applications, except in Touchlink mode for router capability. It turns on the low power mode parameters. Number of endpoints used on one device. At least one endpoint is mandatory for a Zigbee application, and it should not exceed 10. Number of endpoints used on one device. At least one endpoint is mandatory for a Zigbee application, and it should not exceed 10. Network channel should be set between 0 and 26. Network channel should be set between 0 and 26. Endpoint 242 shall be reserved for the Green Power cluster, used in proxy mode with FFD application and not used with RFD application. WARNING: Endpoint IDs shall be unique in one same device. Endpoint 242 shall be reserved for the Green Power cluster, used in proxy mode with FFD application and not used with RFD application. WARNING: Endpoint IDs shall be unique in one same device. Profile of the endpoint, can be: - Home Automation (HA) - Smart Energy (SE) - Zigbee Light Link (ZLL) Profile of the endpoint, can be: - Home Automation (HA) - Smart Energy (SE) - Zigbee Light Link (ZLL) Device description gives a readable information about the application of the device Device description gives a readable information about the application of the device Device description gives a readable information about the application of the device Device description gives a readable information about the application of the device Device description gives a readable information about the application of the device Device description gives a readable information about the application of the device Basic cluster: server mode mandatory for all Zigbee endpoint. Basic cluster: server mode mandatory for all Zigbee endpoint. Identify cluster allows to be in identification mode. - Server receives commands to start and stop identification mode. - Client sends start and stop commands to the server. Identify cluster allows to be in identification mode. - Server receives commands to start and stop identification mode. - Client sends start and stop commands to the server. Alarm cluster configure alarm functionality and send alarm notifications. - Server resides with other clusters which can generate alarm conditions and it sends them to a cluster client. Time server cluster SHALL be set when Alarms server is used. - Client can send user instructions to the server. Alarm cluster configure alarm functionality and send alarm notifications. - Server resides with other clusters which can generate alarm conditions and it sends them to a cluster client. Time server cluster SHALL be set when Alarms server is used. - Client can send user instructions to the server. Time cluster provides a base for real-time application. - Server acts as a time master for the network. It SHALL be set when Alarm server or DRLC client are used. - Client synchronizes itself with the server. Time cluster provides a base for real-time application. - Server acts as a time master for the network. It SHALL be set when Alarm server or DRLC client are used. - Client synchronizes itself with the server. Commissioning cluster allows a commissioning process. - Server responds to a commissioning process and commissions itself into a network. - Client initiates the commissioning of a commissioning server. Commissioning cluster allows a commissioning process. - Server responds to a commissioning process and commissions itself into a network. - Client initiates the commissioning of a commissioning server. Groups cluster manages group addressing. - Server receives configuration commands regarding to the local group table. - Client sends commands to configure the group table. Groups cluster manages group addressing. - Server receives configuration commands regarding to the local group table. - Client sends commands to configure the group table. Scenes cluster allows to configure a set of stored values to create recalling scenes. - Server receives commands to configure scenes. - Client controls the configuration of the scenes. Scenes cluster allows to configure a set of stored values to create recalling scenes. - Server receives commands to configure scenes. - Client controls the configuration of the scenes. Occupancy Sensing cluster provides an interface to an occupancy sensor. - Server receives commands to configure the sensor and reports to the client. - Client sends commands to configure the sensor and receives report from the sensor. Occupancy Sensing cluster provides an interface to an occupancy sensor. - Server receives commands to configure the sensor and reports to the client. - Client sends commands to configure the sensor and receives report from the sensor. Diagnostic cluster informs about the operation of the stack over time and will be used by multiple profiles. As a result it should not be set alone. - Server provides diagnostic data. Attributes are strongly recommended to be stored in persistent memory. - Client sends requests to access diagnostic data. Diagnostic cluster informs about the operation of the stack over time and will be used by multiple profiles. As a result it should not be set alone. - Server provides diagnostic data. Attributes are strongly recommended to be stored in persistent memory. - Client sends requests to access diagnostic data. Poll Control cluster provides a mechanism for the management of a Zigbee End Device's polling mode.It defines the poll interval between (normal or fast) two MAC Data Requests from the ZED to its parent router. - Server sets the polling mode to Normal (long poll interval) or Fast (short poll interval) after periodically checking the client. - Client decides the polling mode to be selected. Poll Control cluster provides a mechanism for the management of a Zigbee End Device's polling mode.It defines the poll interval between (normal or fast) two MAC Data Requests from the ZED to its parent router. - Server sets the polling mode to Normal (long poll interval) or Fast (short poll interval) after periodically checking the client. - Client decides the polling mode to be selected. Power Configuration cluster provides information about the power source and voltage alarms to be configured. - Server receives commands to set its power configuration. - Client sends commands to set the power configuration on a remote device. Power Configuration cluster provides information about the power source and voltage alarms to be configured. - Server receives commands to set its power configuration. - Client sends commands to set the power configuration on a remote device. Power Profile cluster indicates the expected power profile to a controller. - Server provides the local power profile. - Client receives the power profile. Power Profile cluster indicates the expected power profile to a controller. - Server provides the local power profile. - Client receives the power profile. RSSI Location cluster allows exchanges of Received Signal Strength Indication information. - Server requests RSSI information and report RSSI measurement. - Client answers to the server requests and reports. RSSI Location cluster allows exchanges of Received Signal Strength Indication information. - Server requests RSSI information and report RSSI measurement. - Client answers to the server requests and reports. Pressure Measurement cluster provides an interface to configure and control pressure measurement. - Server measures the pressure. - Client configures the server and receives measurements from it. Pressure Measurement cluster provides an interface to configure and control pressure measurement. - Server measures the pressure. - Client configures the server and receives measurements from it. Device Temperature Configuration cluster measures internal temperature and configures temperature alarms. - Server receives commands to access internal temperature data. - Client sends commands to access the internal temperature. Device Temperature Configuration cluster measures internal temperature and configures temperature alarms. - Server receives commands to access internal temperature data. - Client sends commands to access the internal temperature. Temperature Measurement cluster provides an interface to configure and control temperature measurements. - Server measures the temperature. - Client configures the server and receives measurements from it. Temperature Measurement cluster provides an interface to configure and control temperature measurements. - Server measures the temperature. - Client configures the server and receives measurements from it. Thermostat cluster provides an interface to configure and control a thermostat. - Server configures the thermostat. - Client controls the functionalities of the thermostat. Thermostat cluster provides an interface to configure and control a thermostat. - Server configures the thermostat. - Client controls the functionalities of the thermostat. Thermostat UI Configuration cluster provides an interface to configure the user interface of a thermostat. - Server configures the thermostat UI. - Client controls the functionalities of the thermostat UI. Thermostat UI Configuration cluster provides an interface to configure the user interface of a thermostat. - Server configures the thermostat UI. - Client controls the functionalities of the thermostat UI. Meter Identification cluster determines advanced information about utility metering device. - Server provides information. - Client sends requests to the server for information. Meter Identification cluster determines advanced information about utility metering device. - Server provides information. - Client sends requests to the server for information. Electrical Measurement cluster provides an interface to configure and control electrical measurements. - Server makes the electrical measurements. - Client configures the server and receives measurements from it. Electrical Measurement cluster provides an interface to configure and control electrical measurements. - Server makes the electrical measurements. - Client configures the server and receives measurements from it. Fan Control cluster controls the speed and state of a fan. - Server configures the speed or state of the fan. - Client commands the server to set the speed or state of the fan. Fan Control cluster controls the speed and state of a fan. - Server configures the speed or state of the fan. - Client commands the server to set the speed or state of the fan. Pump Configuration and Control cluster provides an interface to configure and control pump devices (control of speed not included). - Server configures the pump. - Client controls the functionalities of the pump. Pump Configuration and Control cluster provides an interface to configure and control pump devices (control of speed not included). - Server configures the pump. - Client controls the functionalities of the pump. Relative Humidity Measurement cluster provides an interface to configure and control humidity measurements. - Server measures the humidity. - Client configures the server and receives measurements from it. Relative Humidity Measurement cluster provides an interface to configure and control humidity measurements. - Server measures the humidity. - Client configures the server and receives measurements from it. On/Off cluster provides functionality to switch a device between On and Off states. - Server receives commands to change the state. Server mode SHALL be set if Level Control cluster OR if Color Control are in server mode. - Client sends commands to request a change of state. On/Off cluster provides functionality to switch a device between On and Off states. - Server receives commands to change the state. Server mode SHALL be set if Level Control cluster OR if Color Control are in server mode. - Client sends commands to request a change of state. Color Control cluster controls the color of a light. - Server receives commands to change the color of the light. - Client sends commands to change the color of the remote light. Color Control cluster controls the color of a light. - Server receives commands to change the color of the light. - Client sends commands to change the color of the remote light. Illuminance Level Sensing cluster provides an interface to configure and control level of illumination watch. - Server senses the level of illumination. - Client configures and gets the notifications from the server. Illuminance Level Sensing cluster provides an interface to configure and control level of illumination watch. - Server senses the level of illumination. - Client configures and gets the notifications from the server. Illuminance Measurement cluster provides an interface to configure and control illuminance measurements. - Server measures the illuminance and report to the client. - Client configures the server and control receives measurements from it. Illuminance Measurement cluster provides an interface to configure and control illuminance measurements. - Server measures the illuminance and report to the client. - Client configures the server and control receives measurements from it. Level Control cluster controls the level of a characteristic value of a device. - Server receives commands to change the level of characteristic values. OnOff server SHALL be set when Level Control server is used. - Client sends commands to change the level of characteristic values. Level Control cluster controls the level of a characteristic value of a device. - Server receives commands to change the level of characteristic values. OnOff server SHALL be set when Level Control server is used. - Client sends commands to change the level of characteristic values. On/Off Switch Configuration cluster provides the switch type on a device. - Server receives commands to define a switch configuration. - Client sends commands to define a switch configuration. On/Off Switch Configuration cluster provides the switch type on a device. - Server receives commands to define a switch configuration. - Client sends commands to define a switch configuration. Door Lock cluster provides an interface to configure and control generic values of door locks and doors. - Server sets the values representing door security. - Client controls the door lock and the door. Door Lock cluster provides an interface to configure and control generic values of door locks and doors. - Server sets the values representing door security. - Client controls the door lock and the door. Window Covering cluster provides an interface to configure and control window coverings. - Server sets the values of the window covering. - Client controls the window covering. Window Covering cluster provides an interface to configure and control window coverings. - Server sets the values of the window covering. - Client controls the window covering. IAS ACE cluster provides an interface to configure and control a Control and Indicating Equipment (CIE) in an Intruder Alarm System (IAS). - Server receives commands to configure the CIE. - Client sends commands to configure and control the CIE. IAS ACE cluster provides an interface to configure and control a Control and Indicating Equipment (CIE) in an Intruder Alarm System (IAS). - Server receives commands to configure the CIE. - Client sends commands to configure and control the CIE. IAS WD cluster provides an interface to configure and control a Warning Device (WD) in an Intruder Alarm System (IAS). - Server receives commands to configure the WD and report to the client. - Client sends commands to configure and control the WD and receives reports. IAS WD cluster provides an interface to configure and control a Warning Device (WD) in an Intruder Alarm System (IAS). - Server receives commands to configure the WD and report to the client. - Client sends commands to configure and control the WD and receives reports. IAS Zone cluster provides an interface to configure and control an IAS security zone device. - Server receives commands to configure the IAS Zone device and report to the client. - Client sends commands to configure and control the IAS Zone device and receives reports. IAS Zone cluster provides an interface to configure and control an IAS security zone device. - Server receives commands to configure the IAS Zone device and report to the client. - Client sends commands to configure and control the IAS Zone device and receives reports. Messaging cluster an interface to pass text messages from one device to another. - Server sends the text message. - Client receives the text message. Messaging cluster an interface to pass text messages from one device to another. - Server sends the text message. - Client receives the text message. DRLC cluster provides an interface to the functionality of Demand Response and Load Control. - Server sends the Load Control Events to the devices. - Client receives the Load Control Events. It is time-dependent, therefore a Time server cluster SHALL be set when DRLC client is used. DRLC cluster provides an interface to the functionality of Demand Response and Load Control. - Server sends the Load Control Events to the devices. - Client receives the Load Control Events. It is time-dependent, therefore a Time server cluster SHALL be set when DRLC client is used. Metering cluster provides an interface to obtain usage information from metering devices. - Server gives information. - Client asks for usage information to the server. Metering cluster provides an interface to obtain usage information from metering devices. - Server gives information. - Client asks for usage information to the server. Price cluster provides an interface to communicates pricing information. - Server gives price information. - Client asks for price information to the server. Price cluster provides an interface to communicates pricing information. - Server gives price information. - Client asks for price information to the server. Smart Energy Tunneling cluster provides an interface for tunneling protocols. - Server provides and manages tunnels. - Client requests a tunnel and close it. Smart Energy Tunneling cluster provides an interface for tunneling protocols. - Server provides and manages tunnels. - Client requests a tunnel and close it. Key Establishment cluster is to be used for communication between devices if original network security can not be trusted. - Server initiates the secure communication transaction. - Client responds the secure communication transation. Key Establishment cluster is to be used for communication between devices if original network security can not be trusted. - Server initiates the secure communication transaction. - Client responds the secure communication transation. Dehumidification Control cluster provides an interface to configure an control dehumidification devices. - Server configures the dehumidification device. - Client controls the functionalities of the dehumidification device. Dehumidification Control cluster provides an interface to configure an control dehumidification devices. - Server configures the dehumidification device. - Client controls the functionalities of the dehumidification device. Ballast Configuration cluster provides an interface to configure an control lighting ballasts. - Server receives command to configure the lighting ballasts. - Client sends commands to configure and control lighting ballasts. Ballast Configuration cluster provides an interface to configure an control lighting ballasts. - Server receives command to configure the lighting ballasts. - Client sends commands to configure and control lighting ballasts. Nearest Gateway cluster provides an interface to send nearest gateway information. - Server gives the information of nearest gateway. - Client asks for the nearest gateway. Nearest Gateway cluster provides an interface to send nearest gateway information. - Server gives the information of nearest gateway. - Client asks for the nearest gateway. OTA Upgrade cluster allows to upgrade application software over the air. - Server distributes the software to upgrade. - Client receives the software to update. OTA Upgrade cluster allows to upgrade application software over the air. - Server distributes the software to upgrade. - Client receives the software to update. Voice Over Zigbee cluster allows voice transmition between Zigbee devices. - Server receives the voice message. - Client sends the voice message. Voice Over Zigbee cluster allows voice transmition between Zigbee devices. - Server receives the voice message. - Client sends the voice message. STM32_WPAN_Init STM32_WPAN_Init CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE CHAR_PROP_WRITE_WITHOUT_RESP CHAR_PROP_WRITE CHAR_PROP_NOTIFY CHAR_PROP_INDICATE S_BLE_HOST S_THREAD S_ZIGBEE