56 lines
2.2 KiB
Org Mode
56 lines
2.2 KiB
Org Mode
#+TITLE: PROJECT: Modular Home Appliances (Universal Literate Note)
|
|
#+ID: project-modular-home-appliances
|
|
#+STARTUP: content
|
|
#+FILETAGS: :hardware:iot:esp32:sustainability:psf:
|
|
|
|
* Overview
|
|
The **Modular Home Appliances** project focuses on developing open-source, sustainable designs for major home appliances (washers, fridges, etc.). It utilizes a modular physical architecture coupled with ESP32-based smart interfaces for AI-driven control and seamless Home Assistant integration.
|
|
|
|
* Phase A: Demand (PRD)
|
|
:PROPERTIES:
|
|
:STATUS: FROZEN
|
|
:END:
|
|
|
|
** 1. Purpose
|
|
Define the requirements for modular, open-source, and intelligent home hardware.
|
|
|
|
** 2. User Needs
|
|
- **Physical Modularity:** Easy replacement and upgrade of mechanical and electrical components.
|
|
- **Smart Interfacing:** ESP32-based control boards for connectivity.
|
|
- **Multimodal Control:** Support for smartphone apps, physical modular controllers, and direct `org-agent` AI interaction.
|
|
- **Sustainability:** Design for longevity, repairability, and efficient power management (inspired by Slate principles).
|
|
|
|
** 3. Success Criteria
|
|
*** TODO Washer/Dryer modular chassis design (draft)
|
|
*** TODO ESP32 firmware specification for appliance state machines
|
|
*** TODO Home Assistant MQTT discovery protocol implementation
|
|
*** TODO Lesson extraction from Slate electric truck architecture
|
|
|
|
* Phase B: Blueprint (PROTOCOL)
|
|
:PROPERTIES:
|
|
:STATUS: SIGNED
|
|
:END:
|
|
|
|
** 1. Architectural Intent
|
|
Interfaces for appliance telemetry and remote actuation. Source of truth is the physical sensors and the Home Assistant state machine.
|
|
|
|
** 2. Semantic Interfaces
|
|
#+begin_src lisp
|
|
(defun appliance-get-telemetry (appliance-id)
|
|
"Queries the MQTT broker for real-time appliance state.")
|
|
|
|
(defun appliance-actuate-program (appliance-id program-id)
|
|
"Sends a command to the ESP32 controller to start a specific cycle.")
|
|
#+end_src
|
|
|
|
* Phase D: Build (Implementation)
|
|
Implementation involves 3D CAD models, circuit designs, and ESP32 firmware (C++/ESP-IDF).
|
|
|
|
** Firmware Logic (Software Component)
|
|
#+begin_src cpp
|
|
// Placeholder for ESP-IDF control logic
|
|
#+end_src
|
|
|
|
* Phase E: Chaos (Verification)
|
|
Verification involves automated cycle testing, Wi-Fi reconnection resilience, and MQTT latency audits.
|