bonaminandClaude Opus 5.5
c56344a6dc
Mirrors the firmware repo's api-reference.md audit (project-vesper docs/reference/api-reference.md): - playback.play: correct field semantics (url not download_url, speed boot default 500 / 0→300, note_assignments value = 1-based bell, sticky fields, legacy total_duration ignored without continuous_loop); playback.stop has no error path. - UART whitelist now matches UARTTransport::WHITELIST (5 raw cmd strings). - Add the missing rf namespace (set_slot/clear_slot/get_slots/enable) with every error string. - Fix clock.set_alerts (camelCase), clock.set_silence (nested), clock.set_time offsets, relay.test_bell missing error, ota.update default channel, ota.set_channel description, files.download download_url, list_builtin "pid" key, logs.list extra error, telemetry boot-history limit=0, diagnostics topic, network.set_config AP-mode messages, ping data.type. - Legacy map now matches LegacyAdapter's tables; message-format card and req_id notes reflect MQTT-only req_id and per-transport "v" defaults. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
BellSystems Admin Panel
Self-hosted web admin panel for managing BellSystems devices, melodies, users, and MQTT communications.
Tech Stack
- Backend: Python / FastAPI
- Frontend: React + Tailwind CSS (Vite)
- Database: Google Firestore (Firebase Admin SDK)
- MQTT: Mosquitto (paho-mqtt)
- Auth: JWT with role-based access control
- Deployment: Docker Compose + Nginx
Getting Started
# Clone the repo
git clone <your-gitea-url>/bellsystems-admin.git
cd bellsystems-admin
# Copy env template and fill in your values
cp .env.example .env
# Place your Firebase service account key in the project root
# (file is gitignored — never commit it)
# Start everything
docker compose up --build
Project Structure
bellsystems-admin/
├── backend/ # FastAPI API server
├── frontend/ # React SPA
├── nginx/ # Reverse proxy config
├── docker-compose.yml
└── .env
Documentation
See BellSystems_AdminPanel_Strategy.md for the full architecture and build plan.