- Total row now sums each license column individually instead of using colspan
- Missing Assignment warning now flags licensed users with no QWE Client set,
replacing the previous department-based company check
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Mapping (Username/QWE Client/IsRestaurant): CSV export and import via new routes
- License prices: persistent DB table (M365LicensePrice), editable price card with auto-save, CSV export/import
- Summary table: Monthly Cost column per client + grand-total row, calculated live in JS from current prices
- PDF export: client-side jsPDF/autotable, landscape A4, includes cost column when prices are set
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
New top-nav section with a CSV-based license calculator. Upload an Azure AD
user export to see license counts (M365 Standard/Basic, Defender P1, PBI Pro,
PBI Premium) grouped by QWE Client. QWE Client and IsRestaurant are editable
per user, saved to SQLite, and restored on the next upload. Department-based
defaults pre-populate QWE Client (AT→QWE AT, SK→QWE SK) when no saved value
exists.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Two changes:
1. _request_with_retry: after a session-error re-login, also re-fetch
sites and refresh the client reference so the retry uses valid state.
2. get_aps: if every site fails with an exception, clear the token and
sites cache so the very next page reload triggers a fresh login.
Previously the broken state was sticky until a container restart.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Clicking a column header sorts ascending; clicking again reverses to
descending. Active column shows ↑/↓ in blue; inactive columns show ↕
in gray. IP addresses are compared numerically (octet by octet) so
.9 sorts before .10. Sort composes with the name filter and IP filter.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Fetches clients for every AP in parallel using the existing /api/ap-clients
endpoint, then keeps only APs where at least one client has an IP with last
octet 150–155. Shows a loading spinner while fetching.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Previous implementation fetched connected client IPs via API (which was
returning empty data). The filter now checks the AP's own management IP
directly from the data already in the table — no network request, instant.
An AP is shown when its IP last octet is between 150 and 155 inclusive.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
New "Filter .150–.155" button fetches all connected clients via
GET /api/all-clients (one request per site, grouped by AP MAC),
then hides any AP row that has no client with a last-octet IP
between 150 and 155. Clicking again clears the filter.
The name/site search and IP filter compose (AND logic) via a shared
applyFilters() function. Client data is cached in-memory for the
current page session so repeated toggles don't re-fetch.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
After confirming a reboot (single or bulk), the row button and checkbox
are immediately disabled and can't be re-triggered in the current session.
Button text changes to "Rebooting…" while the request is in flight, then
"Rebooted" on success or "Failed" on error — but stays disabled either way.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Clicking an AP name opens a modal showing all wireless clients currently
associated with that AP: hostname/MAC, IP, SSID, band, channel, signal
strength with quality label, TX/RX link rate, and connection uptime.
Backend: GET /api/ap-clients?mac=&site_key= calls the Omada clients
endpoint with filters.apMac; falls back to client-side filtering if the
controller doesn't support that query param.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
FastAPI/Jinja2 web app for viewing and rebooting TP-Link Omada APs
across all sites. Authentik OIDC auth, SQLite audit log, Docker deploy.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
cgasserandClaude Sonnet 4.6