An edge-AI IoT orchestration engine on a Raspberry Pi 4 — precision prayer-audio casting, ADB device choreography, and a fully on-device LLM that never touches the real-time path.
One Raspberry Pi is the entire backend. External data flows down through the edge core's service mesh, out over the local network to physical devices, and up to the cloud for the operations dashboard.
annual_schedule.json (incl. Hijri dates).npm audit fix, dependency hygiene.dumpsys power / media_session / audio) and key-event injection to the Android TV, with 8s timeout + SIGKILL guards.npm audit fix + CI.The Pi core sits at the center. Hover any node. Flowing lines show direction and payload: cyan = data ingest, gold = real-time cast/control, emerald = device telemetry, violet = local AI.
One full autonomous cycle, from idle monitoring through the millisecond-precise trigger to recovery and cloud sync. This is the real sequence encoded in CoreScheduler.js.
The on-device LLM is powerful but a Pi 4 inference can take seconds. The architecture forbids any AI work inside each prayer's critical window, so the Adhan always fires on time — no matter what the model is doing.
Watch the AI agent (🤖) travel across the day. In a red prayer window it is blocked; in the green quiet zones it is free to run.
A Pi 4 can't run two inferences at once, and Ollama can wedge. The breaker fails fast and self-heals.
/api/ask never hard-fails.