Removed Duplicate Certificate Loading. Testing Criteria completed using the same main code, alternating library dependency master vs fork .

MQTT

• Cloud device Parameter Passed to IoTaap MQTT Instance.
• MQTT Subscription & Unsubscription to topics.
• Sending Unique Parameters to MQTT Instance.
• Receiving MQTT Payloads from MQTT Instance.
• Sending Payloads to devices topic & Events on IoTaap Console.

OTA

• Check for auto update forward revisioning to highest version.
• Check for auto update backward revisioning.
• Check for manual update forward revisioning.
• Check for manual update through 20 revisions. Note each runtime.

Notes: Behaviour consistent when only the lines to set certificate removed. When either wifiClientSecure.stop(); lines are removed then unhandled exception occurs in a repeatable way. Thus inability to perform the check update function.

Repeatable behaviour also discovered on hardware reset of connected device to create overflow on the uptime within console.

If uploading the code, and not using sleep function, ESP32 subscribes and publishes to some topic succesfully (MQTT Broker is on Raspberry PI, all debugging is done in serial monitor).

Serial output:

WiFi connected
IP address: 
x
Boot number: 2
Setup ESP32 to sleep for every 5 Seconds
Attempting MQTT connection...connected
Subscribed to esp32/topic
Going to sleep now
ets Jun  8 2016 00:22:57

During normal operation, the device cannot perform an update due to memory issues.

IoTaaP OS version: 3.0.2

Log:

[2021-03-07 02:35:34] [INFO] - Checking for updates
sendRequest code=200
[2021-03-07 02:35:37] [INFO] - New update available!
[2021-03-07 02:35:37] [INFO] - Starting update process...
sendRequest code=200
[E][Updater.cpp:158] begin(): malloc failed
[E][HTTPUpdate.cpp:382] runUpdate(): Update.begin failed! (No Error)

[E][HTTPUpdate.cpp:334] handleUpdate(): Update failed

[2021-03-07 02:35:40] [ERROR] - Update failed with error (0): 

[2021-03-07 02:35:40] [WARNING] - Not connected to MQTT broker
[2021-03-07 02:35:40] [INFO] - Data stored locally!

After few retries, the update will succeed. It looks like a heap issue with the MqttTask or an overall memory issue on a system level (something is consuming a lot of memory at random points). This could be connected with Queue dynamic allocation.

Needs further investigation.

wifiClientSecure.setCACert() is duplicated, now it loads the same certificate (before it was loading MQTT and OTAu certificates separately).

This is maybe redundant since there can be only one wifiClientSecure but now we use the same certificate, this maybe can be removed?

Usage in ota_module.cpp:

https://github.com/iotaap/iotaap-os/blob/2d61943b79f46973b7092c9631eae79d5b77f2e7/src/ota/ota_module.cpp#L51 https://github.com/iotaap/iotaap-os/blob/2d61943b79f46973b7092c9631eae79d5b77f2e7/src/ota/ota_module.cpp#L95

Usage in mqtt_client.cpp:

https://github.com/iotaap/iotaap-os/blob/c7f25e4baecd3dd315aa99160b324582b8073ef3/src/mqtt/mqtt_client.cpp#L184

IoTaaP OS v5.0.0 introduces performance and usability improvements, stability updates, improved web configurator and various bug fixes. This version also intruduces batch data publishing to ensure fast and reliable publishing of high frequency data.

Added

• MQTT Batch implemented
• Support for unsecured MQTT connection (without encryption)
• Subscribing to any topic is now supported
• Backup before reset

Changed

• Using WiFi events instead of basic functional approach
• Certificate is now using dynamic allocation of the memory
• Web configurator imrovements and new fields
• OTA server configuration improvement
• NTP servers are removed, IoTaaP Heartbeat is now used to sync time with server
• MQTT client now accepts IP addres for server
• 3rd party libraries updated
• Task timing optimized
• Configurator internal handling

Fixed

• WiFi password generator bug
• Starting web server dinamically
• Static allocation is replaced by dynamic
• Fixed rebooting issue with local configurator
• High memory usage is now optimized
• Queue is fixed and replaced by native solution
• Timestamp was reseting after restart
• Linked list

[4.0.0] - 2021-03-31

Breaking changes

IoTaaP OS v4.0.0 introduces filesystem changes, bug fixes, various cosmetic changes and performance and usability improvements. Please read the Official IoTaaP OS documentation to catch up easily.

Added

• Implemented remote update trigger for devices
• Implemented remote update trigger for devices in the group
• Added development feature for monitoring free stack in internal tasks (disabled by default)
• Added start() function, which now has to be called at the beginning in order to start IoTaaP OS

Changed

• System will not start unitl start() function is called
• Updated initial code (example)
• Implemented internal FAT filesystem, SD is not mandatory to start the system. If SD is not present, logging and data backup will be disabled
• Removed getUserParameter function. Custom parameters are not supported due to switching to internal FAT FS for configuration (better implementation of custom parameters will be implemented in the future releases)
• CA certificate is now stored on internal filesystem, not on the SD card
• SD card is not mandatory and file structure will be automatically created during the first boot (manual SD flashing is not required anymore)
• Improved system logging and serial output

Fixed

• IoTaaP hostname (during Web Configurator AP) is now generated from device MAC, and it is the same as the SSID
• Fixed resetting synced time if WiFi connection is lost (now it will work with previously synced time)
• Internal tasks performance optimizations

Added

• Added checking and creating FS at startup
• Creating default config file (template) at startup if not present
• Web configurator
• CoC and issue templates to the repository

Changed

• Stack size for WiFi and MQTT tasks
• Queue size for logs and local messages
• Status publishing period (to 5000ms)
• Logging (introduced SYSTEM tag and reduced writing of INFO tag log to SD card)

Fixed

• Showing error message if FS is not available, even if serial debug print is disabled