USB-C hubs and my slow descent into madness (2021)
USB‑C hubs, docks and cables promise a single universal connector, but users report a maze of incompatibilities, under‑specced hardware and flaky behavior, especially around power delivery, video output and Ethernet. Many devices and cables violate or only partially implement the USB‑C/PD spec, leading to issues like devices that only charge with their original cable, hubs that reset attached equipment when power is renegotiated, and Realtek‑based network ports that fail under load or across OSes. Commenters gravitate toward expensive Thunderbolt docks and monitor‑integrated hubs as more reliable options, while lamenting poor labeling and testing tools that leave most people guessing what their existing USB‑C cords and accessories can actually do.
One‑cable dream vs messy reality
- Many comments echo the article’s theme: people want a single USB‑C cable for power, display, network, and peripherals, but get there only after multiple failed hubs/docks.
- DisplayLink-based docks are seen as a compromise: they enable many monitors (useful for M1 Macs) but introduce compression artifacts and DRM/streaming issues.
- Thunderbolt 3/4/USB4 docks are praised as the only consistently reliable option, but they’re expensive, often need proprietary power bricks, and sometimes still have firmware or refresh‑rate quirks.
- Monitor-integrated USB‑C hubs and daisy-chained displays are viewed as the cleanest desk setup, but are limited by macOS (no DP MST on some MacBooks, scaling options).
OEM/ODM reality and Realtek skepticism
- Multiple hubs turn out to be the same OEM “Goodway” design rebranded at different prices. This is described as standard industry practice, not exceptional.
- Realtek USB NICs are frequently blamed for flakiness (driver issues, feature gaps, weird failure modes like loops or pause frames killing networks), especially on Linux/BSD.
- Others argue the silicon is often fine and the real problem is low-end manufacturers cutting corners on integration and firmware.
USB‑C spec complexity and broken devices
- Long subthread on devices that only charge with their original USB‑C cable: explanation centers on missing or incorrect CC resistors and lack of USB‑C “dead battery mode,” making them depend on out‑of‑spec A‑to‑C cables that always supply 5V.
- Some note that many products (including well-known brands and even Raspberry Pi revisions) have shipped with non‑compliant USB‑C implementations.
- Debate over whether USB‑PD’s “0V by default until negotiated” is a design mistake or necessary to avoid dangerously tying two power sources together.
Power negotiation and PD hubs/chargers
- USB‑PD power strips/hubs often momentarily cut power to all ports when a new device is plugged in, hard‑rebooting things like Raspberry Pis.
- People report this behavior even on modern GaN chargers from major brands; opinions differ on whether it’s unavoidable or just poor design.
- Some call for user-selectable behavior (e.g., a switch to favor existing loads vs new ones).
Cable capabilities, labeling, and testing
- A recurring frustration is not knowing what any given USB‑C cable supports (data rate, video, PD wattage, Thunderbolt).
- Suggested mitigations: personal labeling systems, USB testers/analyzers, and relying only on clearly logo‑marked cables.
- Some see variable cable capabilities as a spec failure; others argue it’s a necessary tradeoff for backward compatibility, cost, and cable length flexibility.
Hub design gaps
- Many consumer hubs provide mostly USB‑A and just one usable USB‑C data port, contradicting the “USB‑C everywhere” vision.
- A few niche products (USB‑C–only hubs, Thunderbolt/USB4 hubs with multiple downstream C ports) are mentioned, but they’re rare or pricey.
- There is interest in more integrated solutions: docks in monitors, desks, floor boxes, and better “USB power strips” for charging only.