Node red telegram bot issue

General
1

Am using the node-red-contrib-telegrambot in node red to work with home assistant.

I had this working for few days and now I just can't get it to work.

I have a very simple flow to test my command and every time I send the command to the bot, node red does not act on it. I even added a debug node after the command node and nothing comes up on the debug output.

I have used the same token and the chat ID in HA directly and I am able to receive messages but just not with nod red.

Also, every time I deploy the change in node red, I get this error "Error stopping node: Close timed out" and the node it points to is the configuration node where I have my token and the chat id.

can some one please help

Node-RED version: v4.0.8
Node.js version: v22.11.0
Linux 6.6.73-haos x64 LE
node-red-contrib-telegrambot version: v16.1.2

These are some of the node red logs in home assistant:
2 Feb 23:38:44 - [error] [telegram bot:16a9c5bd33bbd4db] Error stopping node: Close timed out
2 Feb 23:38:44 - [info] Stopped flows
2 Feb 23:38:44 - [info] Updated flows
2 Feb 23:38:44 - [info] Starting flows
2 Feb 23:38:44 - [info] Started flows
2 Feb 23:38:44 - [info] [mqtt-broker:HAMQTTBroker] Connected to broker: mqtt://homeassistant.local:1883
2 Feb 23:38:49 - [info] [server:Home Assistant] Connecting to http://supervisor/core
Unhandled rejection RequestError: AggregateError
at new RequestError (/config/node_modules/request-promise-core/lib/errors.js:14:15)
at Request.plumbing.callback (/config/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/config/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/config/node_modules/@cypress/request/request.js:183:22)
at Request.emit (node:events:518:28)
at Request.onRequestError (/config/node_modules/@cypress/request/request.js:869:8)
at ClientRequest.emit (node:events:518:28)
at emitErrorEvent (node:_http_client:103:11)
at TLSSocket.socketErrorListener (node:_http_client:506:5)
at TLSSocket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:90:21)
Unhandled rejection RequestError: AggregateError
at new RequestError (/config/node_modules/request-promise-core/lib/errors.js:14:15)
at Request.plumbing.callback (/config/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/config/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/config/node_modules/@cypress/request/request.js:183:22)
at Request.emit (node:events:518:28)
at Request.onRequestError (/config/node_modules/@cypress/request/request.js:869:8)
at ClientRequest.emit (node:events:518:28)
at emitErrorEvent (node:_http_client:103:11)
at TLSSocket.socketErrorListener (node:_http_client:506:5)
at TLSSocket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:90:21)
2 Feb 23:41:19 - [error] [telegram sender:Send message] Caught exception in sender node:
Error: EFATAL: AggregateError

2

You cannot control the same bot from different places. Each bot can only be controlled from a single connection.

3

Ah ok. I’ll try this. Thank you

4

Tried with different bots too, one to use in node red and it just won’t work

5

I'm at a loss them I'm afraid. I don't use HA so I can't say whether this is an issue.

From the error, it does look like an HA issue rather than a Node-RED one since we know that it works fine in Node-RED as there are a lot of us using it. The error suggests an issue with HA's MQTT broker at second glance.

As not so many HA users inhabit this forum, you may be better off raising in the HA forum.

6

Thank you :slight_smile: