Cpu > 100 % ; Error : ETELEGRAM: 409

Configuration
,
1

Hello everyone,
my Gladys instance is installed on a mini-PC and it often makes a lot of noise.
Gladys is running at over 100%; docker stats returns :

2023_08_24_12h08_docker_stats
2023_08_24_12h08_docker_stats1185×133 56.2 KB

I looked at the Gladys logs and I get this:

2023-08-24T12:07:44+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:07:44+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:07:47+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device MultiPrises Salon, feature power_outage_memory not configured in Gladys.
2023-08-24T12:07:50+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:07:53+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature indicator_mode not configured in Gladys.
2023-08-24T12:07:53+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature power_outage_memory not configured in Gladys.
2023-08-24T12:07:53+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature indicator_mode not configured in Gladys.
2023-08-24T12:07:53+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature power_outage_memory not configured in Gladys.
2023-08-24T12:07:59+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:07:59+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Thu, 24 Aug 2023 10:08:00 GMT
2023-08-24T12:08:00+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:08:09+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:08:13+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:14+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:19+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:08:28+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:28+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:28+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:08:35+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2023-08-24T12:08:38+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:08:39+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2023-08-24T12:08:43+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:43+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:47+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:08:47+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device MultiPrises Salon, feature power_outage_memory not configured in Gladys.
2023-08-24T12:08:57+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:08:57+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:08:57+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:09:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Thu, 24 Aug 2023 10:09:00 GMT
2023-08-24T12:09:06+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:09:12+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:09:12+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:09:16+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:09:22+0200 \u003cinfo\u003e lan-manager.scan.js:19 (LANManager.scan) LANManager starts scanning devices...
2023-08-24T12:09:25+0200 \u003cinfo\u003e lan-manager.scan.js:57 (NmapScan.onSuccess) LANManager discovers 16 devices
2023-08-24T12:09:25+0200 \u003cinfo\u003e lan-manager.stop.js:12 (LANManager.stop) LANManager stops scanning devices
2023-08-24T12:09:25+0200 \u003cwarn\u003e message.connect.js:19 (TelegramBot.\u003canonymous\u003e) Telegram polling error, code = ETELEGRAM, message = ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2023-08-24T12:09:26+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.
2023-08-24T12:09:27+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys.

Here are the node_red logs as well:

Unhandled rejection Error: ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
    at /data/node_modules/node-telegram-bot-api/src/telegram.js:299:15
    at tryCatcher (/data/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/data/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/data/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/data/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/data/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/data/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/data/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/data/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/data/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:466:21)

The error on the camera comes from the fact that it has an issue that I haven’t fixed yet.

I don’t know if all of this is related.

Thank you in advance for your help.

2

By any chance, didn’t you use the same Telegram API key on the Gladys side and in Node-RED?

With Telegram, an API key = one connection :slight_smile:

3

Yes.
So I understand that I need to create two of them.
I want to publish on the same bot, is that possible?

4

I’m not sure that’s possible… Maybe worth testing

Otherwise, we’ll have to create 2 bots