kolergy / IoToTa

Wifi IoT with OTA on GitHub

IoToTa

Wifi IoT with GitHub OTA for the ESP32 this is initially designed for the IoT system of the Artilect Fablab https://artilect.fr/

The ESP32 will connect to wifi then regularely check for new version of the firmware in GitHub, if successfull will perform an OTA update. For security reasons it uses HTTPS & WiFi credentials are not stored in the firmware.

Initially based on https://github.com/programmer131/ESP8266_ESP32_SelfUpdate & some inspiration from https://github.com/SensorsIot/ESP32-OTA

• Adapted to be used with PlatformIO
• Adapted to move the heavy lifting in the OTAtools.cpp & refactored into the OTA class
• Added a scan of the available WiFi networks
• Added a temporary WiFi access point to select the network & set the password.
• Added builtin LED blinking depending of the stat-e of the device
• Added a debug & a silent mode
• Modified to remove the SSID & password from the firmware bin
  • The credentials are stored in the long term memory of the ESP32 (NVS)
  • These will be requested through Serial connection if they are not available
  • So they are never included in the program file available in Github

Usage

Board set-up for OTA

• Partition your board for OAT, this can be done with the Arduino IDE:
  • In tools setup your board & port
  • In tools select the partition scheme: 'minimal SPIFFS (larrge APPS with OTA)'
  • Upload any sketch like blink & your board will be partitionned

Code

• From PlatformIO open the Iotota project (directory cloned by git)
• The '#include "OTAtools.h"' at the start of your sketch link with the OTA functionalities
• The OTA object 'OTA ota = OTA(DEVICENAME, FirmwrVer, FirmwrBin, true);' is created with your settings
• The call 'ota.set();' in your 'setup()' function initiate the OTA functionality
• The call 'ota.check();' in your 'loop()' function will initiate the search for a new firmware every xx seconds

GitHub

• To get started: Fork this repository & try it with your code.
• In the GitHub repository the Data folder holds the firmware number file & the bin file
• Each time you compile a new version push the bin file to the Data folder then increment the version number
• TODO: Automatically push the code on build & increment version

Board builtin led status

• blink @ 1hz -> please connect to a usb serial monitor & input wifi SSID & pass
• blink @ 5hz -> trying to coonect to wifi
• blink fast -> uploading firmware

Errors

Update http Status:

• 200: Success
• 301: Link permanantly moved
• 404: File not found
• 408: Timeout
• 418 I'm a teapot (RFC 2324, RFC 7168) (with IoT one never know what can be on the other end)
• ...
• Global HTTP status list available on Wikipedia:https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Update errors:

• WiFi.status() != WL_CONNECTED -> ESP32 memory not partitionned adequately

WARNING active work ongoing not yet fully stabilised & tested