v1.2.2 — lockfile sync for publish

v1.2.2

Publish install fix. No RCA engine change.

• Lockfile in sync. A clean install failed because ajv 6 (eslint) and ajv 8 (form resolvers) were not both recorded. Companion site can install and publish again.

python3 mist_disconnect_console.py
python3 mist_disconnect_console.py --self-test

Observer (read-only) token. GET only. Sample data uses fictional DEMO-AP-F2-* names.

v1.2.1 — radar banner, full screen, diagnose hint

v1.2.1

Bug fixes on the v1.2 radar store.

• One radar banner. Mist often returns the same association twice (connect times a fraction of a second apart). One DFS hit is now one Alert · session on radar AP card.
• Radio events full screen. Expand the 7-day table so every kept event is reachable.
• Diagnose fetch hint. A busy site (lots of devices and radio events) can take up to 60 seconds.
• Teams timestamps. Millisecond call start/end still overlap same-AP radar.

python3 mist_disconnect_console.py
python3 mist_disconnect_console.py --self-test

Observer (read-only) token. GET only. Sample data uses fictional DEMO-AP-F2-* names.

v1.2 — AP-keyed radar store

v1.2 — AP-keyed radar store

Code fixes. Same-AP radar correlation still requires a session on the AP that took DFS; neighbor radar is not a hit.

• RadioEventStore looks up radars by the session AP (and BSSID aliases) instead of scanning the site firehose. Mist listSiteRrmEvents cannot filter by AP.
• Time-sliced RRM fetch so a radar storm in the last hour cannot hide a hit from hour 18.
• Scrollable client-radar panel and banner tables so the matching DFS row is visible.
• Open-session overlap: Mist disconnect: 0 is treated as still associated.
• Faster login and live: token validate is /self only; live polls walk the newest hour of RRM, not the full 7-day page walk.

python3 mist_disconnect_console.py
python3 mist_disconnect_console.py --self-test

Observer (read-only) token. GET only. Sample screenshots use fictional DEMO-AP-F2-* names.

v1.1 — DFS radar session alerts, 7-day Radio Events, Teams correlation

v1.1 — DFS radar session alerts, 7-day Radio Events, Teams correlation

Python console RCA for Juniper Mist client disconnects. Sample screenshots use fictional DEMO-AP-F2-* names only.

Highlights

Alert when a session was on the radar AP

If the client’s session was associated to the AP that took a Post radar / DFS hit, a pulsing banner shows:

• the exact session (connect, disconnect, AP, SSID, band)
• the exact radio event (date, channel pre → post, width, power, Post radar)
• any Microsoft Teams meeting in progress

Juniper RRM: DFS radar deauthenticates every associated station. Radar on a different AP is not a correlation.

7-day Radio Events (portal parity)

GET /sites/{id}/rrm/events requires band. v1.1 fetches 5, 24, and 6 in parallel (5 GHz paginated). Labels match the portal: Post radar, Interference AP non wifi, Scheduled site RRM.

Teams / Zoom (7 days)

Call window, meeting id, audio/video quality, overlap with same-AP radar or wireless disconnects.

Full session list

Every association in the window — not the first eight. Radar-overlapped rows are tagged.

Event timeline

CLIENT_IP_ASSIGNED is OK (DHCP Success). Timed-out / denied DHCP stays FAIL.

Run

python3 mist_disconnect_console.py

Observer (read-only) token. GET only. python3 mist_disconnect_console.py --self-test for the correlation checks.

See the README for screenshots and API table.

Mist WiFi Client Disconnect RCA

Provides additional RCA analysis for persistent client disconnect issues on layer 1 and above.