ESP-Now VS core

There's some other good tutorials for it as well, https://randomnerdtutorials.com/?s=esp-now and https://github.com/HarringayMakerSpace/ESP-Now

For power, I'd recommend Li-Ion primary (non-rechargeable) cells, whatever size works best for you. Those have essentially zero internal leakage and a 5 year shelf-life. If you've done it all correctly, it's conceivable it could be 5 years before you need to change the batteries (on top of a 30' ladder). You'd need a small high-efficiency buck converter to drop the 6.8V batteries down to 3.3V for the ESP, with a separate switched 5V linear regulator (one with a SHUTDOWN pin) to power the servos when they need to be driven. The ESP will consume 16-20uA in Deep Sleep, and the buck converter should mostly be off, except for when the ESP wakes every 3.5 hours (maximum Deep Sleep interval). If you're already using ESP-NOW to talk to the vent ESPs, then you could do a 'vent changed' check every time it wakes, otherwise it's more efficient to go back to Sleep quickly and wait until 12-24 hours has elapsed before you fire up a full WiFi connection. Not counting buck inefficiencies and servo movements, the ESP would only consume about 175mAh per year. The batteries will expire before they empty, maybe in 6-7 years.

I presume you've seen Anthony Elder's examples? He got a single ESP to act as hub by restarting it. In a low-traffic environment that'd work. There was discussion and a new PR to speed up the reconnect time using WIFI_RESUME that's been merged in the git repo, which should make a single-ESP hub faster to respond. You'd need a little fault checking in case the BSSID changes of course, but for the normal case things would be faster.

Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.

Replit is the category leader here, but other products in this space include: Glitch, Codesphere, StackBlitz. Coherence fits here as well, with our “Workspaces” Cloud IDE. We’re also the only option where the PaaS is replaced by an Internal Developer Platform.

"TypeScript Swagger Editor" is a web-based TypeScript editor (of StackBlitz) for Swagger API specifications, with SDK (Software Development Kit) library generated by nestia. It generates SDK types, functions and mockup simulator by analyzing content of the input swagger.json file.

Instantly deploy sites with Firebase hosting and integrate seamlessly with GitHub repos. Stackblitz

Use online code editors such as Codesandbox or Stackblitz. They let you focus on writing code rather than dealing with local environment complexities.

Editor de código Stackblitz

I've started learning React and was using stackblitz.com. which is good but I got into some limitations like not being able to upload my own images.

For a few years I have been aware of on-line development environments such as JSBin, JSFiddle and CodePen. They have spearheaded on-line development and more recently a new breed of on-line resources have become available including CodeSandbox, Stackblitz and Replit. You can even access your GitHub repos directly through an in-browser (web) version of MS Visual Studio Code by pressing the full-stop (try it in one of your own repos). Of course there are also cloud offerings from Amazon, Google, Microsoft, etc. but they require a little more configuration and setup than I was happy to incur. Finally, there are two relatively new offerings in this space in the form of GitPod and GitHub Codespaces. I have signed up but not yet explored what they have to offer.