Replace ESP32 with unified Raspberry Pi controller and update course README #4
Labels
No labels
area/android
area/device
area/hardware
area/linux-hub
area/protocol
area/server
area/testing
area/ui
kind/bug
kind/chore
kind/docs
kind/feature
state/blocked
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rznz/signal-lost#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Replace the split ESP32 hardware peripheral and standalone Linux hub with a single Raspberry Pi running embedded Linux (GPIO peripheral I/O, scenario engine, and REST/WebSocket API), and update
README.mdwith the course project proposal required for checkpoint 1.Acceptance Criteria
README.mdcontains the course proposal sections (team members and Forgejo handles, topic, tasks, expected December 2026 outcome, and public repository link) targeting Raspberry Pi and Android (Java).AGENTS.mdandARCHITECTURE.mddescribe the Raspberry Pi as the unified embedded Linux physical controller and scenario/API hub, with optional VPS sync.ARCHITECTURE.mdconnect the Android app directly to the Raspberry Pi hub over local REST/WebSocket and remove the separate ESP32 network hop.solve_workflow.md,schema.md) reflect Raspberry Pi hardware/service verification instead of ESP32 firmware compilation.outcome.md) records the architectural decision and regeneratesdocs/generated/indexes cleanly.