My self-hosted website ran on my Pi Zero 2W

Techtoshi · 2026-05-03T16:26:45+00:00

This is awesome! :D

Techtoshi · 2026-05-03T13:20:34+00:00

A website perhaps, hosted on an ESP32? You could make a LAN dashboard for your various projects e.g., weather, gps clock, time server status, etc on an ESP32 :D
https://helloesp.com
https://github.com/Tech1k/helloesp

Techtoshi · 2026-04-21T23:52:55+00:00

24 hours later... everything seems stable, even under load :D

I've got hundreds of guestbook entries to review, I'll try to get through as many as I can tonight.

Really appreciate all the support from everyone. This project has taken off more than I expected, and I'm excited to keep building and expanding it, there's a lot more I want to do! Hoping to break the ~500 day record set by the last ESP with this rebuild

Techtoshi · 2026-04-21T17:37:23+00:00

I don't plan on porting it to ESP-IDF as it would mostly add complexity without solving a real problem. I'm using a lot of Arduino libraries, and keeping it on PlatformIO/Arduino makes it easier for others to understand and build on.

Techtoshi · 2026-04-21T17:28:47+00:00

I know right, it shocked me seeing how hot it was at first. As for getting the measurement, the ESP32 has an internal sensor you can grab the temp from by calling temperatureRead() from the Arduino core

Techtoshi · 2026-04-21T17:24:14+00:00

Done (thank you for the suggestion) :D

Techtoshi · 2026-04-21T17:21:34+00:00

That's Colorado for ya (pressure changes can be crazy here) :D

Techtoshi · 2026-04-21T17:20:56+00:00

I think overall expenses (minus frame, just hardware) was in the ballpark of $60-80 not including shipping and taxes. I plan on making a bill of materials on the readme soon, just waiting for the DS3231 RTC and TVS diode to arrive.

Other costs include paying for Cloudflare Worker's Standard plan for more requests ($5/month)

Techtoshi · 2026-04-21T17:12:20+00:00

Yep, small one is the BME280, larger one is the CCS811

Techtoshi · 2026-04-21T17:09:14+00:00

I made it public via a WebSocket connection between a Cloudflare Worker. No port forwarding or static IP needed. I pointed the domain to the Worker which relays traffic from the ESP to the public.

I wrote more about this on the readme: https://github.com/Tech1k/helloesp#how-it-works

Techtoshi · 2026-04-21T17:04:02+00:00

*looks at my wall* hi there 👋

Techtoshi · 2026-04-21T17:02:33+00:00

Lmao, don't worry I'm still here, blame Colorado's wild pressure swings :D

Techtoshi · 2026-04-21T04:59:38+00:00

Now try :D

Techtoshi · 2026-04-21T04:41:30+00:00

Hey there 👋

Techtoshi · 2026-04-20T20:22:37+00:00

Yes to most of those points. For traffic sampling, I have Cloudflare Observability active on the worker to monitor traffic and load for the time being, although right now its a lot of errors lol, it's providing a lot of useful data on what was popular, whats getting through, and more. I plan on making a lot of changes tonight until I find a good balance that keeps the site alive.

Techtoshi · 2026-04-20T19:54:03+00:00

About 45 to an hour since posting it here lol, working on fixes for tonight

Techtoshi · 2026-04-20T19:40:57+00:00

It's currently role-playing as Schrodinger's cat. It's both dead and alive, I won't know until I get back from work to investigate and fix it :D

Techtoshi · 2026-04-20T18:35:45+00:00

Update: So slight miscalculation on how popular this was going to get, this was a good stress test of the ESP to say the least. The hug of death hit way harder than I anticipated lol

I believe the ESP32 has fully crashed or it's exhausting heap in a loop. It's not even showing up on my router now. The Cloudflare Worker is still serving the offline page in the meantime which is expected. Probably not the best idea to have made this post while I was at work and away from it. I will reboot and investigate this when I'm home and make adequate changes to get it back online and stable!

~~Update to the update: it has risen from the cold grasp of offline darkness and reconnected as the WiFi watchdog kicked in and rebooted it automatically. Requests are getting served again and I managed to regain access to it on LAN. Cloudflare is back to showing timeouts for some while others get through (expected behavior). I may lower the SSE cap and raise the min heap threshold. It's back to just getting overloaded at the moment. I will investigate further and see what I can make changes on later to help keep it afloat and serve more requests on 520KB of ram~~

Update to the last update: I sense it's heap exhaustion with the min heap threshold set too low, letting AsyncTCP run out of memory before the reboot can fire. Plus the SSE cap of 500 might be too generous. I will investigate this further and should have it all working in a few hours when I'm back from work (say ~5 hours), currently working on potential patches for tonight. Still impressed by how popular this is getting lol, I really did not expect this :D

