mutmut
14. August 2026 um 16:54
1
Auf der neuen Geräte-Seite sollten die echten Namen der Integrationen statt der Docker-Bild-Tags angezeigt werden:
ext-callemand-gladys-melcould-home → MELCloud Home
In diesem PR Display integration names on the devices list by cicoub13 · Pull Request #2886 · GladysAssistant/Gladys · GitHub
Es kann Dubletten geben, daher habe ich angegeben, wann es sich um eine Community-Integration handelt + den genauen Suffix, wenn es mehrere Einträge mit demselben Namen gibt.
Genau wie auf der Seite ‹ Dienstleistungen ›!
Was ist die Seite Dienste ?
mutmut
15. August 2026 um 14:35
6
ach ja, die hatte ich noch nicht gesehen!
Hallo zusammen!
Dieses Thema ist nun in Entwicklung .
Ein Pull Request wurde erstellt, um den echten Namen der Integrationen auf der Seite Einstellungen → Dienste anzuzeigen:
master ← claude/services-page-integration-names
ouvert 02:14AM - 18 Aug 26 UTC
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)
## Summary by CodeRabbit
* **Improvements**
* Improved service display names, including clearer labels for integrations with duplicate names.
* Services are now sorted by translated or manifest-provided names.
* Added localized names, external-service indicators, and direct links to integration dashboards.
* Improved handling of services without matching integration pages.
* Updated service-name styling for better alignment, spacing, and long-name display.
Zögert nicht, dem Pull Request zu folgen, zu testen (optional, vor allem bei kleinen Anfragen) und euer Feedback hier zu hinterlassen, falls nötig.
