SWRU455M February 2017 – October 2020 CC3120 , CC3120MOD , CC3130 , CC3135 , CC3135MOD , CC3220MOD , CC3220MODA , CC3220R , CC3220S , CC3220SF , CC3230S , CC3230SF , CC3235MODAS , CC3235MODASF , CC3235MODS , CC3235MODSF , CC3235S , CC3235SF
After the SimpleLink device has finished confirming a profile, it should send the confirmation result to the provisioning smartphone app. The confirmation result is used to report to the user, whether or not the provisioning process was successful.
When the provisioned SimpleLink device is able to connect to the configured wireless network and acquire an IP address, it advertises itself using broadcast and multicast packets, and waits for the smartphone app to contact it. The smartphone app should connect to the same wireless network that was configured to the provisioned device, discover the device IP address by listening to its broadcasts, and send an HTTP GET request to the device's internal HTTP server to receive the confirmation result.
If the smartphone app can get the confirmation result from the device, it notifies the user that the provisioning process was successful, and on the device side, a successful confirmation result event is sent from the networking subsystem to the host.
If the provisioned device cannot connect to the configured wireless network, or if it is able to connect to the configured wireless network, but the smartphone app did not receive the confirmation result, the profile confirmation fails. When a profile confirmation fails, the confirmation fail reason is sent by the networking subsystem to the host through an event, and the device waits for another profile configuration attempt. At this point, the smartphone app still does not have the confirmation result, because it was not able to find the provisioned device on the wireless network. To get the confirmation result, the smartphone app may disconnect from the configured wireless network and try to directly connect the SimpleLink device AP (possible only if AP-provisioning or AP+SC-provisioning configuration modes are used). If the smartphone app was able to connect to the SimpleLink AP, it sends an HTTP GET request to the device internal HTTP server, to retrieve the confirmation result. If the profile confirmation failed because the device was not able to connect to the wireless network (SSID was not found, WLAN connection failed, or an IP address was not acquired), the smartphone app reports it the user. If the profile confirmation failed because the confirmation result was not delivered to the smartphone (feedback failed), the smartphone app reports to the user that the confirmation was successful, and the networking subsystem sends the host a successful confirmation result event (because the feedback was eventually successfully provided to the user’s smartphone app).