37 lines
1.4 KiB
Markdown
37 lines
1.4 KiB
Markdown
# Omada Software Controller
|
|
|
|
Runs on the OptiPlex homeserver (`192.168.30.20`, Servers VLAN) in `~/omada`,
|
|
using the community-maintained
|
|
[`mbentley/omada-controller`](https://github.com/mbentley/docker-omada-controller)
|
|
image instead of TP-Link's cloud controller. UI: `https://omada.home.staffenberger.at`
|
|
(via NPM) or `https://192.168.30.20:8043`.
|
|
|
|
Migrated from the temporary instance on David's desktop on 2026-10-04 — see
|
|
[../../docs/omada-controller-migration.md](../../docs/omada-controller-migration.md).
|
|
|
|
## Operate
|
|
|
|
```bash
|
|
docker compose up -d
|
|
docker compose logs -f
|
|
```
|
|
|
|
Version check:
|
|
|
|
```bash
|
|
curl -sk https://localhost:8043/api/info | grep -o '"controllerVer":"[^"]*"'
|
|
```
|
|
|
|
## Notes
|
|
|
|
- Image tag is pinned to `major.minor` (`6.3`, controller 6.3.0.45). **Never use
|
|
`latest`** — it still points at v5. Check
|
|
[Docker Hub tags](https://hub.docker.com/r/mbentley/omada-controller/tags)
|
|
before bumping, and never move backwards once the Mongo database has been
|
|
touched by a newer version.
|
|
- `network_mode: host` because discovery/adoption depends on broadcast and a
|
|
wide range of UDP/TCP ports.
|
|
- Data is bind-mounted to `./data` and `./logs`. Auto-backups land in
|
|
`./data/autobackup`. Export a manual backup after every bigger change
|
|
(Settings → Maintenance → Backup & Restore). Backups contain secrets (device
|
|
account, WireGuard keys, DDNS settings) — keep them out of git.
|