Primary field operation guide for non-expert shelter staff and volunteers.
- Connect power, LAN, and display cables.
- Boot the device and wait for services.
- Verify:
systemctl is-active azazel-edge-websystemctl is-active azazel-edge-control-daemon
- Open dashboard from a local-network browser at
http://<pi-ip>:8080. - Confirm posture color and recommended first action.
- GREEN: Continue monitoring and periodic checks.
- YELLOW: Run initial checks and keep system state stable.
- RED: Treat as active incident, escalate, and use reviewed runbooks.
- Q: Wi-Fi does not connect. A: First isolate whether it is one device or many devices, then follow runbook candidates.
- Q: The status turned red. A: Confirm current recommendation and execute one approved step at a time.
- Q: How do we reboot safely? A: Check logs and execute only approved reboot procedure.
| Role | Name | Contact |
|---|---|---|
| Shift lead | ||
| Network support | ||
| Escalation |
- Raspberry Pi unit
- SD card
- Power adapter
- LAN cable
- e-Paper display
For full Japanese wording, see docs/OPERATOR_GUIDE_JA.md.
GREEN -> monitor -> continue normal checklist
YELLOW -> check dashboard -> follow reviewed runbook if needed
RED -> escalate immediately -> run approved runbook only
Principle:
- Do not perform destructive or unapproved actions outside reviewed runbooks.
auth_failed: token missing/invalid. Confirm token source and retry.control_socket_unavailable: control daemon unavailable. Check service state and socket path.aggregator_registry_unavailable: aggregator store unavailable. Continue local deterministic operations.runbook_not_found: runbook ID mismatch. Refresh list and confirm current runbook catalog.