NEWS
telegram Adapter startet ständig sporadisch neu
-
Hallo,
seit neustem habe ich ein sporadisches Starten des telegram adapters 1.7.0. Dies geht soweit, dass der Adapter zeitweise nicht mehr startet und manuell gestartet werden muss.
Der Log zeigt folgendes:
2021-02-23 09:45:21.468 - error: telegram.0 (29604) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2021-02-23 09:45:21.469 - error: telegram.0 (29604) unhandled promise rejection: ETELEGRAM: 403 Forbidden: bot can't initiate conversation with a user 2021-02-23 09:45:21.469 - error: telegram.0 (29604) Error: ETELEGRAM: 403 Forbidden: bot can't initiate conversation with a user at /opt/iobroker/node_modules/node-telegram-bot-api/src/telegram.js:284:15 at tryCatcher (/opt/iobroker/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/opt/iobroker/node_modules/bluebird/js/release/promise.js:547:31) at Promise._settlePromise (/opt/iobroker/node_modules/bluebird/js/release/promise.js:604:18) at Promise._settlePromise0 (/opt/iobroker/node_modules/bluebird/js/release/promise.js:649:10) at Promise._settlePromises (/opt/iobroker/node_modules/bluebird/js/release/promise.js:729:18) at _drainQueueStep (/opt/iobroker/node_modules/bluebird/js/release/async.js:93:12) at _drainQueue (/opt/iobroker/node_modules/bluebird/js/release/async.js:86:9) at Async._drainQueues (/opt/iobroker/node_modules/bluebird/js/release/async.js:102:5) at Immediate.Async.drainQueues [as _onImmediate] (/opt/iobroker/node_modules/bluebird/js/release/async.js:15:14) at processImmediate (internal/timers.js:461:21) 2021-02-23 09:45:21.469 - error: telegram.0 (29604) Exception-Code: ETELEGRAM: ETELEGRAM: 403 Forbidden: bot can't initiate conversation with a user
Ich hoffe jemand kann mir einen Hinweis geben, wie ich die Situation verbessere.
Gruß & Danke
Thomas