[RESOLVED] Zigbee2mqtt - Connected outlets warning

Configuration
1

Hello everyone,

While updating my tests with @pierre-gilles on the Google Home integration, he noticed warnings in the log that would be related to the Zigbee2mqtt integration.

Here are the warnings in question:

2021-10-10T18:05:03+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x7cb03eaa0a0826c6, feature linkquality not configured in Gladys.
2021-10-10T18:05:03+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x7cb03eaa0a0826c6, feature update not configured in Gladys.
2021-10-10T18:05:03+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x7cb03eaa0a0826c6, feature update_available not configured in Gladys.
2021-10-10T18:05:03+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x7cb03eaa0a0826c6, feature linkquality not configured in Gladys.
2021-10-10T18:05:04+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x7cb03eaa0a0826c6, feature update not configured in Gladys.
2021-10-10T18:05:04+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x7cb03eaa0a0826c6, feature update_available not configured in Gladys.

The connected plugs work perfectly under Gladys. My problem is that one of these two connected plugs remains in the on state under Google Home. I also specify that the two connected plugs are of the same brand.

2

Hello.
In the Zigbee2Mqtt integration, the « features Â» not handled by Gladys (as they are not present in the core part) are logged in this form.
Here, linkquality is at the value corresponding to the quality of the link between your outlet and the Zigbee key.
update and update_available indicate that you can update your outlets (via OTA or otherwise): Zigbee2MQTT

I don’t see a link between these logs and your Google Home problem.

3

@Mastho Mince on our response, we’ll have to dig a bit deeper then…

4

Good news! After rebooting the Google Home, the connected outlet under it is now synchronized with Gladys. Not surprising after all, given that @pierre-gilles no longer saw errors under Gladys Plus and that the Zigbee2mqtt warnings had nothing to do with it…

5

Oh, good it wasn’t from us, you scared me @Mastho! :stuck_out_tongue:

Thanks for the update!