個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗A safety-first home-automation project that turns a Shelly Plug S Gen3 into a timed coffee-maker controller. Every on-state is a countdown timer — the plug can never be left on indefinitely. The device runs autonomously with an mJS state machine and a connectivity watchdog, takes commands over a local MQTT broker (mTLS) with a cloud bridge for off-LAN access, and is also controllable directly over Wi-Fi (local HTTP). Clients: an Android app, a web page, or curl.
Live web control: https://laffs2k5.github.io/shelly-coffee-timer/
Documentation: Specification · Architecture · AI Test Guide · Regression Checklist
This is v2 — local MQTT broker + cloud bridge + connectivity watchdog, validated on hardware. The v1 release used Adafruit IO; that design is archived in docs/archive/ (frozen at the
adafruit-finaltag). v2 design: specs 11–12 and Architecture.
shelly-coffee-timer/
├── app/ Android app (Kotlin/Compose) with notification service
├── device/ mJS script for the Shelly (coffee.js)
├── web/ HTML control page (GitHub Pages)
├── scripts/ Bash utilities (feed setup, REST/MQTT testing)
├── docs/spec/ Specification documents (00–03, 05–12 + INDEX; 04 archived)
├── docs/ Architecture overview, test guides
├── docs/archive/ v1 (Adafruit) docs + v2 build/validation record
├── .github/workflows/ CI/CD: APK build, release, GitHub Pages deploy
├── .env.example Template for credentials
└── CLAUDE.md AI assistant context
cp .env.example .env and fill in your broker hosts, credentials, and Shelly IP; source .envMqtt.SetConfig via RPC — see doc 11 §5)scripts/build-device.sh produces device/coffee.min.js; flash it via RPC (Script.PutCode) or paste into the Shelly web UIscripts/app/ in Android Studio.p12 and your broker's private-CA public cert (.crt/.pem) — both via the Import buttons in Settings. (HTTP-direct and cloud work without these.)Nothing identity-specific is baked into the APK — the official released build is fully functional once you enter settings and import the CA +
.p12at runtime. No rebuild needed.
web/index.html locally in a browserAll secrets live in .env, which is gitignored. This repo is public — never commit real API keys. See doc 10 §7 for the full credentials policy.