Skip to content

Expose wireless band, channel, and channel width on client device trackers - #174

Open
cmadds wants to merge 1 commit into
schmittx:mainfrom
cmadds:pr-band-channel
Open

Expose wireless band, channel, and channel width on client device trackers#174
cmadds wants to merge 1 commit into
schmittx:mainfrom
cmadds:pr-band-channel

Conversation

@cmadds

@cmadds cmadds commented Jul 30, 2026

Copy link
Copy Markdown

Summary

Adds band, channel, and channel_width attributes to connected wireless client device_tracker entities, sourced from data the API already returns (interface.frequency, channel, connectivity.rx_rate_info.channel_width).

Example attributes on a wireless client:

band: 5 GHz
channel: 153
channel_width: WIDTH_80MHz

Why

Makes it easy to see how clients are distributed across bands (2.4 / 5 / 6 GHz) and channels — handy for spotting devices parked on a band with poor signal, or auditing 2.4 vs 5 GHz usage across a mesh.

Notes

  • Only added for wireless clients while connected (wired clients have no band).
  • No new entities; just attributes on the existing device_tracker, consistent with the current connected_to / connection_type attributes.
  • Verified populating correctly across a live network (2.4/5/6 GHz clients).

…ckers

Adds band (e.g. '2.4 GHz' / '5 GHz'), channel, and channel_width attributes to
connected wireless client device_tracker entities, sourced from data the API
already returns. Useful for seeing how clients are distributed across bands.
mikesten added a commit to mikesten/home-assistant-eero that referenced this pull request Aug 12, 2026
…h on client trackers

Adopted from cmadds via schmittx#174 (unmerged upstream).
Adds band/channel/channel_width attributes to wireless client device trackers
- the per-client radio detail this integration was installed to surface.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant