[Zigbee2Mqtt] Suppression logs warning

Development
1

What do you think about removing these logs?

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.

or better, emit them once during the service configuration, but not for every message.

1 Like
2

I agree that currently the message is scary even though this message is « normal »!

I’m in favor of this approach :slight_smile:

2 Likes
3

@AlexTrovato Does it make sense to you if I put it here Gladys/server/services/zigbee2mqtt/utils/features/mapDefinition.js at master · GladysAssistant/Gladys · GitHub?

Or here Gladys/server/services/zigbee2mqtt/utils/features/mapExpose.js at master · GladysAssistant/Gladys · GitHub?

These mapDefinition and mapExpose seem to be called only during configuration.

4

Hello everyone,
Indeed, these messages…

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