Scribd Logo
Upload

Welcome to Scribd!

  • Potes

    Uploaded by

    hariprathap
    14 views1 page
    This document provides troubleshooting tips for connecting ESP8266 and ESP32 devices to AWS IoT Core. The ESP8266 sketch requires inserting a CA root certificate and acquiring time from an external NTP server, while the ESP32 sketch does not. The ESP8266 sketch also requires specifying the certificate size as a second argument. Care must be taken to correctly format the certificates as they differ between sketches. Incorrect certificate formatting is a common cause of devices connecting but not receiving data. Links to example sketches and modified sketches sending JSON payloads are also provided.

    Original Description:

    Original Title

    potes

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document provides troubleshooting tips for connecting ESP8266 and ESP32 devices to AWS IoT Core. The ESP8266 sketch requires inserting a CA root certificate and acquiring time from an external NTP server, while the ESP32 sketch does not. The ESP8266 sketch also requires specifying the certificate size as a second argument. Care must be taken to correctly format the certificates as they differ between sketches. Incorrect certificate formatting is a common cause of devices connecting but not receiving data. Links to example sketches and modified sketches sending JSON payloads are also provided.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    14 views1 page

    Potes

    Uploaded by

    hariprathap
    This document provides troubleshooting tips for connecting ESP8266 and ESP32 devices to AWS IoT Core. The ESP8266 sketch requires inserting a CA root certificate and acquiring time from an external NTP server, while the ESP32 sketch does not. The ESP8266 sketch also requires specifying the certificate size as a second argument. Care must be taken to correctly format the certificates as they differ between sketches. Incorrect certificate formatting is a common cause of devices connecting but not receiving data. Links to example sketches and modified sketches sending JSON payloads are also provided.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    of 1

    Important Sketch Notes for troubleshooting:

    2. You can use the authors CA Root cert with the ESP8266 sketch but you will need
    to insert
    your own into the ESP32 Sketch
    3. The ESP8266 sketch needs to aquire current time for certificate validity from
    pool.ntp.org,
    however the ESP32 sketch doesnt need to fetch external time
    4. The ESP8266 sketch needs a second argument of
    1.
    6. You can use the originl format for the ESP8266, or use my 'EOF' shortcut
    method.
    7. If you see your device connecting under 'Monitor' in AWS IoT Core but you are
    not getting any
    Data under 'outTopic' than you most likly formatted your certificates
    incorretly.
    ----------------------

    https://github.com/HarringayMakerSpace/awsiot/blob/master/Esp8266AWSIoTExample/
    Esp8266AWSIoTExample.ino
    https://github.com/HarringayMakerSpace/awsiot/blob/master/Esp32AWSIoTExample/
    Esp32AWSIoTExample.ino

    my Modified sketch's with JSON payload to AWS IoT Core

    https://github.com/sborsay/AWS-IoT/blob/master/ESP8266-to-AWSIoT-Modified
    https://github.com/sborsay/AWS-IoT/blob/master/ESP32-to-AWSIoT-modfied
    Replace my certificates with your own three certificates in the sketchs
    2. You can use the authors CA Root cert with the ESP8266 sketch but you will need
    to insert
    your own into the ESP32 Sketch
    3. The ESP8266 sketch needs to aquire current time for certificate validity from
    pool.ntp.org,
    however the ESP32 sketch doesnt need to fetch external time
    4. The ESP8266 sketch needs a second argument of certificate size to set certs
    correctly,
    The ESP32 doesnt need a second argument as it can dynamically configure
    certificate size.
    5. Be very careful configuring your certificates, as they are different for the
    two sketchs
    The specific formats and string vs. char pointers have to be exactly correct.
    6. You can use the originl format for the ESP8266, or use my 'EOF' shortcut
    method.
    7. If you see your device connecting under 'Monitor' in AWS IoT Core but you are
    not getting any
    Data under 'outTopic' than you most likly formatted your certificates
    incorretly.
    ----------------------

    https://github.com/HarringayMakerSpace/awsiot/blob/master/Esp8266AWSIoTExample/
    Esp8266AWSIoTExample.ino
    https://github.com/HarringayMakerSpace/awsiot/blob/master/Esp32AWSIoTExample/
    Esp32AWSIoTExample.ino

    my Modified sketch's with JSON payload to AWS IoT Core

    https://github.com/sborsay/AWS-IoT/blob/master/ESP8266-to-AWSIoT-Modified
    https://github.com/sborsay/AWS-IoT/blob/master/ESP32-to-AWSIoT-modfied

    You might also like