The MQTT integration becomes "MQTT Virtual Devices"

Hi everyone :slightly_smiling_face:

I feel this is a topic that comes up often, especially among users coming from Home Assistant: the MQTT integration is sometimes misunderstood.

In Home Assistant, all devices whose data goes through an MQTT broker (Zigbee2MQTT, ZwaveJS, etc.) are generally grouped in the MQTT integration.

In Gladys, the paradigm is different: we operate with integrations per technology.

We clearly distinguish Zigbee, Z-Wave, Nuki, etc., even if internally these integrations may use MQTT.

To avoid this confusion, I therefore decided to rename the integration “MQTT” to “MQTT Virtual Devices”.

The idea is to make it clearer that this integration is meant to create custom devices via MQTT, and not to manage all equipment using MQTT in the background.

Here is how it looks in French and English :backhand_index_pointing_down:

The PR :

3 Likes