Failing to use TCP proxy mode "Client disconnected"

[arthurlutz]

Server side

2026-03-09 17:00:39,022 - meshcore.proxy - DEBUG - Backend → TCP: 8830a2[snip]404 (154 bytes)
2026-03-09 17:00:39,026 - meshcore.proxy.tcp - DEBUG - No clients connected, frame not sent
2026-03-09 17:00:52,342 - meshcore.proxy.tcp - INFO - New client connected: ('REDACTED_CLIENT_IP', 36880)
2026-03-09 17:00:52,357 - meshcore.proxy.tcp - DEBUG - Received frame from ('REDACTED_CLIENT_IP', 36880): 13 bytes
2026-03-09 17:00:52,363 - meshcore.proxy - DEBUG - TCP → Backend: 010snip69 (13 bytes)
2026-03-09 17:00:52,369 - meshcore.proxy.serial - DEBUG - Sending frame: 3c0d000snip3636c69 (13 bytes payload)
2026-03-09 17:00:52,388 - meshcore.proxy - DEBUG - Backend → TCP: 05011616e6ca39snip67656e6365 (79 bytes)
2026-03-09 17:00:52,394 - meshcore.proxy.tcp - DEBUG - Broadcasting frame to 1 client(s): 79 bytes
2026-03-09 17:00:57,349 - meshcore.proxy.tcp - INFO - Client disconnected: ('REDACTED_CLIENT_IP', 36880)

Client side :

2026-03-09 18:00:51,955 - meshtui - INFO - MeshTUI started - logging to ~/.config/meshtui/meshtui.log
2026-03-09 18:00:51,967 - meshtui - INFO - Attempting auto-connect...
2026-03-09 18:00:51,967 - meshtui - INFO - Connecting to TCP device: REDACTED_SERVER_IP:5000
2026-03-09 18:00:51,968 - meshtui.connection - INFO - Connecting to TCP device: REDACTED_SERVER_IP:5000
2026-03-09 18:00:52,153 - meshcore - INFO - TCP Connection started
2026-03-09 18:00:57,156 - meshcore - ERROR - No response from meshcore node, disconnecting
2026-03-09 18:00:57,157 - meshtui.connection - ERROR - TCP connection failed: 'NoneType' object has no attribute 'commands'
2026-03-09 18:00:57,158 - meshtui - ERROR - Failed to connect to specified TCP device: REDACTED_SERVER_IP:5000

Again maybe related to #9 with slow hardware. Maybe there could be a timeout setting that needs to be higher.

[reezmaize]

Came here to report the same isue. My logs are identical to the above. Worth noting this also happens when attempting connection via meshcore-cli. Tested on two different companion devices

[ekollof]

This was not a timeout or slow-hardware issue. The radio answered the APPSTART command in ~36ms (the 79-byte 0x05 SELF_INFO frame in your proxy log). MeshTUI never parsed it.

MeshCore companion framing is:

• host → device: 0x3C
• device → host: 0x3E

meshcore.tcp_cx.handle_rx() looks for 0x3E. The proxy re-wrapped serial replies as 0x3C, so the client discarded them, waited for the handshake, then create_tcp() returned None and MeshTUI crashed with 'NoneType' object has no attribute 'commands'.

That also matches the report that meshcore-cli failed the same way (same library, same framing).

Fix on master: the proxy now sends device→host frames as 0x3E, serial RX syncs on 0x3E/0x3C, and a failed TCP handshake is reported instead of crashing.

After updating, restart meshcore-tcp-proxy and try meshtui --tcp HOST --port 5000 again.