meshcore-cli over TCP via meshcore-proxy receives SELF_INFO in proxy log, but cli disconnects with "No response from meshcore node" #14
Description
Environment
• meshcore-cli: v1.5.4
• meshcore-proxy: 0.4 - First Friday
• Connection type: TCP via meshcore-proxy
• Proxy target is a companion/client node, not a repeater
What I expected
meshcore-cli should connect through meshcore-proxy over TCP and execute commands such as infos or ver.
What happens instead
meshcore-cli connects, sends appstart, then disconnects with:
ERROR:meshcore:No response from meshcore node, disconnecting
At the same time, meshcore-proxy shows that it forwarded CMD_APPSTART and successfully received SELF_INFO from the node.
CLI command
docker compose run --rm meshcore-cli -D -t 10.0.0.48 -p 5000 infos
meshcore-cli output
DEBUG:meshcore:connection established
INFO:meshcore:TCP Connection started
DEBUG:meshcore:Connected successfully:
DEBUG:meshcore:Sending appstart command
DEBUG:meshcore:Sending raw data: bytearray(b'\x01\x03 mccli')
DEBUG:meshcore:sending pkt : b'<\r\x00\x01\x03 mccli'
DEBUG:meshcore:Dispatching event: EventType.CONNECTED, {'connection_info': }, {}
DEBUG:meshcore:data received
ERROR:meshcore:No response from meshcore node, disconnecting
DEBUG:meshcore:TCP Connection closed
DEBUG:meshcore:TCP server closed the connection
meshcore-proxy output
INFO:meshcore_proxy.proxy:Client connected: ('10.0.0.142', 55079)
-> CMD_APPSTART: version=3 | app=mccli
<- SELF_INFO: name=VM Žvėrynas 31 | type=client | public_key=312a306c7123... | tx_power=22 | freq_mhz=869.62 | bw_khz=62.50 | sf=8 | cr=8
INFO:meshcore_proxy.proxy:Client disconnected: ('10.0.0.142', 55079)
<- LOG_DATA
<- LOG_DATA
<- LOG_DATA
<- LOG_DATA
Notes
• TCP path is working.
• Proxy is working.
• The node responds and identifies itself as type=client.
• This does not look like a repeater-mode mistake.
• It looks like the CLI receives bytes but does not accept them as a valid response after appstart.
Question
Is there a known compatibility issue between meshcore-cli v1.5.4 and meshcore-proxy 0.4, or a framing/parsing issue in the TCP path after SELF_INFO?