Blynk disconnects

Blynk disconnects several times a day, without consequence.
It does not matter much, but where can I see why? which log ?

02-026434

Not sure what platform your running local blynk server on? If its a pi, then look under /home/user_account/Blynk/logs/blynk.log
Note: Typically user_account=pi

The archive directory under logs contains previous days files ordered by date. blynk.log.YYYY-MM-DD
On the pi, you may have to open it using LibreOffice Writer (opens large files)

Based on log.level=(trace|debug|info|error) will define how precise logging will be.
This setting is located inside server.properties file (under Blynk directory). INFO is the most comprehensive. It should be noted that the TRACE setting includes debug,info & error log entries.

Many things can cause disconnections. If your running a DSL connection for instance, a line retrain can cause temporary disconnection. Lastly, if you change the log setting, you need to restart the blynk server.

Good Luck

1 Like

thank you, I run local server under Windows 10.

I just changed info to trace, wait and see …
I think it’s due to a line retrain as you told.

Not much info to go on.
If its a esp8266 and you put it in an enclosure its probably over heating.

it is a nodemcu and it’s not in an enclosure.
When it disconnects, the program continues to work perfectly without connection, and wait 30 seconds to reconnect to blynk local server.
(@Gunner script )

No more info in blynk.log

blynk disconnects at 15:23 ,
why local server uses fcm.googleapis.com?

15:23:54.367 DEBUG- 

Request DefaultFullHttpRequest(decodeResult: success, version: HTTP/1.1, content: UnpooledSlicedByteBuf(freed))
POST /fcm/send HTTP/1.1
Authorization: key=**************************************************
content-type: application/json; charset=utf-8
content-length: 251
host: fcm.googleapis.com
accept: */*

Response DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Date: Thu, 03 Jan 2019 14:23:55 GMT
Expires: Thu, 03 Jan 2019 14:23:55 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN ........................

blynk disconnects at 16:53 ,
but no info in blynk.log, I don’t think it’s the way to know the cause of disconnection.

Make sure your seeing INFO- entries in log, just like DEBUG-

This capture looks like your using a web hook to post something. Hard to tell much more.

Update: :hushed:
looks like that is for Blynk.notify(). They use https://firebase.google.com/docs/cloud-messaging/
for notify widget.

1 Like