TP2 🔄 omada-mcp deployed (.176/pve-LXC) — braucht Open-API-Client-Creds

- omada-mcp Container auf pve-LXC (.126, endpointId=2, ipvlan .176), Stack Id=200, gestoppt
- Erkenntnis: jmtvms/tplink-omada-mcp nutzt Omada OPEN API (CLIENT_ID/SECRET/OMADAC_ID/SITE_ID),
  NICHT username/password → .env-Schema + compose-Kommentare + .env.template angepasst
- omada-mcp in ~/.claude/settings.json eingetragen (SSE .176:3000)
- Letzter manueller Schritt: Open-API-App im Controller-UI anlegen (Platform Integration),
  Client-Creds + SITE_ID in .env → Container starten → reload → dann VLANs + Adoption

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

mcp/omada/.env.template

@@ -1,8 +1,16 @@
 # omada-mcp Secrets — .env (gitignored). Dieses File = Template, .env = echte Werte.
+#
+# jmtvms/tplink-omada-mcp nutzt die Omada OPEN API (nicht User/Passwort!).
+# Client-Credentials erzeugen: Controller-UI → Settings → Platform Integration → Open API →
+#   neuen App-Eintrag (Grant Type: Client Credentials) → liefert Client ID + Client Secret.
+# omadac_id: aus https://10.40.41.175:8043/api/info → result.omadacId
+# site_id:   Controller-UI Site-Auswahl, oder API /{omadacId}/api/v2/sites → result.data[].id
+
 MCP_TRANSPORT=sse
 PORT=3000
-OMADA_URL=https://10.40.41.175:8043
-OMADA_USERNAME=admin
-OMADA_PASSWORD=REPLACE_AFTER_WIZARD
-OMADA_SITE=BF
-OMADA_SKIP_CERT_VERIFY=true
+OMADA_BASE_URL=https://10.40.41.175:8043
+OMADA_OMADAC_ID=adbef8fa3505fb16b09818eab71d824e
+OMADA_CLIENT_ID=REPLACE_OPENAPI_CLIENT_ID
+OMADA_CLIENT_SECRET=REPLACE_OPENAPI_CLIENT_SECRET
+OMADA_SITE_ID=REPLACE_SITE_ID
+OMADA_STRICT_SSL=false