SWRA513C January   2020  – September 2020 CC3120 , CC3120MOD , CC3135 , CC3135MOD , CC3220MOD , CC3220MODA , CC3220R , CC3220S , CC3220SF , CC3235MODS , CC3235MODSF , CC3235S , CC3235SF

 

  1.   Trademarks
  2. 1Introduction
    1. 1.1 Terminology
  3. 2Overview
    1. 2.1 General Description
  4. 3Provisioning Configuration Modes
    1. 3.1 AP Provisioning
    2. 3.2 SmartConfig Provisioning
    3. 3.3 AP Plus SmartConfig Provisioning
    4. 3.4 AP Plus SmartConfig Plus External Configuration Provisioning
  5. 4Initiating the Provisioning Process
    1. 4.1 Host-Initiated Provisioning
    2. 4.2 Auto-Provisioning
    3. 4.3 Ending the Provisioning Process
  6. 5Profile Confirmation
    1. 5.1 Feedback
      1. 5.1.1 Local Feedback
      2. 5.1.2 External Feedback (Cloud)
    2. 5.2 Confirmation Fail
  7. 6External Configuration
  8. 7Host APIs
    1. 7.1 Provisioning Command
    2. 7.2 Provisioning Status Event
    3. 7.3 Provisioning Profile-Added Event
    4. 7.4 Reset Request Event
    5. 7.5 Blocking APIs During Provisioning
  9. 8Provisioning Use Examples
    1. 8.1 Successful SmartConfig Provisioning
    2. 8.2 Unsuccessful SmartConfig Provisioning
    3. 8.3 Successful SmartConfig Provisioning With AP Fallback
    4. 8.4 Successful AP Provisioning
    5. 8.5 Successful AP Provisioning With Cloud Confirmation
    6. 8.6 Using External Configuration Method: WAC
    7. 8.7 Successful SmartConfig Provisioning While External Configuration Enabled
  10. 9Provisioning HTTP/HTTPS Server APIs
  11.   Revision History

Confirmation Fail

If the SimpleLink Wi-Fi device fails to connect to the configured profile, the device switches back to the configuration stage, and the smartphone provisioning app will not find the device on the local wireless network or the cloud. If the current configuration mode requires that the SimpleLink Wi-Fi device is in the AP role, the smartphone provisioning app may try to directly connect to the device, and then ask for the confirmation result (SSID not found, WLAN connection failed, or IP not acquired).

If the SimpleLink Wi-Fi device successfully connects to the configured profile, but the user’s smartphone provisioning app failed to collect the confirmation result over the local wireless network or the cloud, the device switches back to the configuration stage. If the current configuration mode requires that the SimpleLink Wi-Fi device is in the AP role, the smartphone app may try to directly connect to the AP of the device, and then ask for the confirmation result. If the smartphone app can connect the device and asks for the confirmation result (which is connection successful, feedback failed) the device answers with the confirmation success result, because the feedback was eventually successfully delivered to the user (although it was in the configuration stage instead of the confirmation stage), and the provisioning process will successfully end. In addition, the device switches to the role that it was requested to switch to if successful in provisioning. If the device is in STA role, it also automatically connects to the new added profile.

Profiles that were configured during the configuration stage are not deleted in case of a failed confirmation.