This is an ACME client for ESP (ESP32, etc) devices, so your IoT can fetch their own certificate for secure communication. ACME is a protocol (see <a href="https://tools.ietf.org/html/rfc8555">RFC8555</a>) for automatic certificate management. Sites such as letsencrypt.org allow you to obtain free (no charge) certificates in an automated way using the ACME protocol. Now also supporting the ARI protocol, to learn about when to renew a certificate. Also works with Google ACME, next to Letsencrypt.
Progressive (SOF2) JPEG decoder for memory-constrained systems. Decodes at 1/1, 1/2, 1/4 or 1/8 in a single forward pass with no seeking, storing only the low-frequency corner of each block that a reduced-scale IDCT will read. Storage still scales with the SOURCE image and not with the output, but with a much smaller constant than a general-purpose decoder: on a 12 MP 4:2:0 progressive file the peak is 23.0 / 8.9 / 3.6 MB at 1/2 / 1/4 / 1/8, against libjpeg-turbo's ~36 MB coefficient array at every scale. Size the budget from the frame header, not from the output you want; PSRAM is the assumption at megapixel sizes. Portable C99; I/O, row output and allocation are caller callbacks, so the large buffers can be pointed at external RAM while the hot working state stays internal.
iotta codec-board audio IO — ES8311 DAC + ES7210 mic-array ADC over a shared full-duplex I2S bus (esp_codec_dev). Optional Build-B voice backend for the iotta device SDK; wire via Esp32Platform::set_audio().
iotta device SDK — ESP-IDF binding. Runs the portable iotta core (session/protocol state machine, provisioning, MCP, audio pipeline, OTA) on ESP32-S3 by implementing the PAL with ESP-IDF APIs: control plane, voice over I2S, and A/B OTA. Add this component and wire it from your app's app_main (see example/ and sdk/docs/PORTING_NEW_CHIPSET.md).