Small companion service that receives SNEK callbacks, decodes Sens'it
Discovery payloads for all 6 modes (Standby, Temperature, Light, Door,
Vibration, Magnet), stores in SQLite, and serves a responsive dashboard.
Backend (Python Flask):
- POST /webhook: receive SNEK callback
- GET /api/devices, /api/messages, /api/decode
- GET /events: Server-Sent Events for live push
- SQLite persistence at /data/messages.db
Frontend:
- Tailwind CSS via CDN, Chart.js for temp/humidity graph
- Live updates via SSE
- Device cards with icons per mode
- Message log with human-readable summaries
Deploy:
- Separate deployment (snek-dashboard) with own PVC
- LoadBalancer on 192.168.1.213:80
- SNEK callback URL: http://snek-dashboard.snek.svc.cluster.local/webhook
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
SNEK resets to authentication=enabled on every restart and does not persist
the state anywhere. The entrypoint now waits for the SNEK API to be ready
and POSTs to /ned/saturation to disable auth automatically.
- Registered devices without HMAC public keys (e.g. demo Sens'it) are
decoded immediately on first boot and after any pod restart
- To re-enable auth in production, comment the polling block in entrypoint.sh
README updated with details in the "Configuration des devices" section.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Add "Sécurité, vie privée & aspects légaux" section covering:
- What the SDR dongle actually captures (RF broadcast)
- What SNEK exposes by default (nothing for unregistered devices)
- Theoretical interception attack scenario
- Legal aspects (Article 226-15, RGPD)
- Best practices to mitigate
- Fix MAX_DEVICES doc: 5 is the hard limit (JS frontend hardcoded)
Removed misleading claim that config change to 10 works
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
tarcourt