# MQTT device creation - semantic improvement **URL:** \ **Category:** Demande de fonctionnalités\ **Tags:** mqtt\ **Created:** [November 9, 2023, 12:25pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469 "2023-11-09T12:25:33Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [November 9, 2023, 12:25pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/1 "2023-11-09T12:25:33Z")
Hello This is a purely aesthetic feature but it seems clearer to me for those who, like me, have a slow brain and aren’t very ‹ with it › 🤣. When creating MQTT devices I find it would be easier to understand to ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [November 9, 2023, 5:23pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/2 "2023-11-09T17:23:10Z")
Hello, There are two requirements in one request (it’s better to create a request for your « copy » button) 😮‍💨 I don’t see the added value of the first ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [November 10, 2023, 9:24am UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/3 "2023-11-10T09:24:13Z")
Hello @spenceur, > [@spenceur](#): > > I don’t understand the added value of the first request personally, especially if it’s just for the comfort of one or two users, but oh well 🙃. Well, I find that it highlights and emphasizes the « Gladys to the outside » meaning more in the case I’m proposing! The first one, I find, seems more ambiguous regarding the direction of listening and publishing… > [@spenceur](#): > > I think it’s not much to do, so it’s better that you make the change and submit the PR 🫣 I admit I would do it, but I don’t really know how to do it 🥴 if you could give me some pointers for that I’d be grateful! 😉 It could help me for other cases too! 😊 ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [November 10, 2023, 11:31am UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/4 "2023-11-10T11:31:10Z")
> [@cce66](#): > > I admit I’d love to do it but I don’t really know how to 🥴 if you could give me some pointers for that I’d be grateful! 😉 It could be useful for other cases! 😊 > > ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [November 10, 2023, 4:28pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/5 "2023-11-10T16:28:47Z")
Thanks @spenceur, but what do I do next? I’m a beginner in this area on GitHub… 😥 ---
**Author:** ![Tlse-vins](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/tlse-vins/32/6054_2.png) [@Tlse-vins](https://community.gladysassistant.com/u/Tlse-vins)\ **Post date:** [November 10, 2023, 4:33pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/6 "2023-11-10T16:33:23Z")
Look at this tutorial — you should be able to do it. > [@Nouveau tutoriel : Mettre en place un environnement de développement sous Windows](https://community.gladysassistant.com/t/nouveau-tutoriel-mettre-en-place-un-environnement-de-developpement-sous-windows/5900): > > Salut à tous, Pour tous ceux qui veulent aider au développement de Gladys, il manquait jusque-là un tutoriel pour mettre en place un environnement de développement Gladys 4 sous Windows. La raison est simple: je fonctionne sous MacOS/Linux, et je n’ai aucune expérience sous Windows. Heureusement, @VonOx nous a fait un super tutoriel pour développer sous Windows avec WSL! Pour ceux qui sont sous MacOS/Linux: Merci @VonOx pour ce super tutoriel ! :warning:Attention, ce tutoriel est desti… ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [November 10, 2023, 5:17pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/7 "2023-11-10T17:17:20Z")
Thanks @Tlse-vins, I’ll take a look at that! ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [November 30, 2023, 9:00am UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/8 "2023-11-30T09:00:03Z")
> [@cce66](#): > > The version with a button to copy the topic would be even better (that’s more semantics I admit! 😊) It’s impossible to use the copy/paste API on a non-HTTPS site. Possible on Gladys Plus but not locally, so this feature was removed (it existed in the past). We could put it back on Gladys Plus 🙂 For the changes to the titles, the change isn’t obvious to me. The text below already explains well what it does, doesn’t it? ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [November 30, 2023, 10:43am UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/9 "2023-11-30T10:43:35Z")
Too bad about the copy-paste 😢 > [@pierre-gilles](#): > > Doesn’t the text below already explain well what it does? Yes, but I find the implicit meaning is missing, maybe add the meaning so that it’s instantly clearer? MQTT topic to publish =\> MQTT topic to publish to Gladys MQTT topic to listen to =\> MQTT topic to listen to from Gladys As it stands, I often tend to copy the wrong topic 🙄 I don’t know if I’m the only one in this case… 🙂 ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [November 30, 2023, 10:44am UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/10 "2023-11-30T10:44:53Z")
> [@cce66](#): > > Yes, but it’s the implicit meaning that’s missing, I think — maybe add the meaning so that it’s instantly clearer? OK I understand, no problem making that more explicit ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [November 30, 2023, 12:57pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/11 "2023-11-30T12:57:51Z")
@cce66 I’ve left feedback on your PR: > > > corrections typo et proposition changement libellé sur les appareils MQTT > > \###… Pull Request check-list > > To ensure your Pull Request can be accepted as fast as possible, make sure to review and check all of these items: > > \- \[\] If your changes affects code, did your write the tests? > \- \[\] Are tests passing? (\`npm test\` on both front/server) > \- \[\] Is the linter passing? (\`npm run eslint\` on both front/server) > \- \[\] Did you run prettier? (\`npm run prettier\` on both front/server) > \- \[\] If you are adding a new features/services, did you run integration comparator? (\`npm run compare-translations\` on front) > \- \[\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[french forum\](https://community.gladysassistant.com/)/\[english forum\](https://en-community.gladysassistant.com/)) for testing before merging. > \- \[\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code) > \- \[\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com). > \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com). > > NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. > > \### Description of change > > Please provide a description of the change here. It's always best with screenshots, so don't hesitate to add some! ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 7, 2023, 1:12pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/12 "2023-12-07T13:12:53Z")
@cce66 You made quite a few PRs over the past few weeks, I left feedback on those PRs but without any response from you I don’t know if you saw them? 🙂 ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [December 7, 2023, 1:17pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/13 "2023-12-07T13:17:01Z")
Ah yes, I saw it then I had a solar panel failure just after and I zoned out… my memory is failing! Ohhhh dear 🤣 I’ll check now — I’m thinking about it this PM and I’ll look at it tonight with a clear head 👍 ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [December 8, 2023, 1:54pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/14 "2023-12-08T13:54:32Z")
@pierre-gilles I made the PRs and fixed one or two extra things — tell me if it’s OK or if I still have something to do (not comfortable with GitHub 🙃) ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 8, 2023, 2:56pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/15 "2023-12-08T14:56:09Z")
I’ve left feedback on this PR: > > > \### Pull Request check-list > > To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items: > > \- \[\] If your changes affects code, did your write the tests? > \- \[\] Are tests passing? (\`npm test\` on both front/server) > \- \[\] Is the linter passing? (\`npm run eslint\` on both front/server) > \- \[\] Did you run prettier? (\`npm run prettier\` on both front/server) > \- \[\] If you are adding a new features/services, did you run integration comparator? (\`npm run compare-translations\` on front) > \- \[\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[french forum\](https://community.gladysassistant.com/)/\[english forum\](https://en-community.gladysassistant.com/)) for testing before merging. > \- \[\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code) > \- \[\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com). > \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com). > > NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. > > \### Description of change > > Please provide a description of the change here. It's always best with screenshots, so don't hesitate to add some! As for the others, which PR are you talking about? Can you put a link here? ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [December 8, 2023, 5:25pm UTC](https://community.gladysassistant.com/t/creation-dappareil-mqtt-amelioration-semantique/8469/16 "2023-12-08T17:25:39Z")
Excuse me, no others for the moment, I was only talking about that one!