I am trying to use an Arduino with an ESP-01 as a shield and am currently using the WiFiEsp library. I need to send a Telegram message. I cannot get a connection. I have spent two weeks researching and today I found a Telegram user group that says I have to use TLS 1.2. The Espressif manual doesn't mention TLS at all and only mentions SSL which seems to be exactly what the available Telegram libraries are using.
Yes, I have asked a related question before. No, no response yet. This request is related but now the question becomes more specific concerning TLS 1.2. Maybe that buzz word will catch someones attention. (fingers crossed)
no. even the newest AT 2.1 doesn't support TLS 1.2.
Arduino esp8266 core does.
there is a custom AT firmware without TCP server and UDP support, which does TLS 1.2
read
I see the 1.7 Firmware supports TLS 1.2. So I have to choose and either give up using the Telegram API which now requires TLS 1.2, or give up using UDP which means I cannot synch the time using NTP. Fantastic situation. I simply can't understand how this problem (some SSL servers not working with ESP-01 & Co) can exist for five years and Espressif simply refuses to update their firmware. This renders their product more and more useless every day, does it not?
Is there an alternative module from any manufacturer that can be used via either a serial, I2C or SPI connection? My project uses a custom ATMEGA1284 based "barebone" (plus all the hardware the project itself needs) so a "normal" Shield doesn't plug into it.
I see the 1.7 Firmware supports TLS 1.2. So I have to choose and either give up using the Telegram API which now requires TLS 1.2, or give up using UDP which means I cannot synch the time using NTP. Fantastic situation. I simply can't understand how this problem (some SSL servers not working with ESP-01 & Co) can exist for five years and Espressif simply refuses to update their firmware. This renders their product more and more useless every day, does it not?
Is there an alternative module from any manufacturer that can be used via either a serial, I2C or SPI connection? My project uses a custom ATMEGA1284 based "barebone" (plus all the hardware the project itself needs) so a "normal" Shield doesn't plug into it.
the special firmware can get ntp time. (if you ask the author, because I see he didn't commit the change yet)
you access the time then with WiFi.getTime();
Great. You are making a bad situation better. If you have contact info for him, could you private message me or ask him to? I would also send you my data to forward to him. If he needs testers, here I am!
JaBa:
Great. You are making a bad situation better. If you have contact info for him, could you private message me or ask him to? I would also send you my data to forward to him. If he needs testers, here I am!
the link to GitHub repo of the custom firmware is in the README of the WiFiEspAT library.
Update: I got that firmware loaded yesterday and just tested it manually, without libraries etc. It is now at least physically possible to connect! I no longer get CLOSED, but CONNECTED as it should be. I'll need to work out the required changes to my software if any and will probably also convert to WiFiEspAT instead of WiFiEsp due to the additional features. I previously shyed away because I was afraid of flashing the module but his firmware is simply loaded like any other Arduino program and couldn't be simpler. Thanks for the tip!
For anyone else who might refer to this thread/topic: Telegram switched to TLS 2.1 about March 2020 and the ESP modules don't support that advanced form of SSL yet so all Telegram applications, samples, etc. probably stopped working in March 2020. The solution is to update to the custom firmware as mentioned in this thread because it supports TLS 2.1 and Telegram absolutely requires it.
Thanks again, I look forward to now moving forward with this project!