Do you have the same issue if you follow the OP’s steps to reproduce it?
No. I have a USB hub connected to my XBOX. In the hub I have a USB memory stick (for captures), a Logitech unifying receiver (for my Logitech K400+ wireless keyboard and a Logitech mouse), a Thrustmaster rudder pedal, and the Honeycomb Alpha XPC yoke. The Bravo throttle quadrant is plugged into the Honeycomb XPC hub, which is plugged into the hub port on the Alpha.
The Bravo controls are recognized, but there are problems with some axis and button bindings. None of the LEDs illuminate.
Provide extra information to complete the original description of the issue:
I followed @Rmag’s excellent YT tutorial on configuring the Bravo (5 configurations for Honeycomb Bravo Throttle Quadrant in MSFS 2020. - YouTube). His tutorial is based on the PC version, which treats the Bravo as a separate peripheral, with the result that the axis and button numbering is different from the XPC version. The XPC version treats the Bravo as an extended switch and axis space of the Alpha. One consequence of this is that in the Options>Controls Options screen the device is illustrated as the combination of the Alpha, Bravo and Charlie (rudder pedals) devices, with none of the buttons or axes numbered. There is currently no correct numbering documentation.
Some buttons don’t scan at all. For example, if you configured @Rmag’s 4 Engine Jet and try to bind the thrust reverser on Throttle 1 to Throttle 1 Decrease, the button is not detected during a scan. You have to bind it by choosing Joystick Button 69 by name.
There is additional confusion regarding throttle axes. You must use, for example, Throttle 1 Axis (0-100%) rather than Throttle 1 Axis. The axes must be reversed too.
Most of the Autopilot features seem to work, but it is hard to use because none of the buttons illuminate. As noted by others, the values entered using the rotary knob may increase/decrease by small or large amounts randomly.
Although the AP functions like HDG and ALT work, there are no obvious bindings shown in the Options>Controls Option menus.
Since today’s mandatory update, the axes don’t animate on the Controls Option screen when you use them. However, the name of the axis does switch from light to dark and back to light.
The landing gear works, but the LEDs don’t illuminate. None of the annunciator lights work.
If relevant, provide additional screenshots/video: