Skip to content

Channels / Channel analysis page rework suggestions #1283

Description

@crowedavid

currently running v2.36.0

again, loving the direction on this. a few suggestions, most on UI enhancements.

keep the band selection sticky when changing between APs

currently, if i want to flip between my APs to compare what the analysis is seeing in the 5 GHz band on each, selecting the AP causes it to switch back to 2.4 GHz.

suggest changing "24 h / Now" selector labels

  • i wasn't sure what they refer to when i first saw it
  • suggested alternatives: "Analysis / Current channels", "Recent scan / Existing view"
  • this selector is already sticky between AP dropdown changes

when the "Now" option is selected, the "Current channels" card could go away and reuse the band selector

  • if the "24 h / Now" selector label text is changed to match, you can remove the Current channels card
  • move the band selector to reuse the top card's band selector

when in the "24 h" mode, in the Networks detected table a few ideas

  • move the SSID to be the first column
  • if CHANNEL is selected to be sorted, use Signal as a secondary sort that initially sorts in descending order (top less negative, bottom more negative)
    • i think the signal column currently does this but in ascending order
    • i usually want to first see what has a closer, stronger signal that might most impact my current band
  • when the SSID is selected to be sorted, use Signal as a secondary sort in descending order
    • use case for this (at least for me) is being able to group the "Hidden" SSIDs together (usually mesh network links)
    • similar Signal strength should help indicate if the neighbor mesh network is stronger and closer
  • add a Filter to limit display from lower Signal entries
    • this will help reduce the clutter with lots of neighbors
    • if the filter isn't an entry field, a dropdown in 5 dBm increments from -50 to -85 dBm
  • add a visual differentiator for different "Width" values
    • the infrequent 40 MHz width channel could be important but can easily be overlooked with lots of 20 MHz bands (for example)
    • text color might be easiest, maybe background? i'm out of my depth on what is "easiest"

Activity

  1. gnacho commented on Oct 6, 2026

    @gnacho
    Owner

    Ideas 1 and 2 shipped (#1286):

    1. Sticky band: the band you pick now survives switching APs - pick 5 GHz once and every unit you flip to selects its 5 GHz radio (when it has one; otherwise it falls back to its first radio).
    2. Labels: the toggle now reads "Analysis / Current channels" (ES: Análisis / Canales actuales) instead of the cryptic "24 h / Now". You were right that it needed words, not units.

    Ideas 3 (folding the Current channels card into the main view when the lens is on) and 4 (table: SSID first, signal as secondary sort, minimum-signal filter) are next in my queue - the table work is the bigger of the two. Leaving this open until both land.

  2. gnacho commented on Oct 6, 2026

    @gnacho
    Owner

    All four ideas shipped:

    1. Sticky band across APs (feat(channels): sticky band across APs, clearer lens labels #1286, restored in feat(channels): Now lens follows the top band selector; restore lost sticky band; client table upgrades #1300 - see below).
    2. Lens toggle now reads "Analysis / Current channels" (ES: Análisis / Canales actuales).
    3. The Now lens is driven by the top band selector: its internal title and selector are gone, and flipping the band on the toolbar flips the survey.
    4. Client table: band and SSID sorts break ties by signal descending (strongest neighbors grouped), a minimum-signal filter (≥ -70/-80/-90) hides the weak clutter, and linked MACs are searchable and shown in the expanded detail (Enhancement for linked MAC address option (related to #1151) #1298).

    One note for the record: my #1286 merge only carried the locale half of the sticky-band change - a working-session collision ate the ChannelPlan half, and the band kept resetting since. #1300 restores it and the final verification caught it. Everything is in main and ships with v2.38.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions