Integration with new hardware

Hi all! Congratulations to the Blynk team for this wonderful product!

I’m considering the integration of Blynk with panStamp’s lagarto server (Python) in order to make our wireless modules compatible with Blynk,

I’ve tried to find an integration guide for new hardware and applications but I think I’m missing something. Can you please guys point me to the right direction?


Hello, here is small brief. Here is a basic Python example. @vshymanskyy do we have something else?.


How’s your C skills? I have written a proggy that can bridge Lagarto to a Blynk server. To Largato it listens for the zmq events, to Blynk it looks like several pieces of hardware.

Still in development but mostly functional.

Although I can’t figure out how to upload it or send it to you.

Thanks @Dimitry for the links. It seems to me that your Python example is mainly a client connecting to a server ( Reading at this page I’ve also found that your cloud-based server can be replaced by a local Java server. I have some questions though:

  1. Is your ESP8266 standalone example connecting with your cloud server or is it implementing the blink server inside the ESP8266?

  2. For the integration with our Lagarto server it would be great if we could implement the Blink server into Lagarto (Python) itself. Otherwise, we could make Lagarto connect with your java server locally, in the same way that we did with OpenRemote. However, this usually adds an extra headache during the installation. Direct connection between our lagarto server and BLink app would be great in fact. Is this the protocol used by clients and server?

  3. I’ve been trying to know a bit more about the blink protocol. It seems that you are using simple TCP/IP socket connections between server and clients. Am I right? Aren’t you using MQTT or any other queue-based solution?

Nice to meet you @NickM here as well! Is this Blink server the (Java) one mentioned above?

It is connecting cloud server.

It is doable but I’m afraid it will take many efforts. Such features as bridge, twitter, mail, push notif, history graph - it’s all requires server logic.


No. Mutual SSL between app<->server. Plain tcp/ip or SSL/TLS sockets for server<->hardware (depends on hardware and connection type).

We don’t. It is overcomplicated for us. Thus server will support MQTT for hardware part in nearest future.

Thanks @estratos

We’ll stay with your cloud server for the moment. I want to know how it performs mainly in terms of speed.

It performs very well :wink:. Of course everything depends on how you will use it. But in general you can handle ~10k req/sec per core.

I’ve been playing with Blynk and the ESP8266 standalone application and I must say that I’m impressed by its speed, given that commands are passing through a remote server.

I’ve however found the limitation in the amount of pages supported by each project and also in the amount of projects supported by each page. I also understand that Blynk is under heavy development so I’ll be following your work impatiently.

Congratulations and thanks for making Blynk.

Glad to hear that! Project space will be extended in future for sure, also limit on projects could be easily removed in case of local server.