FiPy - Device busy on Pysense, unable to interact with device

[Benedikt Chmielewski]

FiPy, Pysense

[Benedikt Chmielewski]

Adding some information to the topic so you know what is going on and can help me:
I have a FiPy device on a Pysense board. Right after recieving both I did a firmware update on both FiPy and Pysense. In Atom, it is stuck at the message Connecting to /dev/ttyACM3... and in VS Code the extension says the device is busy. Do you have any ideas, what I should try to do?
When connecting the device to my linux machine, this is what dmesg says:

[  +3.790516] usb 2-1.1: new full-speed USB device number 7 using ehci-pci
[  +0.100921] usb 2-1.1: New USB device found, idVendor=04d8, idProduct=f012, bcdDevice= 0.10
[  +0.000019] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000006] usb 2-1.1: Product: Pysense
[  +0.000004] usb 2-1.1: Manufacturer: Pycom
[  +0.000004] usb 2-1.1: SerialNumber: Py6493f1
[  +0.001934] cdc_acm 2-1.1:1.0: ttyACM3: USB ACM device

When executing lsusb, only the Pysense device shows up as:
Bus 002 Device 007: ID 04d8:f012 Microchip Technology, Inc. Pysense .

[Jonathan Brewer]

I have this problem too. Latest firmware applied to PySense 1.1 and LoPy4, doesn't work on Mac (attaches to VSCode as tty. not cu. and busy as tty) and on Linux I see it as ACM0 and it's always busy.

I've tried multiple instances of PySense 1.1 and LoPy4 - I have ten units that have been sitting in storage for a few years. None working now that the old tools are all gone.