Dear all, last year I felt the problem is solved, but came again now: After having a network outage (that may happen any time), the Telegram receiver on my raspi stops. The Telegram sender continues sending when triggered later the day. Is there a way or a workaround of "re-encouraging" the receiver to try to receive, other that reboot the raspi via crontab? Some details from the syslog:
$ sudo cat /var/log/syslog|grep telegram
Jan 22 03:03:33 watchdog Node-RED[435]: 22 Jan 03:03:33 - [warn] [telegram bot:xxx] EFATAL: Error: read ETIMEDOUT
Jan 22 03:03:33 watchdog Node-RED[435]: 22 Jan 03:03:33 - [warn] [telegram bot:xxx] Unknown error. Trying again.
Jan 22 03:04:14 watchdog Node-RED[435]: 22 Jan 03:04:14 - [warn] [telegram bot:xxx] EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
Jan 22 03:04:14 watchdog Node-RED[435]: 22 Jan 03:04:14 - [warn] [telegram bot:xxx] Network connection may be down. Trying again.
Jan 22 03:04:54 watchdog Node-RED[435]: 22 Jan 03:04:54 - [warn] [telegram bot:xxx] EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
Jan 22 03:04:54 watchdog Node-RED[435]: 22 Jan 03:04:54 - [warn] [telegram bot:xxx] Network connection may be down. Trying again.
Jan 22 15:02:37 watchdog Node-RED[425]: Sat, 22 Jan 2022 15:02:37 GMT node-telegram-bot-api deprecated In the future, content-type of files you send will default to "application/octet-stream". See https://github.com/yagop/node-telegram-bot-api/blob/master/doc/usage.md#sending-files for more information on how sending files has been improved and on how to disable this deprecation message altogether. at .node-red/node_modules/node-red-contrib-telegrambot/telegrambot/99-telegrambot.js:1467:50
