void-blueprints v0.1.0: Everything Is Open

The Repository Is Live

Today we published void-blueprints — our public repository containing every file you need to build a Void from scratch. CAD source files, exported STLs, ESP32 firmware, wiring diagrams, assembly documentation, and a CI pipeline that packages it all automatically.

This is not a "code dump" open-source release where files get uploaded and forgotten. This is a maintained, versioned, documented repository with tagged releases and automated asset publishing.

What Is in v0.1.0

The first tagged release — v0.1.0, the Golden Ratio Cloche — includes:

CAD Files

• OpenSCAD parametric source for the full dome, split-dome variant, vent caps, base housing, and substrate platform
• Pre-exported STL files ready for slicing and printing
• Golden ratio proportions baked into the parametric constants

ESP32 Firmware

• Arduino-compatible firmware for the ESP32-S3
• BME280 sensor polling for temperature, humidity, and pressure
• PID-tuned humidity control via ultrasonic humidifier
• Scheduled fresh air exchange with configurable intervals
• Ambient LED lighting with species-specific color profiles
• UV-C sterilization cycle with hardware interlock enforcement
• REST API for companion app communication
• WiFi provisioning and local web dashboard

Build Documentation

• Complete bill of materials with component specifications
• Wiring diagrams for all electrical connections
• Step-by-step assembly guide with print settings
• Firmware flashing instructions
• Troubleshooting guide for common issues

Automated Releases

We set up a GitHub Action that triggers on every tagged release. When we push a new version tag, the action automatically:

1. Collects all STL files from the CAD export directory
2. Packages them into the release assets
3. Makes them available as direct downloads from the release page

This means you never have to clone the repo or navigate the file structure to get printable files. Go to the releases page, find the version you want, and download the STLs directly.

Why a Separate Repository

You might notice that void-blueprints is its own repository, separate from the website and the companion app. This is deliberate.

The hardware designs, firmware, and build documentation are the core of the open-source project. They need to be:

• Easy to find — A dedicated repo with a clear name is easier to discover than hardware files buried in a website monorepo
• Easy to fork — Builders who want to modify the dome should not have to clone a Next.js website to get STL files
• Independently versioned — Hardware releases follow their own cadence, separate from website deployments
• Community-friendly — Issues, pull requests, and discussions about the hardware stay focused and organized

The website links to void-blueprints for all downloads, build docs, and firmware references. The companion app references the same firmware API contract. Everything connects, but each piece lives where it makes the most sense.

How to Contribute

The repository is open for contributions under CERN-OHL-P-2.0. Here is how you can help:

Report issues — Found a dimension that is off? A firmware bug? A confusing step in the build guide? Open an issue. Detailed bug reports are one of the most valuable contributions to any open-source project.

Improve documentation — Clearer instructions, better diagrams, additional troubleshooting tips. If you built a Void and something was confusing, help the next builder by improving the docs.

Submit hardware modifications — Designed a new sensor mount? Modified the dome for a specific use case? Created an adapter for a different humidifier? Submit a pull request with your design files and documentation.

Contribute firmware features — The ESP32 firmware has a clean architecture with separate modules for sensors, actuators, control loops, and the API layer. New features — additional sensor support, custom automation routines, new species profiles — are welcome as pull requests.

What This Means for the Community

Open-source hardware only works when the community engages with it. Publishing the files is step one. What happens next depends on builders, growers, and makers who download, print, assemble, and improve the designs.

Every build photo shared on Discord or Reddit helps someone else troubleshoot their own build. Every firmware contribution benefits every grower running that firmware. Every documentation improvement makes the project more accessible to the next newcomer.

The repository is live. The files are ready. The community is forming.

Download the STLs, fork the firmware, and start building. We will be here to help.

Browse the repository at github.com/elastik/void-blueprints or start with the build page for a guided walkthrough.