-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPI disconnects #58
Comments
I am having the same problem on MacOS. |
@Judas2016 It's not OS related but library. It appears to be a timing problem between the client and server. |
Did you have any luck in getting it to work with SSL? |
Only with ESP not with Raspberry |
I got SSL working on macOS and the library works as expected now. I updated the version of Python to latest 3.9 from 3.7 and solved the problem. |
Im noticing the same issue with my RPI disconnecting. It looks like when the socket tries to read here (and there's no data) you get a timeout so this line doesn't get called for a while. Then when it eventually does get called depending on how long its been these lines get called and it disconnects. Not sure if this is a bug in the code or if the conn.read is expecting the blynk server to send data/heartbeat. I honestly just removed those two lines (136-137) and my RPI stoped disconnecting and the project has been working. If this is a bug in the code than I'm sure there is a more elegant way to fix this |
@jonathongardner Interesting! Which server are you using? The central or the assigned one? In my case, the connection works better with the assigned one being it lon1 or fran1. |
Yeah I'm just using the default one in the package |
Raspberry pi (any) with ethernet connection.
The code works fine for few minutes then disconnects with no errors.
Tried to set up line 'blynk = BlynkLib.Blynk(BLYNK_AUTH)' to 'blynk = BlynkLib.Blynk(BLYNK_AUTH, insecure= True)' but I get error: AttributeError: 'socket' object has no attribute 'write'
The option 'insecure=True' works fine on ESP32s however.
Any ideas?
TIA
The text was updated successfully, but these errors were encountered: