Telegram updater error 'Connection aborted.'

Configuration
1

System:

  • Core: 2023.12.4
  • Supervisor: 2023.12.0
  • Operating System: 11.2
  • Frontend: 20231208.2
    The use of Telegram results in an updater error:
Logger: telegram.ext.updater
Source: /usr/local/lib/python3.11/site-packages/telegram/ext/updater.py:478
First occurred: 22:01:53 (1 occurrences)
Last logged: 22:01:53

Error while getting Updates: urllib3 HTTPError ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

I’ve tried to solve this by revoking the bot token.
That seems to work for a few hours, but then it pops-up again in the log.
The notification itself works fine.
Is there something wrong with the configuration?

# Telegram Bot
telegram_bot:
  - platform: polling
    api_key: !secret telegram_api_key
    allowed_chat_ids:
      - !secret telegram_chat_id

# Notifier
notify:
  - platform: telegram
    name: !secret telegram_name
    chat_id: !secret telegram_chat_id

Or what else could I be doing wrong?
TIA

2

Good evening,

I wrote with Telegram via Github. Telegram assumes that it may be due to the version of Python. Telegram is currently working with the version. 3.20. Home Assistant is currently at Python 3.13.

There may be problems there. Attach the corresponding post from Github in the hope that Home Assistant reacts accordingly. Thanks in advance.

1 Like
3

Thank you, Johnyboy1984, very much appreciated!
I will wait and see if they will update it to 3.20
In the mean time I switched over to a Whatsapp add-on, but Telegram would be better.

BTW: maybe you shouldn’t publish your chatID and name like that.

4

is the same problem solved somehow?

5

I don’t know what you mean with “the same problem”.

My question (‘What else could be wrong?’) was answered.
So, I wait to see what the Python update will do.

6

as far as I know, not everyone has this error and it is unlikely to be related to the python update
I have found a mention of this error since 2021, but there was no solution there.

7

True, but from what I remember these were related to using node red, or a simple matter of revoking a token.
The first one didn’t apply to my case and the second one didn’t help.

I don’t know.
Maybe you have a better explanation?

8

I think it’s a bad connection

9

Only a bad connection for Telegram, what would cause that?
Nothing else complains about bad connections.
After throwing out Telegram from the configuration.yaml the log stays silent.

10

what is python for anyway? I completely deleted it from the system and everything works fine xD
by the way, the error is also gone, you can write it down in the solution to the problem - delete python ahaha