Skip to content
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 error 409 #13255

Closed
metbril opened this issue Mar 16, 2018 · 3 comments
Closed

Telegram error 409 #13255

metbril opened this issue Mar 16, 2018 · 3 comments

Comments

@metbril
Copy link

metbril commented Mar 16, 2018

Home Assistant release (hass --version):
0.65.5

Python release (python3 --version):
3.6.3

Component/platform:
telegram_bot

Description of problem:
Since upgrading from 0.64 to 0.65 the telegram bot is flooding my log file with errors. This message appears 5 or 6 times per minute:

2018-03-16 06:57:04 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] wrong status 409

BTW, notifications are working. But it itches me seeing this error.

Expected:
No errors

Problem-relevant configuration.yaml entries and steps to reproduce:

################################################
## Telegram Bot
################################################

telegram_bot:
  - platform: polling
    api_key: !secret telegram_bot_api_key
    allowed_chat_ids:
      - !secret telegram_bot_chat_id_robert

################################################
## Notify
################################################

notify:
  - name: telegram
    platform: telegram
    chat_id: !secret telegram_bot_chat_id_robert

Traceback (if applicable):

Additional info:
Using hassio on rpi 2b
Possibly related to multiple other telegram issues since 0.65 issued at github and/or the community forums.

@metbril
Copy link
Author

metbril commented Mar 16, 2018

The issue is occurring since the same time that #12774 started.

@metbril
Copy link
Author

metbril commented Mar 16, 2018

Telegram error 409 is

another webhook is active

so perhaps I am accidentally using the api key somewhere else. Will look into this. Strange though that this is only showing up recently.

@metbril
Copy link
Author

metbril commented Mar 16, 2018

Don't know what was wrong, but I changed the api key for the bot and added that to my config. This way I was sure the key could not be used somewhere else. Error is gone. So not caused by HA.

@metbril metbril closed this as completed Mar 16, 2018
@home-assistant home-assistant locked and limited conversation to collaborators Jul 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant