I have set up a test just to check functionality of my Raspberry Pi and Bynk 2.
I can send data to Blynk all day long, no problem.
If I try and receive data from Blynk then the Pi disconnects after 1m 54s. Always that time.
If I use a program that sends and receives data then the send is fine there is no disconnection but the receive stops working.
I have tried this on a Raspberry PI 3 and 4, both the same results and the timing is the same.
Pi Details
NAME=“Raspbian GNU/Linux”
VERSION=“10 (buster)”
No I haven’t resolved this issue and in the absence of any help from Blynk I moved from a Pi Zero project to ESP32 running uPython, not what I want, but it works absolutely faultlessly. At the time of posting the ink to the lib it was the latest as supplied by vshymanskyy. Can you point me at the latest issue of the library, and I will give it another go.
Meanwhile I would appreciate it if anybody at Blynk could offer help.
@JohnG The Python lib for Blynk2.0 can be found here, it was updated 2 months ago. Here I exposed a test code. However, the new lib is not stable as it causes disconnections.
Emilio
You have me confused. I have checked the version I am running against the version you linked to in your post and they both seem the same version = “1.0.0”
I don’t think the raspberry pi supports blynk edgent and OTA etc… So I recommend you to use esp32 or nodemcu instead especially if you are going to use blynk commercially.
@John93 Your right but I am not using blynk edgent or interested in OTA. To get over the problem at the moment I am using MQTT to connect the raspi pi to the ESP32 to provide connectivity. It works fine but an unnecessary complication