I’m the developer behind Pinscope. I have always found TLS’s memory footprint to be a challenge when working with the ESP32, making it nearly impossible to integrate TLS-based remote control in some memory-constrained projects.
That is one of the reasons I built Pinscope. It enables remote access, OTA, crash reports, and debug logs to ESP32 devices behind NAT, using Noise protocol for secure connection with minimal memory footprint. It requires only 9.4KB of RAM and can be integrated in any ESP32 project in just a single line of code.
The client code is public, but it is not open source and the free plan supports up to three devices.
Hi HN!
I’m the developer behind Pinscope. I have always found TLS’s memory footprint to be a challenge when working with the ESP32, making it nearly impossible to integrate TLS-based remote control in some memory-constrained projects.
Demo: https://pinscope.dev/demo
Video: https://www.youtube.com/watch?v=AVuoqsDpeYQ
Source: https://github.com/pinscope-dev/pinscope-esp
That is one of the reasons I built Pinscope. It enables remote access, OTA, crash reports, and debug logs to ESP32 devices behind NAT, using Noise protocol for secure connection with minimal memory footprint. It requires only 9.4KB of RAM and can be integrated in any ESP32 project in just a single line of code.
The client code is public, but it is not open source and the free plan supports up to three devices.
I’d love to hear your feedback!