One of the goals of Hestia32 is to keep the hardware as open as the software. That means more than publishing the source files: it also means giving people meaningful choices when building the device.

The first Hestia32 designs use the Seeed XIAO ESP32-C5. I've now completed the HVAC and EU board designs using a generic 30-pin ESP32-C5 DevKit as well.

https://github.com/MakeOpenStuff/hestia32/tree/develop/pcb

Why support another board?

The XIAO is a good fit for a compact design, but it shouldn't be the only way to build Hestia32.

Some builders may prefer a generic development board, already have one available, or simply want to avoid depending on a particular module. Supporting both approaches makes the project more flexible and gives people another route to building their own thermostat.

Same functionality, different hardware

The generic DevKit variants are intended to offer the same functionality and feature set as their XIAO-based counterparts. The controller board changes, but the goal for the thermostat itself remains the same.

The attached render shows the EU version with the generic 30-pin ESP32-C5 DevKit installed. The HVAC version follows the same approach.

Keeping the project open

For me, open hardware should give people the freedom to inspect, modify, build and maintain a design without unnecessary vendor dependence. Supporting an alternative controller takes additional design work, but it's consistent with that goal.

These DevKit variants won't be included in the upcoming Crowd Supply campaign. I'm still exploring how best to make them available afterwards, potentially as bare boards.

The main crowdfunding campaign remains planned for the primary Hestia32 variants.

You can follow the project and subscribe for launch updates here:

https://www.crowdsupply.com/makeopenstuff/hestia32

More development updates as the hardware and user interface continue to evolve.