[Devices] Getting the real names of integrations

mutmut · August 14, 2026, 4:54pm

In the new Devices page, we should use the real names of the integrations instead of the Docker image tags:

ext-callemand-gladys-melcould-home → MELCloud Home

cicoub13 · August 15, 2026, 2:00pm

Done in this PR Display integration names on the devices list by cicoub13 · Pull Request #2886 · GladysAssistant/Gladys · GitHub

There may be duplicates, so I specified when it’s a Community Integration + the exact suffix when the same name appears multiple times.

GBoulvin · August 15, 2026, 2:26pm

Just like on the ‹ services › page!

cicoub13 · August 15, 2026, 2:31pm

What is the Services page?

GBoulvin · August 15, 2026, 2:34pm

Settings, services

mutmut · August 15, 2026, 2:35pm

oh yes, I hadn’t seen that one!

cursor-bot · August 18, 2026, 2:16am

Hi everyone!

This topic is now in development.

A PR has been opened to display the real name of integrations on the Settings → Services page:

github.com/GladysAssistant/Gladys

Display integration names on the services settings page (#2942)

master ← claude/services-page-integration-names

ouvert 02:14AM - 18 Aug 26 UTC

Pierre-Gilles

+151 -58

Implements feature request: https://community.gladysassistant.com/t/appareils-av…oir-le-vrai-nom-des-integrations/10559 ### Description The devices part of this forum request was already shipped in #2886. This PR covers the remaining part reported in reply #3 and confirmed by the author: the same problem exists in **Settings → Services**, which still lists community integrations under their raw service name — the docker image based selector (`ext-callemand-gladys-melcould-home`) instead of their real name (`MELCloud Home`). What changes on the services page: - a community integration is listed under its manifest name, the same title as its card in the integration catalog, and still falls back to the raw service name when there is no manifest name; - it carries the same `Community` tag as in the catalog, so it stays distinguishable from a built-in integration with a similar name; - when two community integrations display the same name (two repositories publishing the same manifest name, or dev installs), each one carries its technical identity next to its name — exactly the rule introduced in #2886; - the list is sorted on the label it actually displays: a built-in integration is now sorted under its translated title instead of its service name, and a community one under its real name instead of its `ext-…` selector. The technical identity of every service stays visible: the `Internal name: …` line under the name is unchanged. Implementation notes: - the disambiguation helper written for the devices list is reused, not duplicated: `disambiguateIntegrationNames` moved from `front/src/routes/devices/integrationLinks.js` to `front/src/utils/integrationNames.js`, and both pages import it from there (the devices page behaviour is unchanged); - the integration lookup that `ServiceItem` did inline moved to `front/src/routes/settings/settings-service/serviceIntegration.js`, which resolves the display identity of a service (name, translation key, community flag, integration link) the same way the devices page does; - no server change, no new translation key: `integration.tags.external` already exists in every language file, and `GET /api/v1/service` already returns the service manifest. This PR was created by an automated Claude Code run. ## Forum Forum: https://community.gladysassistant.com/t/appareils-avoir-le-vrai-nom-des-integrations/10559 ### Checklist - [ ] Tests pass: `cd server && npm run coverage` (Codecov requires 100% coverage on changed lines) and Cypress (`npm run cypress:run`) if the UI changed - [x] Linter and prettier pass on both front and server (`npm run eslint`, `npm run prettier`) - [x] No undocumented breaking change Front only change: `npm run prettier-check`, `npm run eslint`, `npm run compare-translations` and `npm run build` all pass locally. No server file is touched, so the server suite and Codecov patch coverage are not impacted. Cypress was not run locally (binary unavailable in this environment); there is no E2E spec covering the services settings page, and CI runs it anyway. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Feel free to follow the PR, test (optional, especially for small requests) and give your feedback here if needed.

Topic		Replies	Views
Intégration externe - Accéder au changelog de la version actuelle ou future Demandes livrées in-progress	1	42	August 17, 2026
Pouvoir configurer la conservation ou non des appareils des intégrations externes Demandes livrées feature-core , in-progress	1	44	August 18, 2026
Demande de mise en place d'un bouton arrêt et redémarrage du raspberry Demandes livrées feature-core , in-progress	15	923	August 24, 2026
(Petite) Coquille page "Integrations" V4.12.0 Configuration	5	307	November 14, 2022
Affichage adresse IP Demandes livrées in-progress	16	245	August 20, 2026

[Devices] Getting the real names of integrations

Related topics