New Blynk Library v0.5.1 is Released (important for local server owners)

Hi Dmitriy,
thank you for answer.
I use my own Blynk server and currently I am using following command in sketch:
Blynk.begin(auth, server_ip, 8442, arduino_ip, dns_ip, gateway_ip, subnet_mask, arduino_mac);

After update Blynk Library to 0.5.1 I can use following command:
Blynk.begin(auth, server_ip, 8080, arduino_ip, dns_ip, gateway_ip, subnet_mask, arduino_mac);
I am right ?

Which port is preffered for hardware on local Blynk server in the future ?
Best Regards



Does the SSL hardware connection still work on port 8441 by default?

Yes. This part is unchanged for now. However, in future we plan to move this to 8443/443 as well.

@Dmitriy, after upgrading from 0.5.0 to 0.5.1, i observed that the device type changed from “esp8266” to “arduino”. this could be because of some changes in the new library? or why is it so?

anyone else observed this? please look at the terminal line 3 and last.

I had simular (un-responded to) issue here that was “resolved” by changing the device in my IDE.

I think the library’s board detection routines are a little off at times :wink:

well, i also updated the esp core from 2.4.0-rc2 to 2.4.0 maybe that has something to do with this?
i always select “generic esp8266” board in menu.

up to now the blynk always displayed the correct device… will do more investigation tomorrow.

@vshymanskyy should know better.

That’s OK, “fixed”!
It looks like hardware calls use the same port as RESTful api.
I was wondering is there any way to “ping” the local server via REST?

Best Regards

Sure, YOu may do any request and parse the answer.

Sure i can. i’m already using REST to exchange data between my hardware, server and app.
The weird thing with REST is that while exchange of data is normal, there is an “Offline” indication in the application.
There should be some kind of “ping” from the hardware to the server periodically, informing that hardware is alive.
This is missing from REST. I was wondering if there is a way to implement it.

Http is http. Hardware is hardware. How pinging http should affect hardware?

If your hardware is offline than this is the correct thing.

Not necessarily :wink: OP said “that while exchange of data is normal”

@Gunner I saw it. Ticket created.

1 Like

OK, thanks.

Ok, I give up. I can not get the new library 5.1 to work not matter what I try.

sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080 Causes raspberry pi 3 to freeze

#define BLYNK_DEFAULT_PORT 8080 // does not work.

Blynk.config(auth_local_server, local_server, 8080); // does not work.

Or make port forwarding from 80 to 8080. // is not available because I have a web server.

I see these statements. They conflict me.
----- @cj190133 with latest firmware default port is 80 unless you change it.
----- 8080 now is the default port for hardware on the Local Server.

I done a port forward of 8080 to the pi server ( Blynk server) . // does not work.

I’m just going to go back to library 5.0 until we get finished monkey-ing with all the ports

Try to define it directly inside BlynkConfig.h

It worked for me. :slight_smile: (although different port)

edit: this #define doesn’t work in sketch (for me), as it is overwritten by lib. It might be, the compiler must know you want to use local server (another #define?)

Hey Marvin7, That worked.
Thank You so much. You’re a life saver.
Appreciate the quick response.

Glad it worked :slight_smile:

since I was successful with this I thought I would go ahead and do the server upgrade to version .0.33.0.
Bad idea. Nothing works with that version. Not even old esp’s that have been running for a year quit working.
So reverted back to 32.0.