Detecting serial port and workarounds

I've got an Arduino device hooked up and everything is working great. It's usually reporting on port c, but every once in a while it shows up on a different port (usually d, but I'm also not sure what to expect with other computers), so every time I open the patch I have to print to console and manually ensure the correct port is set to go into the serial object. I was hoping to build an autodector that reads from the console and sets the serial object to the correct port as printed to the console, not only to save time when initializing the patch after opening but to build out a way to future-proof the patch for if it runs on a different computer and the Arduino is showing up on a different port.

It doesn't appear like there is a way to read data from the console—though let me know if I'm wrong. So in the meantime, I tried setting up a few different workarounds. My first attempt was to use the different outlets of serial object and combinations of "print" or "getport" messages. The problem here is that even with unpacking, I'm not getting the actual port letter, only the unpacked position of the correct message ("usbmodem1101"). As in, the console shows:

serial: port a: wlan-debug

serial: port b: Bluetooth-Incoming-Port

serial: port c: usbmodem1101

but the unpacked message within the patch coming from printing is simply:

wlan-debug

Bluetooth-Incoming-Port

usbmodem1101

The order is correct, but it does not specify the port. Which means that with some careful [sel] objects I can route towards sending the correct port to the serial object. As in, after unpacking, if the modem message comes out the 4th outlet, a [sel usbmodem1101] object spits out a "port c" message into the serial object. If it comes out of the 5th outlet, a copy of the sel object bangs to a "port d" message into the serial object, etc.

The problem with this is that it would require multiple possible port setups (all 26 letters, to be insanely safe), and if the "usbmodem1101" ever were to change (maybe a firmware update to Arduino? maybe it reads differently on different computers/operating systems?), this detection falls apart. It seems somewhat janky in general though, I somehow do not trust this setup, it seems easy to trip up and not work consistently, especially because I have to set the metro AFTER the correct port is initialized and I think there is a more compact and efficient way to do this.

My theory for what might be a safer solution: because the Arduino sends a gazillion numbers a second when the correct port is open, what if I have a loadbang on this little detector widget, and the widget says "if more than 1 second passes without another piece of data coming in after the initial bang, cycle to the next port message and test this again. if a bunch of data segments come in, this cycle completes because we're on the correct port." (I feel like the [change] object might be helpful here?)

One problem with this is that if the Arduino stutters for a second, the whole patch would basically come to a halt and need to be reinitialized? Not sure if this is a legit concern with Arduino, but maybe not important to consider for now.

So really, the main problem is that I cannot wrap my head around how to build the above concept. The full flow is: Because I know Max cannot detect nothing, a loadbang is necessary to get something started. I've got two messages ("port c" and "port d") going into the serial object. I need to detect if that loadbang is followed by anything coming out of the serial object—if no, send one of the port messages into the serial object. If no again, try the other. Keep trying each until we get a yes, then STOP.

Any ideas on how to build this little module and/or if there is a better way to do serial port detection? Thanks so much in advance yall!