At https://meshtastic.org/docs/software/python/cli/ --port, is described the possible USB ports i.e. /dev/ttyUSB0, /dev/cu.wchusbserial, COM4 etc. These are port names assigned by the operating system. I use Ubuntu. None of these names work in a bash script. To find a valid name, one needs to run lsusb to see the names delivered by the connected device. If you want to use --port aimed at a specific port, the form will be something like 303a:1001 or 10c4:ea60 [ Vendor:Product pair in hex]
The same applies to the web flasher. The drop-down list includes lots of OS-assigned names, but there will be device specific names, like USB JTAG/serial debug unit (ttyACM5) - Paired or CP2102 USB to UART Bridge Controller (ttyUSB1) - Paired
Documentation at https://meshtastic.org/docs/getting-started/serial-drivers/test-serial-driver-installation/ Linux is pretty much correct. It needs to have added: USB JTAG/serial debug unit (ttyACM5) - Paired
At https://meshtastic.org/docs/software/python/cli/ --port, is described the possible USB ports i.e. /dev/ttyUSB0, /dev/cu.wchusbserial, COM4 etc. These are port names assigned by the operating system. I use Ubuntu. None of these names work in a bash script. To find a valid name, one needs to run lsusb to see the names delivered by the connected device. If you want to use --port aimed at a specific port, the form will be something like 303a:1001 or 10c4:ea60 [ Vendor:Product pair in hex]
The same applies to the web flasher. The drop-down list includes lots of OS-assigned names, but there will be device specific names, like USB JTAG/serial debug unit (ttyACM5) - Paired or CP2102 USB to UART Bridge Controller (ttyUSB1) - Paired
Documentation at https://meshtastic.org/docs/getting-started/serial-drivers/test-serial-driver-installation/ Linux is pretty much correct. It needs to have added: USB JTAG/serial debug unit (ttyACM5) - Paired