dashboard-unifi

Go to file

jwed fc4f5370ae fix(ppsk): null schedule = always on; disabled global toggle restores all

Previously SyncPpskSchedules returned early when the global setting
was disabled, leaving any PPSK that had been held by a prior sync
stuck in 'held' state. It also only iterated whereNotNull(schedule),
so null-schedule PPSKs ("always on") were never drift-corrected back
to active either.

Now the command always runs and computes a per-PPSK target state:
  - global ppsk_scheduling disabled  → target = active (always)
  - global enabled  + null schedule  → target = active (always)
  - global enabled  + has schedule   → follow the schedule's slot

PPSKs that drift from the target get enabled/disabled accordingly.
Schedules in unifi_ppsks.schedule are preserved across global toggles
either way — disabling the setting doesn't touch them, so re-enabling
resumes the operator's per-PPSK schedules.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-23 16:09:40 -04:00

config

feat: initial commit — UniFi snap-in package

2026-04-12 23:00:05 -07:00

database/migrations

feat: password rotation, PPSK management, VLAN/AP groups

2026-05-19 17:54:24 -04:00

src

fix(ppsk): null schedule = always on; disabled global toggle restores all

2026-05-23 16:09:40 -04:00

composer.json

feat(nav): surface AP Groups page; always-fresh device data on edit pages

2026-05-23 16:06:49 -04:00