You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the code of this warehouse for mass production planning. According to the code execution process in the main function, after the esp32 is powered on, it first obtains the certificate stored inside the module and passes it into the network context. It performs the MQTT kernel before WIFI initialization. Initialization. Now I want to connect to WIFI after powering on for the first time, and get the certificate content from HTTP to connect to AWS. How can I put MQTT initialization on the WIFI connection and do it after I get the certificate from HTTP.
The text was updated successfully, but these errors were encountered:
Without changing the demo APIs, one could check if the certificate is available in flash before continuing with the demo. If it is not, then initialize WiFi without starting the CoreMQTT Agent in order to perform the HTTP download, store the received certificate in flash, then restart the device.
If restarting a device would take too long, a device could stop the WiFi after retrieving a certificate in order to start coreMQTT-Agent correctly. A clean app_wifi_stop() function could stop the WiFi connection (but not de-init), then clear the bits in wifi_event_group to re-arm the WiFi connected event.
I am using the code of this warehouse for mass production planning. According to the code execution process in the main function, after the esp32 is powered on, it first obtains the certificate stored inside the module and passes it into the network context. It performs the MQTT kernel before WIFI initialization. Initialization. Now I want to connect to WIFI after powering on for the first time, and get the certificate content from HTTP to connect to AWS. How can I put MQTT initialization on the WIFI connection and do it after I get the certificate from HTTP.
The text was updated successfully, but these errors were encountered: