26.0 broke uhubctl, plus USB weirdness

[thebart]

I guess I was bored and decided to update from Sonoma to Tahoe. It broke uhubctl. Now I get this

Current status for hub 1 [0bda:5483 Generic 4-Port USB 2.0 Hub, USB 2.10, 5 ports, ppps]
Port 1: 0100 power
Port 2: 0503 power highspeed enable connect []
Port 3: 0100 power
Port 4: 0303 power lowspeed enable connect []
Port 5: 0100 power
Current status for hub 1 [0bda:5483 Generic 4-Port USB 2.0 Hub, USB 2.10, 5 ports, ppps]
Port 1: 0503 power highspeed enable connect []
Port 2: 0103 power enable connect []
Port 3: 0100 power
Port 4: 0503 power highspeed enable connect []
Port 5: 0503 power highspeed enable connect []

1) it doesn't distinguish between my two hubs. 2) No device has any description. 3) I can't control any device.

Prior to Tahoe, the USB ports stayed powered on when I put MacOS to sleep, so my (wired) keyboard stayed lit. That's why I've been using uhubctl, to power off/on the port the keyboard is connected to when the Mac sleeps/wakes.

With Tahoe, the USB ports power OFF upon sleep and they don't power back on upon wake. So my keyboard is non-functional after waking up. I have to unplug/replug it.

For the time being, I plug it into the monitor so I only have to turn the monitor on/off. Before I just let the monitor sleep and never turned it off (it uses <1w on standby).

Anyone else here uses uhubctl? Is it still working for you?

Is there a setting somewhere that changes it back to the old behavior?

Thanks

 

[thebart]

Good news: someone made a patch for this issue

libusb_get_port_numbers returns nothing on some macOS versions · Issue #1661 · libusb/libusb

The name of the IORegistry port property is not consistent across macOS versions: it's port on some, usb-port-number on others. (Run ioreg -c AppleUSB30HubPort or ioreg -c AppleUSB20HubPort to show...

github.com