# Cpu \> 100 % ; Erreur : ETELEGRAM: 409 **URL:** \ **Category:** Configuration\ **Tags:** node-red, telegram\ **Created:** [Août 24, 2023, 10:16 UTC](https://community.gladysassistant.com/t/cpu-100-error-etelegram-409/8303 "2023-08-24T10:16:54Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gaetanb76](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gaetanb76/32/5911_2.png) [@gaetanb76](https://community.gladysassistant.com/u/gaetanb76)\ **Post date:** [Août 24, 2023, 10:16 UTC](https://community.gladysassistant.com/t/cpu-100-error-etelegram-409/8303/1 "2023-08-24T10:16:54Z")
Bonjour à tous, mon instance Gladys est installée sur un mini-pc et il fait souvent beaucoup de bruit. Gladys tourne à plus de 100% ; docker stats renvoie : ![2023_08_24_12h08_docker_stats](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/c/c5470a93c82789195efc1ab31e0bf67cfd856793.jpeg) J’ai regardé les logs de Gladys et j’obtiens ça : ```auto 2023-08-24T12:07:44+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:07:44+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:07:47+0200 handleMqttMessage.js:106 () Zigbee2mqtt device MultiPrises Salon, feature power_outage_memory not configured in Gladys. 2023-08-24T12:07:50+0200 message.connect.js:19 (TelegramBot.) 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 handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature indicator_mode not configured in Gladys. 2023-08-24T12:07:53+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature power_outage_memory not configured in Gladys. 2023-08-24T12:07:53+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature indicator_mode not configured in Gladys. 2023-08-24T12:07:53+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Prise MiniPC, feature power_outage_memory not configured in Gladys. 2023-08-24T12:07:59+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:07:59+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:00+0200 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Thu, 24 Aug 2023 10:08:00 GMT 2023-08-24T12:08:00+0200 message.connect.js:19 (TelegramBot.) 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 message.connect.js:19 (TelegramBot.) 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 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:14+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:19+0200 message.connect.js:19 (TelegramBot.) 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 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:28+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:28+0200 message.connect.js:19 (TelegramBot.) 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 poll.js:14 (RtspCameraHandler.poll) Unable to poll camera 2023-08-24T12:08:38+0200 message.connect.js:19 (TelegramBot.) 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 poll.js:14 (RtspCameraHandler.poll) Unable to poll camera 2023-08-24T12:08:43+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:43+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:47+0200 message.connect.js:19 (TelegramBot.) 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 handleMqttMessage.js:106 () Zigbee2mqtt device MultiPrises Salon, feature power_outage_memory not configured in Gladys. 2023-08-24T12:08:57+0200 message.connect.js:19 (TelegramBot.) 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 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:08:57+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:09:00+0200 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Thu, 24 Aug 2023 10:09:00 GMT 2023-08-24T12:09:06+0200 message.connect.js:19 (TelegramBot.) 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 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:09:12+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:09:16+0200 message.connect.js:19 (TelegramBot.) 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 lan-manager.scan.js:19 (LANManager.scan) LANManager starts scanning devices... 2023-08-24T12:09:25+0200 lan-manager.scan.js:57 (NmapScan.onSuccess) LANManager discovers 16 devices 2023-08-24T12:09:25+0200 lan-manager.stop.js:12 (LANManager.stop) LANManager stops scanning devices 2023-08-24T12:09:25+0200 message.connect.js:19 (TelegramBot.) 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 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. 2023-08-24T12:09:27+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur Luminosité Salon, feature brightness_state not configured in Gladys. ``` Voilà aussi les logs de node\_red : ```auto 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) ``` L’erreur sur la caméra vient du fait qu’elle a un soucis que je n’ai pas encore corrigé. Je ne sais pas si tout ça est lié. Merci d’avance pour votre aide. ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Août 24, 2023, 4:22 UTC](https://community.gladysassistant.com/t/cpu-100-error-etelegram-409/8303/2 "2023-08-24T16:22:44Z")
Par hasard tu n’as pas utilisé la même clé d’API Telegram côté Gladys et Node-RED ? Chez Telegram, une clé d’API = une connexion 🙂 ---
**Author:** ![gaetanb76](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gaetanb76/32/5911_2.png) [@gaetanb76](https://community.gladysassistant.com/u/gaetanb76)\ **Post date:** [Août 24, 2023, 5:31 UTC](https://community.gladysassistant.com/t/cpu-100-error-etelegram-409/8303/3 "2023-08-24T17:31:31Z")
Si. Je comprends donc qu’il faut en créer 2. Je veux publier sur le même bot, c’est possible ? ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Août 25, 2023, 7:54 UTC](https://community.gladysassistant.com/t/cpu-100-error-etelegram-409/8303/4 "2023-08-25T07:54:59Z")
Je suis pas sûr que ce soit possible… A tester limite Sinon, il faudra créer 2 bots