Hi!
There is a bunch of arduino MEGA256 - esp8266. It works fine, correctly sends data to the server via MQTT. It is required to remake on TCP-socket. I do as in the example, in debug I see the following output:
185270> SOCKET #0: send dataLen=135 socketData=#A0:20:A6:02:20:9C
185270> #t2#10.7
185270> #h2#63.5
185270> #p2#763.9
185270> #v2#3.04
185270> #t1#-12.5
185270> #h1#84.8
185271> #v1#2.95
185271> #h0#45.6
185271> #t0#21.5
185271> #l0#29
185271> #tr#20.0
185271> #D1#94
185271> #D2#107
185271> ##�n�?(
185271> SOCKET #0: Create connection to ip 185.245.187.136:8283
185271> SOCKET #0: Connect to ip 185.245.187.136:8283
187969> HTTP GET /console/text: 200, 107ms, h=17424
188577> HTTP GET /console/text: 200, 47ms, h=17424
189268> SLIP: start or end len=0 inpkt=0
189268> SLIP: start or end len=10 inpkt=1
189268> cmdParsePacket: cmd=4 argc=0 value=0
189269> cmdExec: Dispatching cmd=WIFI_STATUS
189269> cmdResponse: cmd=2 val=2 argc=0
191558> SOCKET #0: conn reset, err=-11
No data is sent to the server. Confusing extra bytes "�n�?(" after "##", they are not in the original packet. "##" - is the end of packet.
The python test script delivers data to the server normally. Tried with firmware esp-link v3.0.14-g963ffbb and v3.2.47-g9c6530d.
El-client - last release. What is my problem? err=-11 - is normally closed session?
Hi! There is a bunch of arduino MEGA256 - esp8266. It works fine, correctly sends data to the server via MQTT. It is required to remake on TCP-socket. I do as in the example, in debug I see the following output: 185270> SOCKET #0: send dataLen=135 socketData=#A0:20:A6:02:20:9C 185270> #t2#10.7 185270> #h2#63.5 185270> #p2#763.9 185270> #v2#3.04 185270> #t1#-12.5 185270> #h1#84.8 185271> #v1#2.95 185271> #h0#45.6 185271> #t0#21.5 185271> #l0#29 185271> #tr#20.0 185271> #D1#94 185271> #D2#107 185271> ##�n�?( 185271> SOCKET #0: Create connection to ip 185.245.187.136:8283 185271> SOCKET #0: Connect to ip 185.245.187.136:8283 187969> HTTP GET /console/text: 200, 107ms, h=17424 188577> HTTP GET /console/text: 200, 47ms, h=17424 189268> SLIP: start or end len=0 inpkt=0 189268> SLIP: start or end len=10 inpkt=1 189268> cmdParsePacket: cmd=4 argc=0 value=0 189269> cmdExec: Dispatching cmd=WIFI_STATUS 189269> cmdResponse: cmd=2 val=2 argc=0 191558> SOCKET #0: conn reset, err=-11 No data is sent to the server. Confusing extra bytes "�n�?(" after "##", they are not in the original packet. "##" - is the end of packet. The python test script delivers data to the server normally. Tried with firmware esp-link v3.0.14-g963ffbb and v3.2.47-g9c6530d. El-client - last release. What is my problem? err=-11 - is normally closed session?