We developed the RTOS (Real-Time Operating System) for our activity trackers using the Zephyr kernel and its libraries.

In this article, I briefly shared a short summary of my experience of choosing different tech stacks for the firmware development of activity trackers.

Happy Reading!

npm package: https://www.npmjs.com/package/hue-logs-client

updated UI (better look now :) )

thanks for suggesting @yahasolutions. Dozzle looks good, and lightweight too. I will explore more

I feel like this is a finding/experience worth sharing. We ran into battery problem when developing our MVP using esp32 c3 MCU. ESP32 have high current consumption during network calls and we resolved this problem by avoiding TCP protocol in our network calls (Moving away from REST API calls).For Details, I am linking full article here: https://khalsalabs.com/iot-101-minimizing-esp32-wifi-battery...

Hope you all enjoy!

Sat Sri Akaal

yes, I have a static IP and port forwarded. It IP can be mapped to website (dns name) via namecheap and godaddy like services. This is enough to put it on internet

In this setup I added a nginx in between (doesn't enable cache yet) for load balancing.

nope, no CDN. It has NGINX reverse proxy

Its still a single esp32 s2 mini. Its Nginx that is saving this little mcu !!

yes, you got it right its due to that odd message web browsers show for non-https websites. This HTTPS/TLS has been added using nginx on different server, also to support some load. The website is still under lot of traffic, however nginx is doing good on its part.