memex/notes/project-modular-home-appliances.org

PROJECT: Modular Home Appliances (Universal Literate Note)

• Overview
• Phase A: Demand (PRD)
  • 1. Purpose
  • 2. User Needs
  • 3. Success Criteria
    • Washer/Dryer modular chassis design (draft)
    • ESP32 firmware specification for appliance state machines
    • Home Assistant MQTT discovery protocol implementation
    • Lesson extraction from Slate electric truck architecture
• Phase B: Blueprint (PROTOCOL)
  • 1. Architectural Intent
  • 2. Semantic Interfaces
• Phase D: Build (Implementation)
  • Firmware Logic (Software Component)
• Phase E: Chaos (Verification)

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)

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 `opencortex` 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)

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

(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.")

Phase D: Build (Implementation)

Implementation involves 3D CAD models, circuit designs, and ESP32 firmware (C++/ESP-IDF).

Firmware Logic (Software Component)

// Placeholder for ESP-IDF control logic

Phase E: Chaos (Verification)

Verification involves automated cycle testing, Wi-Fi reconnection resilience, and MQTT latency audits.