As a fellow ham radio operator (callsign AD7HM), I may have an understanding of what the original poster is trying to do. Unfortunately, like OP, I’ve also floundered with getting my computer to control my radio. One of the problems is that - over the past 15 years - the USB device names visible within programs that we commonly used have been changed by changes to the Linux kernel - and not necessarily in an understandable way.
The lsusb command is good as far as it goes. The problem is that the way various ham radio programs refer to the interfaces does not align with what’s displayed by the lsusb command.
I was using my radio late yesterday, on my computer dedicated to ham radio control, and - for the first time in quite a while - I opened a radio control program called FLRig. FLRig accesses USB devices directly; other ham radio programs use a library called HamLib (technically, libHamLib) as their go-between.
On that computer, the output of the lsusb command is similar to the screen shots. My Icom IC-7610 ham radio transceiver has two USB bridge controllers - one to control receiver A (which is also the transmit side of the radio), and the other to control receiver B (receive-only) - as well as a USB sound card. The lsusb command shows these three devices.
In FLRig, however, the device name isn’t anything similar - if I recall correctly, I have the program talking to a device named /dev/ttyUSB0 to control the first receiver. (I’d have to take a screen shot off that computer to confirm my faulty personal RAM memory.)
I didn’t look at the program I use - CQRLog - for logging voice contacts. CQRLog uses HamLib. I also did not open WSJT (Weak Signal - Joe Taylor), a very popular program for digital contacts, which also uses HamLib - though realistically, I’d only need to look at one to understand how the USB device is entered.
What we hams need is a way to see what the actual /dev/ device to friendly name is. I honestly haven’t searched for any programs that would do that, as I solved my problem, and - until now - haven’t had anyone ask me how to set up Linux for radio control.
Oh…one other thing I’ve learned along the way. On some distros, there is a default group that is the only one allowed to access serial ports. I can’t remember if it’s the dialout group or another one - as I don’t change Linux distros unless something breaks. I’ve found that adding my user to that group solves a lot of “my computer won’t talk to my radio!” problems.