Thanks for your feedback 
@mutmut did you do something?
Maybe depending on my availability I could help and do it?
Apart from filling out the Excel file, that’s all I’ve done and I won’t be able to do any more.
I’m reviving the topic a bit, I don’t know if I can help in one way or another for the next steps.
If I understood correctly, the Excel catalog seems complete… we need to move on to the front-end development phase, right?
I don’t remember putting everything that has been done around the electric vehicle, so there might be things to review.
Hi @guim31, indeed we need to get started on the development!
On my side, it’s not a priority for now. However, if someone takes on the subject, develops the feature, tests it properly and proposes a PR ready to be merged, I will add it to Gladys with great pleasure
I launched a Cursor agent on the topic, and it developed this catalog for me, the result is really clean 
List of MQTT devices:
Editing an MQTT device:
Adding a new feature with the catalog:
The catalog displays the final rendering of each feature, so it’s very clear.
I really like the result
If you ever want to test the PR:
It’s even possible via Gladys Plus on an existing instance, since it’s pure frontend:
https://cursor-mqtt-virtual-device-u.gladys-plus.pages.dev/
Feedback welcome!
I like it. For feedback:
-
Dark mode, the black a bit too gloomy:
-
The „Is this a sensor?‟ button is still broken, I think it already was.
-
The „Back‟ button still stands out more with this new design (but it already did ^^), an opportunity to review it? Even if I know it’s not related to MQTT ^^
But otherwise, yes, I find this new design with the catalog much better!
Oh yes, much better 
And he also fixed the „Is this a sensor‟ button!!
And I’m doing all this from my phone right now — 75% off Cursor credits if you go through the iOS app 
@Will_71 Thanks for the feedback, it’s fixed for « Currency »
A very practical UX improvement, the external ID is now automatically filled in, with the device name and a few random characters to avoid collisions:
And it also works on features:
The new MQTT catalog is merged and will be included in the next version of Gladys 
Sorry, couldn’t test earlier and so I have some feedback…
Small remark about the search, accents are absolutely necessary 
Speed level: no % for me as we already have a speed (%)
Leak: it’s a sensor, not a switch for me
Brightness: add % as a unit
Hue and saturation: issue with the legend and control?
Same for these:
Motion detector: yes/no sensor and not a controller, active/inactive motion detection (instead of press)
For music, I’ve always had issues with these sensors that should be controllers, right (except state)? For TV, we have Press.
Opening: sensor and not switch
pH: no unit for me
Detectors in general: yes/no sensor and not Press or switch
Shutter position: unit in %
Then the anti-theft for the sockets, I didn’t understand If it’s the child lock, it’s an on/off switch
Energy consumed: unit in kWh
UV sensor: no unit
Angles: unit °
COV NO2 indices: either we remove (integer), or we put an integer
Input state: sensor or switch?
Well, sorry again for the check and tests being so long
Otherwise, the previews for the dashboard are really great and ultra-explicit, and that’s awesome 
Thanks a lot for the feedback @mutmut, it’s not too late, I’ll integrate that before the release!
@mutmut It’s fixed here: Fix MQTT feature catalog feedback from community forum by Pierre-Gilles · Pull Request #2634 · GladysAssistant/Gladys · GitHub
Actually, it’s a legacy feature related to the old Z-Wave integration. It’s not useful code in the MQTT integration, so I’ve hidden it.
Thanks for your feedback!
This feature is available in Gladys Assistant 4.82:
Thanks to everyone for your help and feedback 