Survival LLM
A free AI assistant and survival library (1.5 million offline articles) that runs on your own computer, with no internet. Shows the source of every answer. Mac and Windows.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Everything for running the home, in one repo: a control center app, the TV dashboard, and one folder per appliance.
Architecture diagram (open the HTML file in a browser)
| Folder | What it is | Status |
|---|---|---|
| home-dashboard/ | The control center app: Next.js UI plus the shared Supabase schema | In progress |
| tv-dashboard/ | Fire TV home screen: time, weather, portfolio, health, calendar, subway, apps | Live |
| rheem/ | Water heater through the Rheem EcoNet API | Planned |
| ac/ | LG ducted AC through an ESP32 on the wall controller wiring | Planned |
| govee/ | Lights through the official Govee API | Planned |
There is no server at home. The control center runs on Vercel, each appliance has a Supabase Edge Function that talks to its cloud API (or to the ESP32 for the AC), and Supabase scheduled jobs handle polling and schedules so everything keeps running when no screen is open.
You ──> home-dashboard (Vercel) ──> appliance functions (Supabase) ──> Rheem EcoNet API ──> water heater
│ ──> Govee API ──────────> lights
│ <── ESP32 (polls) ──────> AC
└──> Postgres: readings, commands, schedules
home-dashboard/ Next.js app, shared Supabase migrations, architecture diagram
tv-dashboard/ Fire TV app, dashboard page, background videos, its Supabase functions, docs
rheem/ water heater edge function and notes
ac/ ESPHome firmware config and the AC edge function
govee/ lights edge function and notes
.github/workflows/ publish the TV page to GitHub Pages and build the TV app
This repository holds no personal data: no keys, passwords, locations, names or calendar
entries. Personal settings live in private Supabase tables; secrets live in Supabase function
secrets and local .env.local files that are never committed.