v1.4.0-beta.1 is up

[darrylmorley]

@jimmyorz @aguilaair @cannotcollide @Caruso8677 @Mostxlnt @aldobalducci @themadturk7

v1.4.0-beta.1 is up: https://github.com/darrylmorley/whatcable/releases/tag/v1.4.0-beta.1

This one is mostly about docks and device chains, so testers with docks are exactly who I need.

What changed

• Devices behind docks and hubs are now placed by the chain's actual topology, not by matching names. This fixes devices showing up under the wrong dock (issue Devices attributed to the wrong Thunderbolt device on a multi-dock chain #493).
• The "cable is limiting speed" verdict no longer blames the cable when a device further down the chain is the real limit (issue [Bug] Incorrectly reporting data speed limited by cable #507).
• The app writes its widget data far less often (once a minute at most, and not at all if you have no widgets).

What to do

1. Plug in your usual dock/hub setup, ideally with a few devices attached, and check the Connected devices tree: is everything under the right dock, at the right depth?
2. Run Contribute Diagnostic Data (Settings > Community) with the dock attached. This build captures new hub data I can't verify without real hubs, so a submission from each of you is worth a lot.
3. Anything odd, reply here. "Looks fine on my setup" is just as useful.

Thanks as ever.

[cannotcollide]

The OWC Express 1M2 issue is now resolved, so that's great!

I am still getting the same weird readout for that LaCie Rugged, though, since it still reports the TBT1 Drive as 40gbps

I will say that the cable itself is reporting correctly, since the adapter I use is a TBT2 to TBT3 adapter, so 20gbps. The actual incorrect report is the device, 40gbps rather than 10gbps

I just ran another diagnostic probe, so hopefully that should provide some insight. Let me know if there's anything else I can do!

[darrylmorley]

Thanks, that's exactly what I needed. The dock chain being right confirms the main fix, and your submission also proved the new hub data capture works, so double thanks.

The LaCie readout is a confirmed bug: old TB1/TB2 links share a speed code with Thunderbolt 3, and WhatCable currently reads that code as 40 Gbps. Your drive's own registry entry says it's TB1, so the fix is straightforward. Tracking it in #515, fix will be in the next beta.

[aguilaair]

Shared data, everything else looks fine to me :)

[darrylmorley]

@jimmyorz @aguilaair @cannotcollide @Caruso8677 @Mostxlnt @aldobalducci @themadturk7

v1.4.0-beta.2 is up: https://github.com/darrylmorley/whatcable/releases/tag/v1.4.0-beta.2

Two fixes on top of beta.1:

• Old Thunderbolt 1 and 2 devices no longer show as 40 Gbps, and their cables no longer get wrongly blamed for limiting speed (TB1/TB2-era device shown as 40 Gbps in Data Speed, cable wrongly blamed #515, thanks @cannotcollide).
• The charging banner now says "Battery full, not charging" or "Plugged in, charging on hold" instead of implying active charging when the Mac is drawing less than the charger offers (contributed by @YuriNachos, PR fix(charging): honour battery-full/charge-hold state in the macLimit diagnostic #514).

@cannotcollide if you can plug the LaCie Rugged back in on this build, the Data Speed panel should now show the device at 10 Gbps with no cable warning, and the port badge should match.

[cannotcollide]

Looks perfect, thank you!