Skip to content

WhatCable Release Notes

Darryl Morley · Inspect USB-C cable capabilities, dock topology and charging/link bottlenecks on Apple Silicon Macs.

CaskDrivers & HardwareAuto-updates 9.1K
Install command
brew install --cask whatcable
30-day installs
442
#435 in App
1-year installs
5.8K
Last 365 days
Latest version
1.5.0
Download size
23MB
zip
Release cadence
Irregular
0 releases in 30 days
  1. 1.5.0

    Latest

    OpenNavo editorial Added to Homebrew

    CompatibilitymacOS 14 or later

    WhatCable 1.5.0 — Devices, displays and live charging

    Corrects Thunderbolt device placement and TB5 speeds, reads actual macOS display state, and updates charging live. Improves cable tracking, notifications and UI. Review script output changes; update the standalone CLI together with the app.

    Editorial summary

    Corrects Thunderbolt device placement and TB5 speeds, reads actual macOS display state, and updates charging live. Improves cable tracking, notifications and UI. Review script output changes; update the standalone CLI together with the app.

    Saved cables migrate automatically. --bench-report is now schema version 3; --json display objects gain fields and remove compressionPlausible. Review scripts consuming either output. Charging resistance estimates remain experimental and Pro-only. Test-kit consent now names the Mac model identifier sent with a run. Complete details, credits and limitations follow.

    Complete official English release notes

    Devices in the right box, displays read from macOS, and live charging

    A big one. Ten betas went into this, and most of what changed started with a tester's report. Credits inline.

    Connected devices

    • Devices on a Thunderbolt chain show under a dock or display only when the hardware proves they are inside it. Before, a device could look as if it sat in the first box in the chain just because nothing said otherwise. Anything unproven now appears under "Other USB devices on this port", and a dock's own hubs nest where they belong.
    • Thunderbolt 5 daisy chains are sorted. On a Mac to display to dock chain, a drive in the dock used to render under the display. WhatCable now works out which box each hub belongs to from the fabric's own routing data, and leaves the tree alone if the answer does not check out.
    • Devices behind TB3-era docks and displays are attributed to a port again. LG UltraFine 5K, CalDigit TS3+ and others of that generation bring their own USB controller, and everything behind them used to vanish as soon as two Thunderbolt things were connected.
    • Built-in USB-A ports are labelled and split per physical port (#490, thanks @i0ntempest). The box now says to move those devices to a Thunderbolt port to see more about them.
    • A port that can't read cable details now says where to plug the cable instead: a Thunderbolt port (#436, thanks @apple-ihack-geek).

    Displays

    • The display check now reads what macOS says the display is doing, instead of estimating from bandwidth. It tells "the cable is limiting your monitor" apart from "your monitor is set below its best mode".
    • Fewer false warnings on TVs and HDMI adapters: modes they can only send in reduced colour (4:2:0) no longer count against the cable.
    • Every mode the display declares is read, including DisplayID blocks that were skipped before. Where macOS doesn't say enough, the card reads "Display connected" with the reason, rather than a guessed all-clear.
    • The false "needs about 14.4 Gbps" warning on a monitor with a 75 Hz scan range is gone (#596, thanks @JarvisDong). Preferred refresh rates now count EDID borders, contributed by @YuriNachos.

    Thunderbolt

    • A Thunderbolt 5 link reads 80 Gb/s, not the per-lane 40 (#607, thanks @cannotcollide for the raw dumps). Asymmetric links show one rate per direction.
    • An idle Thunderbolt port no longer reads as linked, and a stale row left after an unplug can't describe a link that isn't there.
    • Another Mac on the far end of a Thunderbolt cable reads "Linked to another Mac" and no longer blames the cable.
    • A charger-only cable no longer flashes "10 Gbps" as you plug it in (#181).

    Charging

    • Charging state is now live: no more "charging on hold" for the first minute after plug-in, the open popover updates as it changes, and it now shows when your Mac is held at its charge limit.
    • A third-party charger on MagSafe no longer shows Brick ID junk, and the card stops spinning on a non-PD charger (#592).
    • Pro: the charging resistance estimate is visible and says what it is doing. Still labelled experimental.

    Cables

    • Straighter e-marker wording. Some chargers and docks block the read, and the card now says so. While macOS is still reading it says "Reading cable details…", and when a charger negotiates above 3A without the Mac seeing the e-marker, it says what that contract shows. Thanks @jimmyorz (#413), @cannotcollide, @spreiter and @official-Cromatin (#578).
    • Cables with blank or partial e-marker IDs can be tracked, and so can MagSafe 3 cables. Existing saved cables migrate automatically. Reported by @EmilEmilchen (#530).
    • A registered power brick no longer softens a blank e-marker vendor ID, contributed by @YuriNachos.
    • Apple accessories show their own names. Apple's USB-C EarPods read as a small powered accessory, not a 60 W cable (#542, thanks @maelcum).
    • The cable database now holds 145 entries.

    Notifications

    Thanks to @official-Cromatin for methodical reports and raw captures throughout (#550, #551, #556).

    • Plugging in or unplugging a dock posts one notification naming the dock, with every device on its own row.
    • Disconnect notifications say what left. Clicking a notification opens the popover. A disconnect replaces the held connect banner instead of piling under it.
    • The phantom charger banner at launch is gone, and a device that drops and returns says "Reconnected".
    • Thunderbolt gets named, and Pro users see a saved cable's name, including on charger notifications (#593).
    • "Notify on app updates" is its own switch.

    The app

    • The port card groups every line under what told us it: the cable's chip, your Mac's measurement, WhatCable's database, or the charger. Cards now settle once instead of assembling in front of you, and hold still while you read them (#536, thanks @miketuckman).
    • WhatCable takes up less room in the menu bar, 36pt instead of 42pt.
    • The popup no longer closes itself while you plug and unplug, follows the icon when you rearrange the menu bar (#543, thanks @maelcum), and closes when you tell it to.
    • Settings has an Updates section with an "Include beta versions" switch.
    • Numbers follow your region, and the app language setting reaches the menus too. Thanks to Rob for the number formatting.
    • Pro screens and Settings no longer crop or float in window mode (#600, thanks @official-Cromatin).
    • Pro: see and free your licence's device slots from Settings and the CLI.
    • On a first run, the deep USB probe waits until the welcome screen has shown (#571, thanks @aapple1944 and @tvalleau).
    • The desktop widget shows its detail line again, and a port no longer claims "Plugged in" when your Mac is on battery.
    • The terms now say plainly that you can share what WhatCable tells you, as long as you describe it accurately.

    Test kit

    • The test kit is rebuilt: it captures a fuller hardware snapshot in fewer steps, and uploads are smaller.
    • The consent screen asks you to plug in what you want included and leave it connected until the run finishes, and names the Mac model identifier, which is sent with the run. Running it again no longer replaces your earlier submission.

    For scripts

    • For scripts: --json and --bench-report display output has changed. --bench-report is now schema version 3, with every mode the monitor declares.
    • For scripts: --json display objects gain new fields, and compressionPlausible is gone.
    • New whatcable --bench-report command for a per-cable JSON capture.
    • The terminal dashboard's power view no longer sits on "Waiting for telemetry..." on M1 Pro and similar Macs (#580, thanks @official-Cromatin).

    Update both together

    If you use the standalone CLI, update it along with the app.

    Translations

    Italian from @bovirus, Traditional Chinese from @jimmyorz, and Latvian from @shpokas.

    Thanks

    To the beta group. @official-Cromatin reported and captured most of what changed in notifications and windows, @cannotcollide caught the Thunderbolt 5 speed and sent the dumps that fixed it, @maelcum stuck with the popout through several attempts, and @aldobalducci tested charging on beta.10. @YuriNachos contributed two fixes.

    Official source

  2. 1.5.0-beta.10

    Pre-release

    GitHub Release

    v1.5.0-beta.10: Charging state you can trust, read live

    Charging state you can trust, read live

    Beta build for testers. Not recommended for general use.

    Charging state

    WhatCable now reads the charging state live from the Mac's System Management Controller (SMC), the chip that runs charging. Before, it waited on macOS's battery record, which can take a minute to catch up.

    • After you plug in, the popover shows charging within a few seconds. It no longer says "Plugged in, charging on hold" for the first minute (#634, thanks @official-Cromatin).
    • The open popover updates by itself. You no longer need to close and reopen it.
    • New: "Plugged in, charge limit reached" when macOS has stopped charging at the level it's charging the battery to.
    • New: "Plugged in, running on battery" when the charger is connected but the Mac isn't taking power from it. It only shows once this has lasted 2 seconds, so the brief blip every Mac has at plug-in never appears.
    • The widget and the whatcable CLI show the same state as the popover.
    • Macs without these SMC keys, desktops included, behave exactly as before.

    Also in here

    • Ports: the "USB active" row is gone, because macOS reports it as true on every port. The SuperSpeed row now only shows a live, confirmed USB 3 link (#532).
    • The app language setting now reaches the menus too, and macOS's own strings follow it.
    • The hardware read that runs every second no longer runs on the main thread, so the popover stays responsive.
    • The cable database gains reports #541, #625 and #631.

    What to look at

    • Plug in with the popover open: does it say charging within a few seconds?
    • If you use a charge limit (or Optimized Battery Charging is holding at 80%): does it say "charge limit reached"?
    • Do the widget and the popover agree?
    • Did you ever see "Plugged in, running on battery"? Tell me what was plugged in at the time.

    Install by downloading WhatCable.zip below, unzipping, and dragging WhatCable.app into /Applications over your existing copy.

    Please report anything odd on the issue tracker: https://github.com/darrylmorley/whatcable/issues

  3. 1.5.0-beta.9

    Pre-release

    GitHub Release

    v1.5.0-beta.9: Devices in the right box, and displays read from macOS

    Devices in the right box, and displays read from macOS

    Beta build for testers. Not recommended for general use.

    This is a big one. Since beta.8 the Connected devices list, the display diagnostic, Thunderbolt link readings and the test kit have all changed. The first two sections are where I most need testers.

    Connected devices on Thunderbolt chains

    USB devices now show under a dock or display only when the hardware proves they are inside it. Before, a device could look as if it sat in the first box in the chain just because nothing said otherwise.

    • Anything unproven appears under a new "Other USB devices on this port" heading on that port.
    • A dock's own hubs now nest where they belong.

    The display diagnostic

    It now reads what macOS states about the panel, instead of estimating bandwidth and warning from that.

    • It reads every mode the display declares, including the ones in DisplayID blocks that were skipped before. The top mode is the highest declared mode in any format. Nothing is estimated.
    • Whether the live mode is compressed (DSC) comes from macOS, and so does whether the panel's top mode is offered on this link. "Display may be using compression to reach its top mode" is gone. Apple displays read as compressed with no blame on the link.
    • New wording below the top mode: "Monitor can do more than it is set to" (macOS offers the top mode on this link) and "Monitor can do more than the link is carrying" (it does not).
    • Where macOS does not say enough, the card reads "Display connected" with the reason, rather than a guessed all-clear. One case is a driven timing that lists several colour formats without naming the live one.
    • A mode a panel supports only in 4:2:0 colour is no longer what the link is judged against. A 4K60 TV-style panel is judged on its best full-colour mode, and the verdict names the 4:2:0-only mode as a declared fact.
    • The false "needs about 14.4 Gbps" warning on a monitor with a 75 Hz scan range is gone (#596, thanks @JarvisDong).
    • A display waiting behind an accessory's data approval now says "Display connected, data blocked".
    • The 8-bit bandwidth figure is still shown, labelled as a receipt.

    For scripts: --json display objects gained fields (topMode, edid, drivenTiming, topModeOnLink and others). currentMode.bitsPerComponent can now be null. The compressionPlausible value no longer occurs. --bench-report is now schema version 3 with the full mode list in the EDID object. Anyone parsing either should check.

    Thunderbolt links

    • A Thunderbolt 5 dock reads 80 Gb/s, not the per-lane 40 (#607, thanks @cannotcollide for the raw dumps and test-kit runs).
    • An idle Thunderbolt port no longer reads as linked.
    • Asymmetric TB5 links show one rate per direction, on both ends.
    • A stale Thunderbolt row left after an unplug can no longer describe a link that is not there.
    • Another Mac on the far end of a Thunderbolt cable reads "Linked to another Mac". It no longer blames the cable or a device (#576).
    • A cable's Thunderbolt speed claim alone no longer produces "slower than expected".

    Test kit

    If you contribute diagnostic data, this changes what the run sends.

    • It now runs six probes instead of 23. One is a full registry snapshot, taken at the start and again at the end.
    • Output is compressed before upload, and each run's captures are grouped under one run ID.
    • The consent screen now names the Mac model identifier, which is sent with the run.
    • Running it again no longer replaces your earlier submission.
    • Size limits are higher, so machines with many HID devices no longer get cut off.

    Chargers, cables and accessories

    • A third-party charger on MagSafe no longer shows Brick ID junk on the banner, profile list, diagnostics or power monitor, and the card stops spinning on a non-PD charger (#592).
    • Charger notifications carry the saved cable's name for Pro users (#593), and labels group by physical port.
    • Apple accessories show their own names. Apple's USB-C EarPods read as a small powered accessory, not a 60 W cable (#542, thanks @maelcum).
    • The port controller's own active-cable flag now decides passive versus active. Plug type and e-marker chip vendor appear where known.
    • Billboard devices (docks, adapters) get their alternate modes from what macOS already decoded, so it works with the deep USB probe switched off.

    Also in here

    • On a first run the deep USB probe waits until the welcome screen has shown, so the Settings switch is reachable before anything touches your devices (#571, thanks @aapple1944 and @tvalleau). The welcome screen also wraps its text and sizes itself to fit.
    • Pro licence device management: see and free your slots from Settings and the CLI.
    • New whatcable --bench-report command for a per-cable JSON capture.
    • The terminal dashboard's power view no longer sits on "Waiting for telemetry..." on a charger port on M1 Pro and similar Macs (#580, thanks @official-Cromatin).
    • Translation updates: Italian (thanks @bovirus), Traditional Chinese (thanks @jimmyorz) and Latvian (thanks @shpokas).

    Update both together

    If you installed the standalone whatcable-cli with Homebrew and the app by hand from the zip, update both. An older CLI can tell a new app that you have already been onboarded, so the deep USB probe runs before any window appears. Cask users are not affected.

    What to look at

    • With a dock, a display with USB ports, or a chain of both: do your devices sit in the box they are really in? Report any device shown inside the wrong box.
    • Check the "Other USB devices on this port" heading looks right, and that turning "Show hubs" off and on puts devices in the same place.
    • A display macOS drives uncompressed, and a display behind an HDMI adapter: does the display diagnostic match System Information > Displays? A screenshot of both is ideal.
    • Display cards that read "Display connected" with a reason: is the reason true?
    • Anything that read wrongly on a Thunderbolt link before and reads right now, or the other way round.

    Install by downloading WhatCable.zip below, unzipping, and dragging WhatCable.app into /Applications over your existing copy.

    Please report anything odd on the issue tracker: https://github.com/darrylmorley/whatcable/issues

  4. 1.5.0-beta.6

    Expand

    GitHub Release

    v1.5.0-beta.6: Notifications that behave, cards that settle once, and e-marker wording that adds up

    Notifications that behave, cards that settle once, and e-marker wording that adds up

    Nearly everything in this one traces back to @official-Cromatin's beta.5 report on #566. Credits inline.

    One notification per event, and clicking it works. Notifications now route their clicks properly: clicking opens the popover in the running app instead of launching a second copy (#556, #558). Each category keeps one standing notification, so a disconnect replaces the held connect banner rather than piling under it (#569). The phantom charger banner at launch is gone (#568). A device that drops and returns within a settle window says "Reconnected" instead of pretending it's new (#555).

    Banners queue politely. When a charger and a device land together, the device banner now waits its turn, so both actually present instead of one swallowing the other. The gap is live-verified at 2 seconds (#559 through #562).

    Thunderbolt gets named. Merged device notifications now say Thunderbolt when that's what connected, and Pro users with a saved cable on the port see its name in the title (#566, #570).

    Port cards settle once. A fresh connection shows a calm placeholder with a spinner, then reveals the finished card in one animated step at about six seconds, instead of assembling itself piece by piece in front of you. Unplugging animates out at any stage (#579).

    E-marker wording that doesn't argue with itself. While macOS is still reading, the card now says "Reading cable details…" instead of claiming there's no e-marker (#578). And when a charger negotiates above 3A without the Mac seeing the e-marker, the card now says what that contract actually shows: the cable is e-marked and 5A-capable, the charger read it, and plugging it into another device will show its details. Reported by @official-Cromatin, who caught the app claiming a 3A cap directly above a 100W contract (#578). Amp figures also drop their trailing zeros: 5A, not 5.00A.

  5. 1.5.0-beta.5

    Expand

    GitHub Release

    v1.5.0-beta.5: Daisy chains sorted, cards that sit still, and straighter talk about e-markers

    Daisy chains sorted, cards that sit still, and straighter talk about e-markers

    A busy cycle, and most of it started with a tester's report. Credits inline.

    Devices behind a TB5 dock now show under the dock. On a Thunderbolt 5 daisy chain (Mac to display to dock), macOS lumps every box's USB traffic onto one controller and gives each box an anonymous internal hub, so a drive in the dock rendered under the display. WhatCable now works out which hub belongs to which box from the fabric's own routing data, checks the answer against the controller's port map, and only applies it when everything matches one to one. If anything looks off it leaves the tree alone rather than guessing. Verified on the exact rig that showed the bug.

    The popout follows the icon. Rearranging the menu bar used to leave the open popout anchored where the icon had been. Reported by @maelcum (#543), who stuck with it through several earlier attempts.

    Port cards hold still. When power-source attribution flickered, cards reshuffled mid-read. Order is now stable, and an unplugged charger's card lingers faded for a few seconds instead of vanishing under your cursor. Report by @miketuckman (#536). This is the visual half: the underlying attribution flicker is still under investigation, captures welcome.

    Plugging in a dock posts one notification. Disconnect was grouped in beta.4, connect now matches: one notification naming the dock, every device on its own row. Report, testing and the Notification Centre detective work by @official-Cromatin (#556).

    Straighter e-marker wording. "Every USB-C cable's e-marker can be read" was too confident. Some chargers and docks block the read, so the wording now says so and names the likely culprits. Built on a three-case test matrix and suggested wording from @jimmyorz (#413), with related diagnosis from @cannotcollide on #554, Power-Z meter in hand. Cables with no e-marker at all now also state the practical consequence: capped at 3A, 60W. Suggested by @spreiter.

    Cables with blank or partial e-marker IDs are now trackable. Cable tracking keyed on vendor and product IDs, which some perfectly real cables leave at zero, so they could never be saved. Tracking now uses the full e-marker identity, existing saved cables migrate automatically, and the wording is honest about how confident each match is. Reported by @EmilEmilchen (#530) and a Pro user's support report.

    Beta builds default to beta updates. If you are running a beta, "Include beta versions" now starts switched on, once, and never overrides a choice you have made yourself. @aldobalducci and @official-Cromatin both tripped over the old default in beta.4.

    Translations. Italian refinements from @bovirus, Traditional Chinese refinements from @jimmyorz, including his review of the strings added this cycle.

    The one to lean on: if you have a Thunderbolt daisy chain, open Connected devices and check every device sits under the box it is actually plugged into.

  6. 1.5.0-beta.4

    Expand

    GitHub Release

    v1.5.0-beta.4: Notifications behave, thanks to a proper bug report

    Notifications behave, thanks to a proper bug report

    Unplugging a dock posts one notification, not a lottery. macOS reports a hub and the devices behind it leaving as a dribble of separate events, and WhatCable notified on whatever slice happened to arrive together, so what got named varied run to run. Changes now settle for about a second and a half, then get grouped under the hub they belong to: one notification titled with the dock, everything that left with it listed inside, each device on its own row. Same on connect, at the cost of that small delay. Thanks to @official-Cromatin for the methodical report and the raw captures (#551), the test data for this fix is built from them.

    "Notify on app updates" stands on its own. It was nested under the cable-changes toggle, so turning cable notifications off silently took update notifications with it. It is now its own switch, either can be on without the other. Also @official-Cromatin (#550).

    The test-kit probes also cast a wider net: they now match base IOKit classes instead of a fixed list of leaf names, so port-controller variants Apple ships next turn up in diagnostics instead of being invisible.

    The one to lean on: plug and unplug a dock with things behind it and see if the notification names the lot.

  7. 1.5.0-beta.3

    Expand

    GitHub Release

    v1.5.0-beta.3: Betas can update themselves now, and devices behind older docks come back

    Betas can update themselves now, and devices behind older docks come back

    You can get the next beta from inside the app. Settings has a new Updates section with an "Include beta versions" switch. Turn it on and pre-releases arrive through the normal update prompt instead of you going to the releases page. You still had to fetch this one by hand, sorry, that is the last time.

    Two things it deliberately does not do. Turning the switch back off stops future betas but does not move you off a beta you are already running, the next stable release does that. And if you installed WhatCable with Homebrew you will see a warning, because brew upgrade can put the stable back over a beta without asking.

    Devices plugged into a TB3-era dock or display are attributed to a port again. LG UltraFine 5K, CalDigit TS3+ and anything else of that generation carries its own PCIe USB controller instead of tunnelling USB the way a modern dock does. WhatCable classified those devices as tunnelled with no port, so as soon as you had two Thunderbolt things connected, everything behind the dock quietly vanished from the port card. Found because someone emailed me about it and then ran the test kit so I could see their setup. If you own a dock of that vintage, this is the build to try it on.

    A charger-only cable no longer flashes "10 Gbps" as you plug it in. During the first moment of a connection the port controller briefly reports a SuperSpeed link that then turns out not to exist. WhatCable printed every instant it was handed, so a speed appeared and vanished. It now waits for something to corroborate the claim: a real SuperSpeed device that actually reached the port. Settled readings are unchanged. This is the one The Verge caught (issue #181).

    The popup closes when you tell it to. A regression I introduced in beta.2: the re-anchoring added in beta.2 could race a click-to-close and pop the window straight back open. Worth a hands-on check if you run with the watts readout on, since that was what triggered it.

    Disconnect notifications say what left. They used to read "USB device disconnected" with no name attached, which is not much of a notification. Thanks to Rob for reporting that one.

    Numbers follow your region. If you write 81,8% rather than 81.8%, the app now agrees with you, on screen, in the CLI and in the widget. Exports and --json deliberately stay dot-formatted so scripts do not break. Also Rob.

    Pro: the charging resistance estimate is actually visible now. It shipped in beta.2 rendering only on the live card, and a laptop's charging port is normally the contracted one, so it appeared nowhere. It also says what it is doing: measuring, waiting for the charging load to vary, or a result. Still labelled experimental, still no good/bad verdict, because that needs bench calibration I have not done yet.

    The terms allow sharing what WhatCable tells you. Section 11 read as a ban on showing output to a supplier or a customer. It never meant that. You can share a reading as long as you describe it accurately.

    Italian has been through a thorough pass from @bovirus, covering the charging diagnostics, the power negotiation lines, the display and cable wording, and the Pro screens. Traditional Chinese has another round of refinement from @jimmyorz. The test-kit probes now flag a dump that got cut short by a cable moving mid-read, so a truncated capture stops looking like a machine with fewer devices.

    The dock attribution and the popup close are the two to lean on. If a device shows up under the wrong port, or the popup misbehaves again, tell me what was plugged in at the time.

  8. 1.5.0-beta.2

    Expand

    GitHub Release

    v1.5.0-beta.2: Port cards now say where each fact came from, and a slimmer menu bar item

    Port cards now say where each fact came from, and a slimmer menu bar item

    The big change in this build is the port card. Every line is now grouped under the thing that told us it: what the cable's own chip reports, what your Mac measured, what WhatCable knows about that cable, and what the charger says. Same facts, but you can now see which of them come from the cable claiming something and which come from your Mac actually measuring it. That distinction matters when a cable is lying.

    WhatCable takes up less room in the menu bar. It was 42pt wide, against 22 to 26pt for a typical menu bar extra. It is now 36pt. Every icon is drawn at the same size, so switching icons no longer nudges anything.

    The popup no longer closes itself while you plug and unplug. It used to re-centre its arrow by closing and reopening, which sometimes just closed. It now re-anchors without closing, so a pinned popup keeps its arrow lined up too, which it never did before.

    The desktop widget shows its detail line again. It had been blank since v0.14.0 and nobody spotted it, which tells me something about how closely the widget gets looked at.

    A port no longer claims "Plugged in" when your Mac is on battery. With no charger attached there is nothing to read the cable with, so it now says so rather than implying a connection it cannot see.

    Traditional Chinese wording has been tightened throughout, thanks to @jimmyorz. Nine more cables have been added to the database.

    The port card is the thing to look at on this build. If a line is grouped under the wrong heading, or a card reads worse than it did before, that is exactly what I want to hear about.

  9. 1.4.0

    Expand

    OpenNavo editorial Added to Homebrew

    Fixes dock topology, link-speed blame and charging status.

    Devices
    Place dock devices by actual PCIe topology and keep boot-time TB tunnels.
    Speed
    Compare multi-hop speed against the end device, not the first adapter.Cap Thunderbolt 1/2 devices by generation instead of reporting 40Gbps.
    Power
    Show full/paused charging accurately instead of implying an active charge.
    Data
    Rebuild the cable database with 116 entries and shared fingerprints.

    Fixes dock topology, link-speed blame and charging status.

    Devices

    • Place dock devices by actual PCIe topology and keep boot-time TB tunnels.

    Speed

    • Compare multi-hop speed against the end device, not the first adapter.
    • Cap Thunderbolt 1/2 devices by generation instead of reporting 40Gbps.

    Power

    • Show full/paused charging accurately instead of implying an active charge.

    Data

    • Rebuild the cable database with 116 entries and shared fingerprints.

    Selected exact publisher entries; hardware limitations remain explicit.

    Source: Official release notes.

  10. 1.3.0

    Expand

    OpenNavo editorial Added to Homebrew

    Rebuilds connected-device topology and improves power and certification data.

    Devices
    Nest devices by actual Thunderbolt chain and hide hubs by default.Include device serial number and USB version in CLI JSON.
    Cables
    Read USB-IF certificate IDs against a bundled list without network lookup.Distinguish certified-but-unlisted IDs from absent IDs.
    Power
    Read M1 Pro/Max/Ultra charging contracts and stop stale wattage reports.

    Rebuilds connected-device topology and improves power and certification data.

    Devices

    • Nest devices by actual Thunderbolt chain and hide hubs by default.
    • Include device serial number and USB version in CLI JSON.

    Cables

    • Read USB-IF certificate IDs against a bundled list without network lookup.
    • Distinguish certified-but-unlisted IDs from absent IDs.

    Power

    • Read M1 Pro/Max/Ultra charging contracts and stop stale wattage reports.

    Selected exact publisher entries; hardware limitations remain explicit.

    Source: Official release notes.

  11. 1.3.0-beta.4

    Expand

    GitHub Release

    v1.3.0-beta.4: Power monitor rework, and a fix for M1 Pro / M1 Max charging

    Power monitor rework, and a fix for M1 Pro / M1 Max charging

    This build reworks the whole power path. Most of it is invisible: the same numbers from the same places, moved so one piece of code decides things that used to be decided in three. Two things do change.

    M1 Pro, M1 Max and M1 Ultra should now see their charging contract. On that silicon macOS never reports what the charger and the port agreed, so the Power Monitor's per-port card had nothing to show and sat waiting forever. The figure was in the SMC all along. Thanks to @official-Cromatin for the report and the detail on issue #491.

    The widget stops showing a charge that has ended. Its buffer waited for a slower signal than the app window did, so for a few seconds after unplugging it could still be holding the old figure.

    If a port card looks wrong on this build, that is the thing to tell me about.

  12. 1.3.0-beta.3

    Expand

    GitHub Release

    v1.3.0-beta.3: Beta build 3: the connected devices list, rebuilt

    Beta build 3: the connected devices list, rebuilt

    Third beta for the tester group, still 1.3.0. Everything since v1.2.1 is in here, including beta.1 and beta.2. Licensing is unchanged: use your normal Pro key.

    New since beta.2

    • Connected devices now shows what is plugged into what. Behind a dock chained off a display, that list used to be one flat pile of hubs. On my own setup it was twelve rows, five levels deep, nine of them hubs, with the display and the Ethernet adapter lost in the middle. Now the Thunderbolt chain is the shape of the list, and each device sits inside the thing it is actually plugged into. Same setup, four rows.
    • Hubs are hidden by default. They are plumbing, and they are roughly half of every device list. "Show N hubs" brings them back per port, and the CLI still prints everything.
    • A device that names itself is no longer listed twice. A dock that reports its own name over USB used to appear as both the dock and a device inside itself.
    • Devices are named by their maker where the name alone would not tell two apart. Four identical "USB2.0 Hub" rows are not a device list.
    • The mid-session fault banner stopped blaming you. It fired after two connection events, which one ordinary reconnect can produce on its own, and the wording implied you had done something. It now waits for four and describes what was seen without the accusation.
    • Cable Diagnostics stopped stuttering. It was running its own copy of every hardware watcher alongside the app's. One set now, shared.
    • Six more cables in the database, and cables reporting a placeholder vendor ID are no longer described as coming from a registered vendor.

    What to look at

    • The connected devices list, especially on a dock, a display with USB ports, or a daisy chain. Does the tree match what is physically on your desk? Does each device hang off the right thing?
    • Show hubs, then hide them again. Nothing should move between the two views.
    • If you have a daisy chain, the second device should now appear in that list at all. It never used to.
    • Anything WhatCable cannot work out is left where it always was, at the top of the chain, rather than guessed at. If something looks like it is in the wrong place, that is worth an issue.

    Known and deliberate

    The device count at the bottom of the popover still counts some hubs twice. USB 2.0 and USB 3.x are separate wires, so one hub chip registers with macOS twice, and I would rather leave a duplicate in the count than risk hiding a real device to remove it. Tracked, not forgotten.

    Thank you

    Every report, every odd cable, every "looks fine on my Mac" makes this better. Bugs get their own issue labelled beta, linked from the announcement thread.

  13. 1.3.0-beta.2

    Expand

    GitHub Release

    v1.3.0-beta.2: Beta build 2: sharper cable certification detection

    Beta build 2: sharper cable certification detection

    This is the second beta for the tester group, continuing 1.3.0. It bundles everything since v1.2.1, including all of beta.1. Nothing changes about licensing: use your normal Pro key.

    New since beta.1

    • More certified cables now show it. The "USB-IF certified" line was silently missing on a batch of cables that genuinely are certified (Anker, Belkin, Plugable, ZAGG and others), because the build never asked the registry about them. It does now. Thanks to the tester on discussion #475 whose Cable Matters / Lintes TB5 cable started the hunt.
    • "Certified but unlisted" is now its own case. A cable that advertises a certification ID USB-IF doesn't publish used to look identical to a cable with no ID at all. There's now a neutral line for it: "Carries a USB-IF certification ID (0x...) that isn't in the public registry". It's a fact about the ID, never a verdict on the cable. Certification is voluntary, and Apple's own cables land here.
    • Raw certification ID (XID) is now in the JSON output for anyone scripting against it.
    • Internal tidy-up behind the scenes, no user-facing change.

    Also in this build (from beta.1)

    • Offline cable provenance: the "USB-IF certified" line with manufacturer, read straight from the cable, no network lookup.
    • Front-port devices attributed correctly on desktop Macs.
    • Cleaner power and charging reporting: stale contract wattage no longer shown as live, and a charger that's plugged in but not being drawn from is explained rather than flagged as an error.
    • MagSafe counted on its own line in the "nothing plugged in" message.
    • Live port health counters landing on the right port.
    • Menu-bar popover height clamped to the screen.
    • Licensing help: a "lost your key" form on the support page, and the success page shows your key right after purchase.
    • DisplayPort: monitors at 1.62 Gbps (RBR) labelled correctly.
    • Translations: refreshed Italian (thanks @bovirus) and Traditional Chinese (thanks @jimmyorz).

    What to look at

    • If you have a certified cable that wasn't showing the "USB-IF certified" line before, check it does now.
    • If a cable shows the new "isn't in the public registry" line, that's expected, not a fault. Confirm it reads sensibly.
    • Everything from the beta.1 checklist still applies: the certified-cable line, desktop front ports, and the charging lines.
    • Anything that looks off gets its own issue labelled beta, linked from the announcement thread.

    Thank you

    To everyone testing: thank you. Every report, every "looks fine on my Mac", every odd cable you plug in and tell us about makes WhatCable better. We really appreciate the time anyone puts into this.

  14. 1.3.0-beta.1

    Expand

    GitHub Release

    v1.3.0-beta.1: Beta build: cable provenance, cleaner power reporting, and front-port fixes

    Beta build: cable provenance, cleaner power reporting, and front-port fixes

    This is a beta for the tester group. It bundles everything since v1.2.1. Nothing changes about licensing: use your normal Pro key.

    What's new

    • Offline cable provenance. Cables that carry a USB-IF certificate (XID) now show a "USB-IF certified" line with the manufacturer, read straight from the cable with no network lookup.
    • Front-port devices attributed correctly. On desktop Macs, a device on a built-in USB-only front port is now named against that port instead of being left unattached.
    • Cleaner power and charging reporting. A run of fixes to stop misleading charging lines: stale power-contract wattage is no longer reported as live, and a charger that's plugged in but not being drawn from is now explained rather than shown as an error (thanks to the M1 Pro/Max reporters).
    • MagSafe counted on its own line in the "nothing plugged in" message, instead of being lumped in with the USB-C ports.
    • Live port health counters that update as things change and land on the right port.
    • Menu-bar popover height is clamped to the screen so it can't run off the bottom.
    • Licensing help. A "lost your key" form on the support page, and the success page now shows your licence key right after purchase.
    • DisplayPort: monitors running at 1.62 Gbps (RBR), the lowest DisplayPort rate, are now labelled correctly.
    • Translations: refreshed Italian (thanks @bovirus) and Traditional Chinese (thanks @jimmyorz).

    What to look at

    • If you have a certified cable (many Thunderbolt/USB4 cables are), check the new "USB-IF certified" line reads right.
    • If you're on a desktop Mac, plug something into a front port and confirm it shows up attributed to that port.
    • Charging: confirm the power lines match reality, especially the charger-attached and "not drawing" cases.
    • Anything that looks off gets its own issue labelled beta, linked from the announcement thread.
  15. 1.2.1

    Expand

    OpenNavo editorial Added to Homebrew

    Fixes charger wattage and clarifies Intel and updater limitations.

    Power
    Fix wattage stuck at 3W when another USB-C device is attached.Explain a connected charger that is not the active power source.
    Setup
    Explain missing Intel port data and absent app bundles during update.
    Diagnostics
    Bound diagnostic probes and sanitize hardware text in CLI output.

    Fixes charger wattage and clarifies Intel and updater limitations.

    Power

    • Fix wattage stuck at 3W when another USB-C device is attached.
    • Explain a connected charger that is not the active power source.

    Setup

    • Explain missing Intel port data and absent app bundles during update.

    Diagnostics

    • Bound diagnostic probes and sanitize hardware text in CLI output.

    Selected exact publisher entries; hardware limitations remain explicit.

    Source: Official release notes.

  16. 1.2.1-beta.1

    Expand

    GitHub Release

    v1.2.1-beta.1: Beta: charger wattage fix, plus clearer Intel and updater messages

    Beta: charger wattage fix, plus clearer Intel and updater messages

    A beta for testers ahead of 1.2.1. Nothing about your Pro licence or how the app works changes. As always, please flag anything that looks off.

    What to test

    • Charger wattage no longer sticks at 3W when a second device is plugged in. Charging over MagSafe with a third-party adapter while also using a USB-C display (or any other device on a second port) could freeze the reading at "3W", even though the Mac was charging at full wattage. Unplugging the display used to be the only way to correct it. Now the real wattage shows regardless of what else is connected. Thanks @hinaloe for the clear report and the diagnostics (#443).

    • Intel Macs now say why the app can't work, instead of showing nothing. WhatCable relies on data Intel Macs don't expose, so it can't report cables on them. Instead of a blank window, Intel users now get a clear message explaining that (#407).

    • Power Monitor explains a connected-but-not-selected charger. When a charger is plugged in but the Mac isn't drawing from it, the monitor used to just spin. It now explains what's happening instead (#296).

    Also in this build

    • Updater gives clearer guidance when the app bundle is missing. If the running app was moved (for example, left in Downloads), the updater now explains what to do instead of failing with a cryptic error.
    • The window comes to the front in window mode when reopened (#419).
    • Traditional Chinese translation update, thanks @jimmyorz (#433).
    • The consent sheet and privacy policy now describe exactly what the diagnostic probes send.
  17. 1.2.0

    Expand

    GitHub Release Added to Homebrew

    v1.2.0: Better desktop USB-C port grouping, Thunderbolt tunnel paths, and a probing compatibility switch

    Better desktop USB-C port grouping, Thunderbolt tunnel paths, and a probing compatibility switch

    This release focuses on how WhatCable reads desktop Macs (mini, Studio) and Thunderbolt docks, plus a compatibility switch for Macs where deep USB probing misbehaves.

    What's new

    • Desktop built-in USB ports no longer group under a Thunderbolt dock. On a Mac mini or Studio, the machine's own front USB-C ports were being drawn as if they hung off a connected dock. They now show in their own "Built-in USB ports" section. Raised by @CronoCX in discussion #417.

    • Devices behind a dock on a front USB-C port now show up. Plugging a dock into a Mac mini or Studio front port used to list the dock's own hubs but drop everything plugged into the dock (drives, phones, audio). Those devices now appear, nested under the dock. Thanks @jimmyorz for the report and the testing (#430).

    • Connected devices tree roots under the Thunderbolt link (Pro). The device tree now shows the downstream Thunderbolt device with its live link speed at the top, plus tunnel-path attribution: which display or data tunnel each device is riding.

    • New "Skip deep USB probing" compatibility switch. A few KVM switches and hubs react badly to deep USB probing. Settings now has a switch to turn it off if probing ever stalls or misbehaves on your Mac; everything else keeps working. Thanks @asapuntz (#429).

    Under the hood

    • Test-kit probe hardening and a correction to how hardware identifiers are captured.
    • Internal correctness fixes to USB and power port join keys.
    • Cable database updates: several newly reported cables added, and a Thunderbolt adapter relabelled.
  18. 1.2.0-beta.2

    Expand

    GitHub Release

    v1.2.0-beta.2: Beta: dock devices on front USB-C ports now show up

    Beta: dock devices on front USB-C ports now show up

    Another beta for testers ahead of 1.2.0. Nothing about your Pro licence or how the app works changes. Same as before, please flag anything that looks off.

    What to test

    • Devices behind a dock on a desktop's front USB-C port now appear. On a Mac mini or Studio, plugging a dock into a front port used to show the dock's own hubs but drop everything plugged into the dock (drives, phones, audio). Those devices now show under "Built-in USB ports", nested under the dock. Devices on the rear Thunderbolt ports were never affected. Thanks @jimmyorz for the report and the detailed testing (#430).

    Also in this build

    • Cable database updates: several newly reported cables added, and a Thunderbolt adapter relabelled.
  19. 1.2.0-beta.1

    Expand

    GitHub Release

    v1.2.0-beta.1: Beta: desktop port grouping, tunnel paths, and a probing compatibility switch

    Beta: desktop port grouping, tunnel paths, and a probing compatibility switch

    This is a beta build for testers ahead of the 1.2.0 release. Nothing about your Pro licence or how the app works changes. Please run your usual setup and flag anything that looks off, especially around Thunderbolt docks and the Connected devices view.

    What to test

    • Desktop built-in USB ports no longer group under a Thunderbolt dock. On a Mac mini or Mac Studio, the machine's own front USB-C ports were being drawn as if they hung off a connected dock. They now show separately. Raised by @CronoCX in discussion #417.
    • Connected devices tree now roots under the Thunderbolt link. For Pro users, the device tree shows the downstream Thunderbolt device with its live link speed at the top, plus tunnel-path attribution: which display or data tunnel each device is riding.
    • New "Skip deep USB probing" compatibility switch. If deep USB probing ever stalls or misbehaves on your Mac, Settings now has a switch to turn it off. Everything else keeps working. Thanks @asapuntz (#429).

    Also in this build

    • Test-kit probe hardening and a correction to how hardware identifiers are captured.
    • Internal correctness fixes to port join keys.