Admin channel timeouts and unresponsiveness

Despite what mqtt might say about my nodes gps location (when they respect my static settings), they are both sitting within a foot of each other. Thats when I tested the --dest feature so I cant comment on range despite what my nodes look like on a map. I havent ventured out in the wild with these yet because I dont trust them and my cases are junk. Not knocking the project at all, I could invest in some nice cases and load the stable firmware.

Looks like some of you are using ----option ? Whats up with that? Ive only used --info and --reboot and always after --port because meshtastic on the mac isnt smart enough to detect the port.

Note that on my mac I have to escape the !

e@m firmware-1.2.28 % meshtastic --dest !050c217c --port /dev/cu.SLAB_USBtoUART --info
Connected to radio

INFO:root:Requesting preferences from remote node (this could take a while)
INFO:root:Requesting channel 0 info from remote node (this could take a while)
INFO:root:Requesting channel 1 info from remote node (this could take a while)
INFO:root:Requesting channel 2 info from remote node (this could take a while)
Preferences: { “lsSecs”: 300, “region”: “US”, “fixedPosition”: true }

Channels:
PRIMARY psk=default { “modemConfig”: “Bw125Cr48Sf4096”, “psk”: “AQ==” }
SECONDARY psk=secret { “psk”: “obfuscated”, “name”: “admin” }

Primary channel URL: https://www.meshtastic.org/d/#CgUYAyIBAQ
Complete URL (includes all channels): https://www.meshtastic.org/d/#obfuscated

e@m firmware-1.2.28 %