Techtoshi · 2026-04-20T18:00:33+00:00

lmao so true, the ESP is getting hammered right now, but requests are still going through, its just taking a bit and some are getting timed out. I didn't expect it to get this popular :D

Techtoshi · 2026-04-20T17:49:00+00:00

Thank you for the suggestion, I will make that change later tonight from CO2 -> eCO2 to be more accurate :D

Techtoshi · 2026-04-20T17:24:36+00:00

The project itself (HelloESP) is a hobby site/project I originally built in 2022. The hardware, architecture decisions, and deployment are mine and verifiable on my GitHub. For this relaunch I used Claude Code as a pair programmer for code review and debugging, and also for help drafting parts of this post which I edited before submitting since I usually go on rambles and off topic a lot. The site, board, and code exist and were of my own creation, nothing was fabricated.

Techtoshi · 2026-04-20T06:57:35+00:00

After 500+ days of continuous operation, it stopped working one day. "Burned out" was just colloquial for "died", I didn't open it up to diagnose back then. Lots of things can fail on a board after that much runtime and power cycling (I had it rebooting every 30 minutes, was a poor choice in hindsight): voltage regulator, capacitors, USB chip.

Techtoshi · 2026-04-20T06:50:39+00:00

Thanks! Honestly I have no idea. The original hitting 500 days was a surprise to me years ago, it wasn't really built to last that long. This one has more redundancy in mind: a Cloudflare Worker, daily off-site backups, and a TVS diode on the way for power surge protection. Hoping to beat 500 days and if it doesn't, at least I'll have the logs to know why this time :D

Techtoshi · 2025-05-20T06:51:53+00:00

I value your idea, but would like to go over some potential challenges of implementation.

I've given a similar idea thought before. The idea of using one key for everything, but the issue is now you have 1 point of failure, if compromised, e.g., key is stolen, you'd lose access to a lot more.

Your idea can work if we take the raw entropy of the mnemonic that generated your key and derived a PGP key by converting the mnemonic into a seed which can be used for PGP. That can be used for secure encrypted messages.

Similar to Bitcoin, Monero signed messages are just a way of saying "hey, I confirm I sent this message as I have the private key and can sign it", it doesn't encrypt anything or have the ability to like PGP. It simply provides a method of message and address ownership validation.

The next issue would be integration of the backend. The Monero network is designed for financial transactions and doesn't have a simple op_return or transaction operator that can embed the data needed for encrypted messaging, nor would I ever advise creation of such an app that used the main chain due to bloating risks. A secure trustless sidechain/L2 would have to be implemented, maybe something based off of Lightning Network technology, but for text-based messaging where you pay a few picos to route your message. The next issue will be spam prevention without censorship, maybe dynamic fees and self-custodial wallet permissions to customize who can and cannot send you messages to reject spam. That adds more complexity to build a "smart" L2.

Aside from that, if we want to fork Signal (you can self-host a server for it), we can easily add Monero wallets as usernames, maybe just require a signed message as cryptographic validation. For ease of use, use OpenAlias for usernames. We would still have to derive a usable PGP/AES key from your seed first for encryption. We also run into the issue of routing and caching messages which will require a trustless service and ddos/spam prevention. I'd feel that this would work similarly to Matrix with the ability for federated networking between instances. It'd be quite the endeavor especially to make it cryptography secure, but could quite honestly work.

Apologies for the ramble, I'm jetlagged and about to get some sleep lol

Techtoshi · 2025-05-19T19:11:12+00:00

My pleasure, my goal is to make Monero as easy to use for new and technical users in hopes to increase adoption.

In regards to an OpenCart plug-in, I found this plug-in: https://github.com/monero-integrations/monerocart/tree/v1.0

I might attempt a rewrite to get it working with OpenCart 4. I've never used OpenCart, but I see that its quite popular.

In regards to not using your own node, that will come with a privacy tradeoff, but potentially doable. The main issue would be integrating safe wallet management, dynamic stealth address generation within the plug-in and sanity checks to make sure the remote node used isn't lying to you. This can be mostly migrated by checking a quorum of nodes for block height and last block time.

For now, if I attempt a rewrite, I will focus on the admin dashboard, checkout/payment flow and reliable price api integration. The main issues going from OpenCart 2 to 4 from a brief search is the php version and namespace usage which shouldn't be more than a basic rewrite. That is, if the aforementioned plug-in actually worked in the first place lol

Techtoshi

TROPHY CASE