-
Notifications
You must be signed in to change notification settings - Fork 306
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
ESP32 core 2.0.2 does not work (2.0.1 does) #270
Comments
This issue seems to be that somehow, the ssl handshake timeout is set to 0 after the first message. |
I ran into this problem, and came with my work-around, which was to keep the channel open by deleting this line (at the cost of memory perhaps)
But then I saw @ndaneil comment .... and added to it. Rather than dig into ssl_client.cpp, you can add this line before the client->connect in the library.
You would have to add that setHandshakeTimeout before every one of these lines:
The 120000 is milli-seconds or ??? But it comes from this source:
You might also have to make this change to stop using Client and switch everything to WiFiClientSecure to get access to these calls (in the .h and .cpp)
|
This is a simpler solution / work-around. Did you post this bug over in esp32-arduino issues?
|
I found an open issue with the problem in the esp32-arduino repo: |
Seeing as the client is passed into the library, you should be able to set
the timeout in the client from your sketch. This would save the need for modifying the library.
I assume it only needs to be set once per instance of the client.
…On Mon 3 Jan 2022, 17:58 ndaneil, ***@***.***> wrote:
I found an open issue with the problem in the esp32-arduino
<https://github.com/espressif/arduino-esp32/issues> repo:
espressif/arduino-esp32#6077
<espressif/arduino-esp32#6077>
—
Reply to this email directly, view it on GitHub
<#270 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL5PQVBBNXXZYRUI4YM6EDUUHPTVANCNFSM5KVR5RWQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: <witnessmenow/Universal-Arduino-Telegram-Bot/issues/270/1004258138@
github.com>
|
Jan 18, 2022 ver 8.9 - updates from Arduino 1.8.19 - return from void problem re-runs the function if you dont do a return ??? https://stackoverflow.com/questions/22742581/warning-control-reaches-end-of-non-void-function-wreturn-type - updates for esp32-arduino 2.0.2 - bug with 2.0.2 handshake timeout - added timeout resets in this file as a workaround witnessmenow/Universal-Arduino-Telegram-Bot#270 (comment) - updates for esp32-arduino 2.0.2 - esp-camera seems to have changed to fill all free fb buffers in sequence, so must empty them to get a snapshot
Jan 18, 2022 ver 8.9 - updates from Arduino 1.8.19 - return from void problem re-runs the function if you dont do a return ??? https://stackoverflow.com/questions/22742581/warning-control-reaches-end-of-non-void-function-wreturn-type - updates for esp32-arduino 2.0.2 - bug with 2.0.2 handshake timeout - added timeout resets in this file as a workaround witnessmenow/Universal-Arduino-Telegram-Bot#270 (comment) - updates for esp32-arduino 2.0.2 - esp-camera seems to have changed to fill all free fb buffers in sequence, so must empty them to get a snapshot
Hi,
So I was testing my Telegram bot code after a long time since the last time I used it. I updated the ESP32 core to 2.0.2 (how lucky, just released 10 hours ago...), the UniversalTelegramBot to 1.3.0 and the ArduinoJson to 6.18.5. Testing either example codes or my own code, the bot just manages to send one message, but not more. It always gets stuck after the first sent message.
I have spent nearly an hour trying to figure out what was the problem, I even tried creating a new bot. As a last option, I just downgraded the ESP32 core to 2.0.1 and it worked perfectly.
So, if someone just runs with the same issue, downgrade to ESP32 core 2.0.1 (or just don't update it). I hope I can save someone's time.
Cheers.
The text was updated successfully, but these errors were encountered: