- retrofit.RetrofitError: sendto failed: ECONNRESET (Connection reset by peer) #1027
- Comments
- lakshay148 commented Aug 24, 2015
- ECONNRESET (Connection reset by peer) #5
- Comments
- mree58 commented Jan 16, 2018
- martin-ger commented Jan 16, 2018
- mree58 commented Jan 17, 2018 •
- MasyaShu commented Jan 19, 2018 •
- MasyaShu commented Jan 19, 2018
- MasyaShu commented Jan 19, 2018 •
- martin-ger commented Jan 19, 2018
- MasyaShu commented Jan 19, 2018
- mree58 commented Jan 19, 2018
- martin-ger commented Jan 19, 2018
- MasyaShu commented Jan 19, 2018
- martin-ger commented Jan 20, 2018
- MasyaShu commented Jan 22, 2018
- MasyaShu commented Jan 22, 2018
- MasyaShu commented Jan 22, 2018
- mree58 commented Jan 22, 2018
- martin-ger commented Jan 22, 2018
- mree58 commented Jan 22, 2018
- martin-ger commented Jan 22, 2018
- MasyaShu commented Jan 23, 2018
- MasyaShu commented Jan 23, 2018
retrofit.RetrofitError: sendto failed: ECONNRESET (Connection reset by peer) #1027
Comments
lakshay148 commented Aug 24, 2015
I am uploading images with retrofit multipart and continuously getting the following exception :
Caused by: retrofit.RetrofitError: sendto failed: ECONNRESET (Connection reset by peer)
at retrofit.RestAdapter$RestHandler.invokeRequest(RestAdapter.java:395)
at retrofit.RestAdapter$RestHandler.invoke(RestAdapter.java:240)
at java.lang.reflect.Proxy.invoke(Proxy.java:397)
at $Proxy2.uploadImage(Unknown Source)
at gaadi.evaluator.com.retrofit.RetrofitRequest.makeImageUploadRequest(RetrofitRequest.java:26)
at gaadi.evaluator.com.service.ImageUploadServiceRevamp.onHandleIntent(ImageUploadServiceRevamp.java:73)
. 4 more
Caused by: java.net.SocketException: sendto failed: ECONNRESET (Connection reset by peer)
at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:546)
at libcore.io.IoBridge.sendto(IoBridge.java:515)
at java.net.PlainSocketImpl.write(PlainSocketImpl.java:504)
at java.net.PlainSocketImpl.access$100(PlainSocketImpl.java:37)
at java.net.PlainSocketImpl$PlainSocketOutputStream.write(PlainSocketImpl.java:266)
at okio.Okio$1.write(Okio.java:78)
at okio.AsyncTimeout$1.write(AsyncTimeout.java:155)
at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.java:176)
at okio.RealBufferedSink.write(RealBufferedSink.java:46)
at com.squareup.okhttp.internal.http.HttpConnection$FixedLengthSink.write(HttpConnection.java:302)
at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.java:176)
at okio.RealBufferedSink$1.write(RealBufferedSink.java:198)
at retrofit.mime.TypedFile.writeTo(TypedFile.java:78)
at retrofit.mime.MultipartTypedOutput$MimePart.writeTo(MultipartTypedOutput.java:54)
at retrofit.mime.MultipartTypedOutput.writeTo(MultipartTypedOutput.java:144)
at retrofit.client.OkClient$1.writeTo(OkClient.java:88)
at com.squareup.okhttp.internal.http.HttpEngine$NetworkInterceptorChain.proceed(HttpEngine.java:898)
at com.squareup.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:760)
at com.squareup.okhttp.Call.getResponse(Call.java:274)
at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:230)
at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:201)
at com.squareup.okhttp.Call.execute(Call.java:81)
at retrofit.client.OkClient.execute(OkClient.java:53)
at retrofit.RestAdapter$RestHandler.invokeRequest(RestAdapter.java:326)
. 9 more
Caused by: android.system.ErrnoException: sendto failed: ECONNRESET (Connection reset by peer)
at libcore.io.Posix.sendtoBytes(Native Method)
at libcore.io.Posix.sendto(Posix.java:176)
at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
at libcore.io.IoBridge.sendto(IoBridge.java:513)
. 31 more
The adapter i am using is :
public static RestAdapter getRestAdapter(Context context) <
String url = Utils.getWebServiceURL(context);
String urlBase = url.substring(0, url.lastIndexOf(«/»));
Interface method used for making request is as follows :
@multipart
@post(«/
public ImageUploadResponse uploadImage(@path(«path») String path, @part(Constants.EVALUATION_DATA) String map, @part(«certImg») TypedFile file);
Call made to this interface method is as follows :
TypedFile file = new TypedFile(«multipart/form-data», new File(imagePath));
String url = Utils.getWebServiceURL(UILApplication.getInstance());
return requestInterface.uploadDocumentImage(path, jsonParams, file);
Could not find a solution to this on stackoverflow.
The text was updated successfully, but these errors were encountered:
Источник
ECONNRESET (Connection reset by peer) #5
Comments
mree58 commented Jan 16, 2018
Thanks for this great work firstly, but I have some problem with it. Let me try to explain it please. I can connect successfully to the broker, and with latest release I can successfully disconnect I suppose. But after a couple of connect-disconnect sequence (usually 4-6) ESP is not accepts new connections. It throws this immediatelly when I try to connect :
java.net.SocketException: recvfrom failed: ECONNRESET (Connection reset by peer)
Until I restart (power off then on) the ESP, I cannot connect to the mqtt broker from any client on any platform
#using the latest commit of this library as a broker
#using the paho.mqtt.android as a client (tried on other platforms as well, client is not problem I think)
The text was updated successfully, but these errors were encountered:
martin-ger commented Jan 16, 2018
Cannot reproduce the error. Using mosquitto_sub and mosquitto_pub I can connect and disconnect (from my laptop) without any obvious problem.
What exactly is your test-setup with paho.mqtt.android (or another client with problems)?
mree58 commented Jan 17, 2018 •
Thanks for your reply. I builded the example project that they provided (only disconnect() function called on onDestroy method, ip and port changed also ofcourse) :
The log output from client side was written in first message. I can record video or prepare sample mobile app for you in case you need.
MasyaShu commented Jan 19, 2018 •
Hello. I also encountered such a problem.
uMQTTBroker is installed on one ESP.
To another PubSubClient.
If the client connects to the server for the first time, then everything is in order. When the client is rebooted, the connection returns an error:
-4 : MQTT_CONNECTION_TIMEOUT — the server didn’t respond within the keepalive time
The error is saved before the uMQTTBroker reboot.
MasyaShu commented Jan 19, 2018
Solved a problem:
client.disconnect ();
// Wait 15 seconds before retrying
delay (15000);
MasyaShu commented Jan 19, 2018 •
martin-ger commented Jan 19, 2018
Could you send me the client’s code? Guess, it has to do with session handling. For some reason the server rejects the CONN request (probably, because the session is still there?)
MasyaShu commented Jan 19, 2018
// Update these with values suitable for your network.
const char* ssid = «AU_01_WiFi»;
const char* password = «»;
long lastReconnectAttempt = 0;
WiFiClient espClient;
PubSubClient client(espClient);
long lastMsg = 0;
char msg[50];
int value = 0;
IPAddress local_IP(192,168,4,22);
void setup() <
pinMode(BUILTIN_LED, OUTPUT); // Initialize the BUILTIN_LED pin as an output
Serial.begin(9600);
setup_wifi();
client.setServer(local_IP, 1602);
client.setCallback(callback);
>
delay(10);
// We start by connecting to a WiFi network
Serial.println();
Serial.print(«Connecting to «);
Serial.println(ssid);
while (WiFi.status() != WL_CONNECTED) <
delay(500);
Serial.print(«.»);
>
Serial.println(«»);
Serial.println(«WiFi connected»);
Serial.println(«IP address: «);
Serial.println(WiFi.localIP());
>
void callback(char* topic, byte* payload, unsigned int length) <
Serial.print(«Message arrived [«);
Serial.print(topic);
Serial.print(«] «);
for (int i = 0; i 2000) <
lastMsg = nowT;
++value;
snprintf (msg, 75, «hello world #%ld», value);
Serial.print(«Publish message: «);
Serial.println(msg);
client.publish(«outTopic», msg);
>
mree58 commented Jan 19, 2018
I think, it could be the same problem. What do you think, is it the same problem ? Here is the video and the sample app :
martin-ger commented Jan 19, 2018
Thanks — probably it is the same problem — no time today, will try to look into it over the weekend.
MasyaShu commented Jan 19, 2018
Thank you. I would be very grateful if I can get rid of this problem.
martin-ger commented Jan 20, 2018
Think, I found the problem. Introduced it, when trying to fix issue #3
It failed to clean up old sessions from the same client. Should be fixed now.
MasyaShu commented Jan 22, 2018
Thank you, it’s getting better. Now after reboot it is stably connected from the second time: https://image.prntscr.com/image/8HFba0bRQaauzAEEUYBQoQ.png
If the client uses «client.disconnect ();», then the connection does not exist.
MasyaShu commented Jan 22, 2018
Now the client turns on, sends a message and falls asleep, after 5 seconds wakes up, sends a message again. After he wakes up the connection to the broker occurs at the second attempt.
I tried to disconnect from the broker before going to sleep: «client.disconnect ()», in this version it could not connect a second time.
MasyaShu commented Jan 22, 2018
After it increased the sleep time (30 seconds), it started from the first time: https://image.prntscr.com/image/calH1rC2SZaT7mbgo8P1Lw.png
mree58 commented Jan 22, 2018
Same result for me. Same error occurred, which could be seen in the video that I send.
martin-ger commented Jan 22, 2018
Let me try to understand the setup:
- you are directly connected to the ESP as AP? (or are both, client and broker STAs of a different WiFi AP?)
- the client is hard rebooted (and or correctly disconnected via MQTT?)
- you are using the clean-session flag during connection?
mree58 commented Jan 22, 2018
|
martin-ger commented Jan 22, 2018
Tried to reproduce the problem, somewhat hard.
With the ESP as AP and IoT MQTT Dashboard (https://play.google.com/store/apps/details?id=com.thn.iotmqttdashboard) as sample client on Android it just works fine.
Pubsubclient on the AP for me doesn’t even try to connect. (I don’t see any TCP connect request on the ESP).
Could you help me an try the following on you setup:
in «mqtt_server.c» in the library please uncomment the two lines:
40: #undef MQTT_INFO
41: #define MQTT_INFO os_printf
And add
Serial.setDebugOutput(true);
in your Arduino code?
This enables debug output in the MQTT server. The output might give some insight into what’s going on.
MasyaShu commented Jan 23, 2018
Starting MQTT broker
Starting MQTT server on port 1602
MQTT_ClientCon_connected_cb(): Client connected
MQTT: InitClientCon
MQTT_ClientCon_recv_cb(): 33 bytes of data received
MQTT: TCP: data received 33 bytes (State: 15)
MQTT: total_len: 33
MQTT: message_type: 1
MQTT: Connect received, message_len: 33
MQTT: Connect flags 2
MQTT: Keepalive 60
MQTT: Client id «gghdrj1516683805700»
MQTT: Server task activated — state 20
MQTT: Sending, type: 2, id: 0000
MQTT_ClientCon_sent_cb(): Data sent
MQTT_ClientCon_recv_cb(): 15 bytes of data received
MQTT: TCP: data received 15 bytes (State: 20)
MQTT: total_len: 15
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 15
MQTT: Message id 1
MQTT: Subscribed topic /DVP/123 QoS 0
MQTT: Subscribe successful
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0001
MQTT_ClientCon_recv_cb(): 96 bytes of data received
MQTT: TCP: data received 96 bytes (State: 20)
MQTT: total_len: 17
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 17
MQTT: Message id 2
MQTT: Subscribed topic outTopic/# QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 13
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 13
MQTT: Message id 3
MQTT: Subscribed topic /DVP/# QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 15
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 15
MQTT: Message id 4
MQTT: Subscribed topic mybroker QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 12
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 12
MQTT: Message id 5
MQTT: Subscribed topic ggggg QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 18
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 18
MQTT: Message id 6
MQTT: Subscribed topic mybroker/sv QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 21
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 21
MQTT: Message id 7
MQTT: Subscribed topic MyBroker/count QoS 0
MQTT: Subscribe successful
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683805700
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0002
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683805700
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0003
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683805700
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0004
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683805700
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0005
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683805700
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0006
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683805700
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0007
MQTT_ClientCon_sent_cb(): Data sent
MQTT_ClientCon_recv_cb(): 2 bytes of data received
MQTT: TCP: data received 2 bytes (State: 20)
MQTT: total_len: 2
MQTT: message_type: 14
MQTT: receive MQTT_MSG_TYPE_DISCONNECT
MQTT: ServerDisconnect
MQTT_ClientCon_discon_cb(): client disconnected
MQTT: DeleteClientCon
MQTT: Broker already disconnecting
MQTT: Server task activated — state 9
MQTT: Client disconnected
MQTT: DeleteClientCon
MQTT_ClientCon_connected_cb(): Client connected
MQTT: InitClientCon
MQTT_ClientCon_recv_cb(): 33 bytes of data received
MQTT: TCP: data received 33 bytes (State: 15)
MQTT: total_len: 33
MQTT: message_type: 1
MQTT: Connect received, message_len: 33
MQTT: Connect flags 2
MQTT: Keepalive 60
MQTT: Client id «gghdrj1516683823586»
MQTT: Server task activated — state 20
MQTT: Sending, type: 2, id: 0000
MQTT_ClientCon_sent_cb(): Data sent
MQTT_ClientCon_recv_cb(): 15 bytes of data received
MQTT: TCP: data received 15 bytes (State: 20)
MQTT: total_len: 15
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 15
MQTT: Message id 1
MQTT: Subscribed topic /DVP/123 QoS 0
MQTT: Subscribe successful
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0001
MQTT_ClientCon_recv_cb(): 96 bytes of data received
MQTT: TCP: data received 96 bytes (State: 20)
MQTT: total_len: 17
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 17
MQTT: Message id 2
MQTT: Subscribed topic outTopic/# QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 13
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 13
MQTT: Message id 3
MQTT: Subscribed topic /DVP/# QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 15
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 15
MQTT: Message id 4
MQTT: Subscribed topic mybroker QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 12
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 12
MQTT: Message id 5
MQTT: Subscribed topic ggggg QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 18
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 18
MQTT: Message id 6
MQTT: Subscribed topic mybroker/sv QoS 0
MQTT: Subscribe successful
MQTT: Get another received message
MQTT: total_len: 21
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 21
MQTT: Message id 7
MQTT: Subscribed topic MyBroker/count QoS 0
MQTT: Subscribe successful
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683823586
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0002
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683823586
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0003
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683823586
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0004
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683823586
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0005
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683823586
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0006
MQTT_ClientCon_sent_cb(): Data sent
MQTT: Next message to client: gghdrj1516683823586
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0007
MQTT_ClientCon_sent_cb(): Data sent
MQTT_ClientCon_recv_cb(): 2 bytes of data received
MQTT: TCP: data received 2 bytes (State: 20)
MQTT: total_len: 2
MQTT: message_type: 12
MQTT: receive MQTT_MSG_TYPE_PINGREQ
MQTT: Server task activated — state 20
MQTT: Sending, type: 13, id: 0000
MQTT_ClientCon_sent_cb(): Data sent
MQTT_ClientCon_recv_cb(): 2 bytes of data received
MQTT: TCP: data received 2 bytes (State: 20)
MQTT: total_len: 2
MQTT: message_type: 12
MQTT: receive MQTT_MSG_TYPE_PINGREQ
MQTT: Server task activated — state 20
MQTT: Sending, type: 13, id: 0000
MQTT_ClientCon_sent_cb(): Data sent
На клиенте:
WiFi connected
IP address:
192.168.4.121
Attempting MQTT connection.
pm open,type:2 0
failed, rc=-4 try again in 5 seconds
Attempting MQTT connection. connected
Publish message: hello world #1
16870
state: 5 -> 0 (0)
rm 0
pm close 7
del if0
usl
MasyaShu commented Jan 23, 2018
If ESP does not go to sleep, and you use «client.disconnect ()», then on the client:
192.168.4.121
Attempting MQTT connection . connected
Publish message: hello world # 1
19705
Attempting MQTT connection .
pm open, type: 2 0
failed, rc = -4 try again in 10 seconds
Attempting MQTT connection . failed, rc = -4 try again in 10 seconds
Attempting MQTT connection . failed, rc = -4 try again in 10 seconds
Attempting MQTT connection . failed, rc = -4 try again in 10 seconds
Attempting MQTT connection . failed, rc = -4 try again in 10 seconds
On the broker:
Starting MQTT server on port 1602
add 1
aid 1
station: 5c: cf: 7f: da: 01: 36 join, AID = 1
MQTT_ClientCon_connected_cb (): Client connected
MQTT: InitClientCon
MQTT_ClientCon_recv_cb (): 27 bytes of data received
MQTT: TCP: data received 27 bytes (State: 15)
MQTT: total_len: 27
MQTT: message_type: 1
MQTT: Connect received, message_len: 27
MQTT: Connect flags 2
MQTT: Keepalive 15
MQTT: Client id «ESP8266Client»
MQTT: Server task activated — state 20
MQTT: Sending, type: 2, id: 0000
MQTT_ClientCon_sent_cb (): Data sent
MQTT_ClientCon_recv_cb (): 23 bytes of data received
MQTT: TCP: data received 23 bytes (State: 20)
MQTT: total_len: 23
MQTT: message_type: 3
MQTT: Publish received, message_len: 23
MQTT: Published topic «outTopic»
MQTT: Matches to:
MQTT: Client: LOCAL Topic: «#» QoS: 0
received topic ‘outTopic’ with data ‘hello world’
outTopic
MQTT_ClientCon_recv_cb (): 14 bytes of data received
MQTT: TCP: data received 14 bytes (State: 20)
MQTT: total_len: 14
MQTT: message_type: 8
MQTT: Subscribe received, message_len: 14
MQTT: Message id 2
MQTT: Subscribed topic inTopic QoS 0
MQTT: Subscribe successful
MQTT: Server task activated — state 20
MQTT: Sending, type: 9, id: 0002
MQTT_ClientCon_recv_cb (): 33 bytes of data received
MQTT: TCP: data received 33 bytes (State: 20)
MQTT: total_len: 33
MQTT: message_type: 3
MQTT: Publish received, message_len: 33
MQTT: Published topic «outTopic / qqqqqq»
MQTT: Matches to:
MQTT: Client: LOCAL Topic: «#» QoS: 0
received topic ‘outTopic / qqqqqq’ with data ‘hello world # 1’
outTopic / qqqqqq
MQTT_ClientCon_sent_cb (): Data sent
MQTT_ClientCon_recv_cb (): 2 bytes of data received
MQTT: TCP: data received 2 bytes (State: 20)
MQTT: total_len: 2
MQTT: message_type: 14
MQTT: receive MQTT_MSG_TYPE_DISCONNECT
MQTT: ServerDisconnect
MQTT: Server task activated — state 7
MQTT: Disconnect
MQTT_ClientCon_discon_cb (): client disconnected
MQTT: DeleteClientCon
MQTT: Broker already disconnecting
MQTT_ClientCon_connected_cb (): Client connected
MQTT: InitClientCon
MQTT_ClientCon_recv_cb (): 27 bytes of data received
MQTT: TCP: data received 27 bytes (State: 15)
MQTT: total_len: 27
MQTT: message_type: 1
MQTT: Connect received, message_len: 27
MQTT: Connect flags 2
MQTT: Keepalive 15
MQTT: Disconnect client: ESP8266Client
MQTT: Client id «ESP8266Client»
MQTT: Server task activated — state 8
MQTT: Disconnect
MQTT_ClientCon_discon_cb (): client disconnected
MQTT: DeleteClientCon
MQTT_ClientCon_connected_cb (): Client connected
MQTT: InitClientCon
MQTT_ClientCon_recv_cb (): 27 bytes of data received
MQTT: TCP: data received 27 bytes (State: 15)
MQTT: total_len: 27
MQTT: message_type: 1
MQTT: Connect received, message_len: 27
MQTT: Connect flags 2
MQTT: Keepalive 15
MQTT: Disconnect client: ESP8266Client
MQTT: Client id «ESP8266Client»
MQTT: Server task activated — state 8
MQTT: Disconnect
MQTT_ClientCon_discon_cb (): client disconnected
MQTT: DeleteClientCon
MQTT_ClientCon_connected_cb (): Client connected
MQTT: InitClientCon
MQTT_ClientCon_recv_cb (): 27 bytes of data received
MQTT: TCP: data received 27 bytes (State: 15)
MQTT: total_len: 27
MQTT: message_type: 1
MQTT: Connect received, message_len: 27
MQTT: Connect flags 2
MQTT: Keepalive 15
MQTT: Disconnect client: ESP8266Client
MQTT: Client id «ESP8266Client»
MQTT: Server task activated — state 8
MQTT: Disconnect
MQTT_ClientCon_discon_cb (): client disconnected
MQTT: DeleteClientCon
MQTT_ClientCon_connected_cb (): Client connected
MQTT: InitClientCon
MQTT_ClientCon_recv_cb (): 27 bytes of data received
MQTT: TCP: data received 27 bytes (State: 15)
MQTT: total_len: 27
MQTT: message_type: 1
MQTT: Connect received, message_len: 27
MQTT: Connect flags 2
MQTT: Keepalive 15
MQTT: Disconnect client: ESP8266Client
MQTT: Client id «ESP8266Client»
MQTT: Server task activated — state 8
MQTT: Disconnect
Источник
