Can't open WMR HMD via built-in HID support
Found thanks to @technobaboo - they have an in-progress WMR driver that wasn't working. Turns out num_hidraws is 0 and the monado-cli test thing doesn't show any hid stuff for the device (045e:0659) when there should be one on interface 2.
My dmesg says this on plug of an Odyssey+ related to the device we care about, which might be related:
[183775.779961] usb 1-7.1: new high-speed USB device number 17 using xhci_hcd
[183775.931047] usb 1-7.1: config 1 has an invalid interface number: 3 but max is 2
[183775.931048] usb 1-7.1: config 1 has an invalid interface number: 4 but max is 2
[183775.931049] usb 1-7.1: config 1 has no interface number 0
[183775.931049] usb 1-7.1: config 1 has no interface number 1
[183775.944048] usb 1-7.1: New USB device found, idVendor=045e, idProduct=0659, bcdDevice= 0.05
[183775.944049] usb 1-7.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[183775.944049] usb 1-7.1: Product: HoloLens Sensors
[183775.944050] usb 1-7.1: Manufacturer: Microsoft
[183775.944050] usb 1-7.1: SerialNumber: x
[183776.114974] hid-generic 0003:045E:0659.001E: hiddev8,hidraw13: USB HID v11.10 Device [Microsoft HoloLens Sensors] on usb-0000:02:00.0-7.1/input2
so it looks like the kernel is somewhat finding its hid stuff? In any case, OpenHMD can open it (via libhidapi), but monado can't via the prober.