BLYNK
HOME       📲 GETTING STARTED       📗 DOCS       ❓HELP CENTER       👉 SKETCH BUILDER

Huge Blynk Library update! v0.5.0 [Arduino, PlatformIO, Particle, MBED, OpenWrt]

#1

PlatformIO, Particle, ARM mbed and OpenWRT packages have been updated accordingly.

In this release

  • General improvements

    • Forget about “flood errors”. Probably :wink:
    • Library is now easier to port/run on 3rd party hardware
    • We now use a single implementation of BlynkFifo
    • Better diagnostic/debug prints
    • NeoPixel lib is no longer included in Blynk release zip package.
  • New hardware support:

    • ESP32
      • Bluetooth LE initial support + example
      • SSL (secure connection) support + example
      • App Export example for ESP32 (with WiFi credentials provisioning)
    • ESP8266
      • SSL stability improvement (still not perfect due to a bug in ESP Core)
      • SSL now checks certificate chain (previously fingerprint was used). Needs 2.4.0-rc2
      • BIG stability improvements in Shield mode (AT commands)
    • Realtek RTL8710 / Ameba support
    • Arduino UNO WiFi support
    • WIZnet WizFi310 support
    • Improved ARM mbed support
    • Improved Linux support
    • All frameworks are now enabled for PlatformIO library
  • Bugfixes:

    • Unexpected “Login timeout” during redirect (#374)
    • 100% CPU load on linux/raspberry
    • Compile Error with Arduino 101 (#369). Please keep in mind that #304 is still there…
    • Call BLYNK_DISCONNECTED() on unsuccessful write (#371)
    • RFDuino uses BLEPeripheral now
    • Travis CI build is fixed

Full list of supported hardware is here.

Grab the update here: https://github.com/blynkkk/blynk-library/releases/latest

:star2: BTW, if you like Blynk, don’t forget to give us a github star! :star2:

Please post your feedbacks in this topic.

14 Likes

Concurrent BLYNK_WRITE's
pinned globally #2
0 Likes

#3

could you please elaborate this?

2 Likes

#4

@wanek the library now automatically delays sending out commands, if the user sketch tries to do it too fast.

5 Likes

Defer Writes
#5

Does it mean we can put Blynk.virtualWrite to void loop? :smiley:

2 Likes

#6

You can try.

1 Like

#7

wow, this is a great idea, considering that 70% of newbies actually putting virtualwrite to main loop!

0 Likes

#8

I think the practise should still be discouraged because loop() will still be a bad use of resources, even if Blynk was able to cope with it.

3 Likes

#9

Yes that is just to make newbies happy.
BlynkTimer usage recommendations still apply.

1 Like

#10

Great, more happy newbies “flooding” the forums with bad coding practices becasue new library enhancements will “fix everything” :thinking: Gee, Thanks :stuck_out_tongue_winking_eye: JK

3 Likes

#11

Well, those Makers will encourage @vshymanskyy to create better and stable code for the library, so every disadvantage has it’s advantage :wink:

0 Likes

#12

Hello,

I’d like to be sure…
So I’ve just to remove old Blynk libraries/tools folder and replace them by new libraries and tools folders, at the same location?

0 Likes

#13

@Alx-I yes

0 Likes

#14

I can certainly see BIG stability improvements with my MEGA/ESP-01 setup… 20 hours and counting without a single need to activate my built-in reconnect routines. and considering how bloated that testbench project is, and my limited coding abilities… this is a loong time :stuck_out_tongue:

:+1::+1:

I don’t suppose there is a “Total Neanderthals How-to Guide” for doing so with NodeJS on the RPi? :wink:

1 Like

#15

Can please explain me anyone how can i update the library on a raspberry pi 2 with raspbian?

0 Likes

#16

@Andy_Wand Check the documents and Help Center… if using WiringPi (C++) follow the links and directions accordingly, if using NodeJS, that is presently stable at v.0.4.7 with no current way to upgrade.

http://help.blynk.cc/how-to-connect-different-hardware-with-blynk/raspberry-pi/nodejs-vs-c-library

0 Likes

#17

I use node but blynk or so crashed after few days i think its the 100% cpu usage or so that’s why I wanted to update.

0 Likes

#18

That issue seemed to be related specifically to the C++ method and beta 0.5.0 (since updated as stable).

Node v.0.4.7 has been around for a long time and is stable… but you might have code issues that, in Linux, need to be ‘caught’ else they stop the script.

Best to start a NEW topic and provide as much detail as possible, and show your full code.

1 Like

#19

Thank you very much, Blynk Gurus. You guys are awesome!

1 Like

#20

A question. Does this upgrade cure the instability of ESP when doing Blynk.syncAll() when there are lots of V pins?

0 Likes