ok, I will going looking deeply and I will back.
Thanks @Canedje.
Hi again @Canedje. You know⊠its really weard⊠but⊠this type of node was finally my problem⊠I dont know why⊠but after removed it puaf⊠no more debug error. Inside this node obiusly I was configurate my only bot, and previusly (because yor recomendation) I have removed all the âresidualâ botsâŠ
For now⊠I dont have error on my debug pipeline.
Thanks for all your advices.
Hugs from Chile.
well done 
I only use the sender node. sending tekst or photoâs or variables
1 Like
Had the same error running the bot in configuration (not used in NodeRed) - was resloved by switching from polling to wehooks
1 Like
Iâm getting this exact error on Homeassistant.
I think I am not using two bots because I only have it configured on home-assistant and I call it from node-red through home-assistant call service.
My telegram configuration for home-assistant is as follows (I use two chats, so I created to notifiers, not sure if that is correct):
# Notifications
notify:
- name: Telegram
platform: telegram
chat_id: !secret telegram_chat_id
- name: timelapses
platform: telegram
chat_id: !secret telegram_chat_timelapse
telegram_bot:
- platform: polling
api_key: !secret telegram_api_key
parse_mode: html
allowed_chat_ids:
- !secret telegram_chat_id
- !secret telegram_chat_timelapse
Can this be motivated by calling the telegram service too fast or from two different places (for example, two different nodered flows?) Iâm a bit worried about this spamming my log.
The way you discribe is that you still using two bots
one in HA and one by NodeRED
But that requires the telegram node-red integration, no? I donât have node-red telegram integration. What I do is call the notification service of home-assistant, and I donât have any automation on home-assistant that uses telegram
Then I wondering how you call the notification from HA in NodeRED as far as I know thats not possible
You can through a call service node:
Homeassistant exposes the telegram bot as an entity with some services.
It is working, but I still get those nasty errors, and I guess I am missing some events.
Probably Iâm sending too much because I get like ~300 messages a day, but I was not getting those, letâs say, 3 weeks ago.
I updated to the latest HA version yesterday and this error message doesnât show up anymore. Fingers crossed.
Ok, so I found my problem, and I have to say that the error message is terrible and gives the the wrong idea.
It makes you think that you can not have several instances of a bot telegram running on your local machine, but what happens, in reality, is that you can not use the same bot credentials on several bot clients.
How I realised? After not seeing the error for a while I connected a hacked dafang camera, then checked the camera logs, and guess what? They were filled with this same error, and the error started appearing again in home-assistant. The reason? I was using the same bot credentials on both places.
I wish documentation (this time, on telegram library) were better about this.
I am getting this error. I instaled node-red integration and use telegram bot in it without problems. But after I also config telegram bot in Home Assistant and I began to see that error in the log. At first I thought it was normal because I have two instances running but after uninstall node-red and restart Home Assistant the error continues appearing.
Any idea what could be happening?
Thanks.
You can only use one telegram bot. Or in HA or in Nodered
Hi everybody
I have the same issue.
I used the HA telegram integration for notify in HA.
In my node red flow I used the call service which call behinds HA.
My problem is I used too in my node red the node-red-contrib-telegrambot-home and telegrambot-switch for asking questions to user via telegram when I leaved home,âŠ
HA and node red used the same bot and same tokenâŠ
Whatâs the solution to resolve this issue ? I read all the posts on this subject without find solution.
Can we use a second token or user for the same bot ?
Thx to all
