-
Notifications
You must be signed in to change notification settings - Fork 0
User Guide Web App
Oliver Hennhöfer edited this page Apr 7, 2026
·
1 revision
This page explains end-user workflows in the React frontend.
Use this page for account, charger, favorites, and anomaly workflows in the UI.
- Platform users and operators interacting with the web app.
| Route | Purpose | Access |
|---|---|---|
/register |
Create account | Public |
/verify |
Email verification | Public |
/login |
Sign in | Public |
/forgot-password |
Request password reset | Public |
/reset-password |
Set new password with token | Public |
/ |
Charger overview dashboard | Authenticated |
/details/:chargerId |
Telemetry detail for one charger | Authenticated |
/monitoring/:chargerId |
Start/stop monitoring workloads | Authenticated |
/favorites |
Favorite chargers list | Authenticated |
/anomalies |
Recent anomaly events | Authenticated |
/account |
User profile/account actions | Authenticated |
Compatibility note: some historical references may still mention /favourites; use /favorites in current docs.
- Register with email and password.
- Verify account via email link.
- Log in and receive bearer token.
- Token is attached to API calls by frontend API client.
If verification mail is not visible in local mode, check Mailpit at http://localhost:8025.
- Open
/to list chargers. - Select charger to open
/details/:chargerId. - Select telemetry type and time range.
- UI fetches telemetry and renders charts/tables.
- Add/remove favorite from charger views.
- Open
/favoritesto manage favorite list. - Favorites are user-scoped.
- Open
/anomalies. - Filter by charger and telemetry type.
- Jump from anomaly entries back to charger details/monitoring context.
| UI Message Pattern | Typical Cause | Action |
|---|---|---|
| Login failed / unauthorized | invalid credentials or unverified account | verify email, retry login |
| No chargers found | no data ingested yet | validate source MQTT or simulator path |
| Telemetry request failed | API/DB latency or outage | check gateway/TACTIC/DB health |
| Monitoring start failed | invalid model config or orchestration failure | validate model params, inspect TACTIC logs |