Not a Meshcore Device

[munsterrr]

2025-12-10 10:16:20,371 - meshtui - INFO - MeshTUI started - logging to ~/.config/meshtui/meshtui.log
2025-12-10 10:16:20,374 - meshtui - INFO - Attempting auto-connect...
2025-12-10 10:16:20,377 - meshtui - INFO - No connection args provided, attempting auto-detection...
2025-12-10 10:16:20,379 - meshtui - INFO - Scanning for serial devices...
2025-12-10 10:16:20,381 - meshtui.connection - INFO - Scanning for serial devices...
2025-12-10 10:16:20,400 - meshtui.connection - INFO - Found 2 serial ports, checking 1 ports...
2025-12-10 10:16:22,476 - meshtui.transport.serial - INFO - ✓ Found MeshCore device at /dev/ttyACM0: Heltec Tracker V2 vnightly-09c121e
2025-12-10 10:16:22,618 - meshtui.connection - INFO - ✓ MeshCore device found at /dev/ttyACM0
2025-12-10 10:16:22,621 - meshtui.connection - INFO - Quick scan found MeshCore device, stopping search
2025-12-10 10:16:22,624 - meshtui.connection - INFO - Scanned 1 devices, 1 are MeshCore devices
2025-12-10 10:16:22,626 - meshtui - INFO - Attempting to connect to: /dev/ttyACM0
2025-12-10 10:16:22,629 - meshtui.connection - INFO - Verifying /dev/ttyACM0 is a MeshCore device...
2025-12-10 10:16:22,671 - asyncio - ERROR - Task was destroyed but it is pending!
task: <Task pending name='None' coro=<EventDispatcher._process_events() done, defined at /home/munsterrr/.local/share/pipx/venvs/meshtui/lib/python3.13/site-packages/meshcore/events.py:157> wait_for=>
2025-12-10 10:16:23,166 - meshtui.connection - ERROR - /dev/ttyACM0 is not a MeshCore device
2025-12-10 10:16:23,169 - meshtui - INFO - Serial auto-connect failed, trying BLE...
2025-12-10 10:16:23,172 - meshtui.connection - INFO - Scanning for BLE devices (timeout: 2.0s)...
2025-12-10 10:16:23,226 - asyncio - ERROR - Task was destroyed but it is pending!
task: <Task pending name='None' coro=<EventDispatcher._process_events() done, defined at /home/munsterrr/.local/share/pipx/venvs/meshtui/lib/python3.13/site-packages/meshcore/events.py:157> wait_for=>
2025-12-10 10:16:23,805 - meshtui.connection - ERROR - BLE scan failed: ('No powered Bluetooth adapters found. Turn on Bluetooth and try again.', <BleakBluetoothNotAvailableReason.POWERED_OFF: 3>)
2025-12-10 10:16:23,808 - meshtui.connection - ERROR - No MeshCore devices found
2025-12-10 10:16:23,811 - meshtui - INFO - Auto-connect failed - no compatible devices found

[munsterrr]

Sorry. Copied and pasted then had to run. I'm not sure if it's because it is a nightly build or because the tracker v2

[mti-sk]

Hi,
I have same problem with my Seeed Studio SenseCAP T1000-E, companion BLE, fw version 1.11.0.
Using meshcore-cli working well.

[ekollof]

I'll see if I can reproduce this with my Heltecs this weekend

[ekollof]

Auto-connect was identifying the serial device during scan, then immediately identifying it again before opening the real connection. The second probe often lost the race with the still-settling port (your log shows Task was destroyed but it is pending! between the two steps).

Scan now hands the already-identified port to connect_serial(..., verify_meshcore=False), and identification waits a bit longer after disconnect so the port can settle.

This is on master. Workaround until the next release: start with an explicit port, e.g. meshtui --serial /dev/ttyACM0 (that path already skipped the extra verify).