-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Telegram sending error on 14.0.0.1 (and master 14.0.0 also) #21464
Comments
I can confirm, just build 13.4.0 and work correctly, on 14.x it's not working anymore |
I'm not familiar with the time it normally makes, but it seems the two log lines are very close to each other:
It's maybe linked to #21442 The timeout value changed from seconds to milliseconds in the Core3 API. This could explain why the "Failed" messages happens only 134ms after the actual command (which is shorter than a full TLS handshake) |
It consistently replies:
even with a timeout of 10000 ms (being default in code) |
I'm still surprised how quickly it returns the error, 105 ms including the logging |
From what I see above it doesn't connect at all as and no heap usage either:
|
Unrelated issue:
It seems that the GoDaddy Authority is long expired. Although I understand you don't use it and use fingerprint instead |
Yep. That was the reason we had to use |
I'm still looking into the Telegram issue. As a test I started to reuse an ESP8266 but it fails there too. So for now we can rule out core3. How about the fingerprint? Where can I see if the fingerprint is still valid? |
Invalid fingerprint would generate a TLS error. It's not the case here. |
Adding some more debug info doesn't ring my bells:
I'm lost for now. |
Ah, it is a TLS connection error after all. Let me first update the CA. |
I updated the CA from Telegram, but now I get error 49: This would be a lot of work to allow unsupported features, hence I'm in favor of removing CA verification in Telegram (which wasn't working anyways). The Fingerprint seems to have changed, it is now: |
With latest change in CA and
with
|
Yep! Succes. The changed fingerprint workx. |
PROBLEM DESCRIPTION
Telegram returns error when sending message on 14.0.0.1 (and master 14.0.0 also).
Sending via Telegram API using
webquery
works for master 14.0.0 build (which I've initially compiled and updated one of my tasmotas) but don't work for dev.REQUESTED INFORMATION
- [ ] Pre-compiledBacklog Template; Module; GPIO 255
:- [ ] If using rules, provide the output of this command:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
EXPECTED BEHAVIOUR
Telegram sends message
SCREENSHOTS
n/a
ADDITIONAL CONTEXT
Telegram was working fine with every release lower than v14 with on many Tasmota devices.
Manual sending via
webquery
worked for the master branch 14.0.0.1 but don't work for dev 14.0.0.1:After "Done" nothing comes to the telegram chat. At the same time this query works on another tasmotas and PC.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: