Hi everyone!
I’m releasing Gladys Assistant 4.41 today 
On the agenda, a long-awaited feature: the ability to listen to custom MQTT topics from the Gladys MQTT integration 
I present all of this
7 Likes
Great job everyone for the work!!
I have a few remarks after watching the video:
-
You suggested it quickly @pierre-gilles, but indeed I think we could consider changing the label of the MQTT integration to « Virtual devices », in any case a way to make this part more understandable and accessible. Quite a few people request features on the forum that are actually already possible thanks to these fake devices… maybe we should highlight that more.
-
I also think within the same integration we need to rethink this: Catalogue des features supportées en MQTT
Because as you showed with the risk level feature, I can’t guess that this feature expects a minimum value of 0 and a maximum of 3 … Unless I do specific research. I think this info should be available from the interface.
My 2 cents ! 
4 Likes
Thank you for your feedback, I agree with both points
2 Likes
Very good explanation. Another example of using the custom MQTT topic that links to 4.40 and 4.41: a person with an existing zigbee2MQTT setup who has a sensor not yet supported by Gladys could quite easily create an MQTT device to retrieve the metric they’re interested in while waiting for a native integration. A bit convoluted but it has the merit of being possible.
I quite like the idea of « Virtual devices » — it’s less « techy », however it should still be made clear that this relies on MQTT. Someone using Node-RED/Home Assistant flows might be a bit lost otherwise.
1 Like
Some people use it to send information via MQTT from physical devices. Could that cause confusion?
Sure… That’s why I’m putting the idea out there and waiting for others to come up with a better one than me 
The term needs to be thought through, but in