# \[Zigbee2Mqtt\] Avertissement : suppression des logs

**URL:** <https://community.gladysassistant.com/t/zigbee2mqtt-suppression-logs-warning/8072>\
**Category:** Développement\
**Tags:** zigbee2mqtt\
**Created:** [Avril 3, 2023, 9:38 UTC](https://community.gladysassistant.com/t/zigbee2mqtt-suppression-logs-warning/8072 "2023-04-03T09:38:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [Avril 3, 2023, 9:38 UTC](https://community.gladysassistant.com/t/zigbee2mqtt-suppression-logs-warning/8072/1 "2023-04-03T09:38:37Z")

</div>

Que pensez-vous de supprimer ces logs ?

```auto
2023-04-03T11:36:03+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device Prise chambre, feature indicator_mode not configured in Gladys.
2023-04-03T11:36:03+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device Prise chambre, feature power_outage_memory not configured in Gladys.
2023-04-03T11:36:06+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device Prise café, feature indicator_mode not configured in Gladys.
2023-04-03T11:36:06+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device Prise café, feature power_outage_memory not configured in Gladys.
2023-04-03T11:36:24+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device Prise télé, feature indicator_mode not configured in Gladys.
2023-04-03T11:36:24+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device Prise télé, feature power_outage_memory not configured in Gladys.

```

ou mieux, de les émettre une fois lors de la configuration du service, mais pas à chaque message.

---

<div class="post-metadata">

**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:** [Avril 3, 2023, 9:41 UTC](https://community.gladysassistant.com/t/zigbee2mqtt-suppression-logs-warning/8072/2 "2023-04-03T09:41:16Z")

</div>

Je suis d’accord qu’actuellement le message fait peur alors que ce message est «&nbsp;normal&nbsp;» !

> [@cicoub13](#):
>
> ou mieux, de les émettre une fois lors de la configuration du service, mais pas à chaque message.

Je suis plutôt pour cette piste 🙂

---

<div class="post-metadata">

**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\
**Post date:** [Avril 3, 2023, 9:49 UTC](https://community.gladysassistant.com/t/zigbee2mqtt-suppression-logs-warning/8072/3 "2023-04-03T09:49:03Z")

</div>

@AlexTrovato Ça te paraît logique si je le mets ici [Gladys/mapDefinition.js at master · GladysAssistant/Gladys · GitHub](https://github.com/GladysAssistant/Gladys/blob/master/server/services/zigbee2mqtt/utils/features/mapDefinition.js#L14) ?

**Ou** ici [Gladys/mapExpose.js at master · GladysAssistant/Gladys · GitHub](https://github.com/GladysAssistant/Gladys/blob/master/server/services/zigbee2mqtt/utils/features/mapExpose.js#L12) ?

Ces `mapDefinition` et `mapExpose` ont l’air d’être appelés uniquement pendant la configuration.

---

<div class="post-metadata">

**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:** [Avril 19, 2023, 4:22 UTC](https://community.gladysassistant.com/t/zigbee2mqtt-suppression-logs-warning/8072/4 "2023-04-19T16:22:33Z")

</div>

Bonjour à tous,  
En effet, ces messages…

```auto
2023-04-19T18:11:01+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4c1381f81bb16dd, feature power_outage_memory not configured in Gladys.
2023-04-19T18:11:02+0200 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4c1389bcc3df2fc, feature brightness_state not configured in Gladys.

```

font peur.

Mais si c’est normal, ça me rassure.  
Ok avec @cicoub13 :

```auto
    ou mieux, de les émettre une fois lors de la configuration du service, mais pas à chaque message.

```