Project · Edge systems
DEF: modular firmware for ESP32
Domus Edge Framework is a modular framework for building firmware for embedded devices, based on ESP32 and ESP-IDF/C++. It targets home automation, robotics, and systems that connect software with the physical world.
- Application
- Home automation and robotics
- Platform baseline
- ESP32 · ESP-IDF/C++
Status and resources
Active exploration
What this page does not publish
- Demo
- Not authorized
- Firmware or downloads
- Not authorized
- Source code
- Private · not published
- Availability
- No public service or hardware
Do not start every device from scratch
A sensor, home controller, or robot needs more than reading a pin: orderly startup, persistent configuration, event coordination, and separation between product logic and its board. Repeating those pieces in each firmware makes hardware changes and multiple applications harder to maintain. DEF aims to turn them into a reusable shared foundation.
Shared Core, separate integrations
Core organizes lifecycle, events, and configuration and storage interfaces. Communications and platform capabilities connect through defined contracts, without mixing drivers or board details into application decisions. The intended baseline is ESP-IDF/C++; Arduino is neither a base dependency nor compatibility promised by this page.
From an idea to a device
For a home controller, for example, the application can be organized around readings, decisions, and actions; the shared foundation coordinates lifecycle and configuration. The goal is to reuse those pieces when the product changes instead of rebuilding the whole firmware structure. This is an illustrative scenario, not a published demo or a certified sensor integration.
Available evidence
Core has an implementation and host tests for lifecycle, events, and configuration/storage. The owner documented a consumer build with a generic ESP32 profile; that build does not establish working hardware on a particular board. The development console is local and fail-closed: it is not a production protocol or a public demo.
Scope and evolution
Drivers, physical control, secure connectivity, and firmware updates require their own integrations and validation. A planned module is not a ready capability. Source remains private, with no downloadable firmware or public hardware; each board needs specific evidence before support is declared.