Je l’avais signalé pour des scènes et c’est déjà corrigé, mais il y a le même phénomène sur les appareils mqtt : leur nom est tronqué sur mon iPhone.
C’est soit parce que le nom est un peu long, soit parce que l’info est très large. Quelques exemples :
Je l’ai vu aussi en mode Desktop les ....
Je mettrais le Pas de valeur récente sur 2 lignes pour gagner encore de la place.
Salut tout le monde !
Ce sujet est désormais en cours de développement .
Une PR a été ouverte pour afficher entièrement les noms MQTT trop longs dans le widget appareils du dashboard, au lieu de les tronquer :
master ← claude/mqtt-device-names-mobile-jlb0q1
ouvert 08:42AM - 29 Aug 26 UTC
### Description
On the dashboard devices widget, long device/feature names — ty… pical of MQTT devices, where the feature name carries all the context — were ellipsized down to a few characters on mobile, even when the control next to them was a mere switch or value badge.
The root cause: the widget rows are a real table, so its three columns were **shared by every row of the card**. One wide control (a shutter button group, a setpoint capsule) claimed that width for the whole control column, and every name of the card was crushed against it, while narrower rows showed a large dead gap.
This change (CSS only — the `<tr>/<td>` markup of the 25+ feature components is untouched) makes each widget row an independent flex row, like the scene rows already are:
- the control keeps exactly its natural width and hit area, whatever the name's length;
- the name gets every remaining pixel of **its own row**, and wraps on several lines (`overflow-wrap: anywhere` breaks even single-token names like `Volet_roulant_chambre_parentale`) instead of being truncated;
- the slider is the one control allowed to give width back to a long name, down to a usable ~6rem floor, and the Bootstrap `.col` gutters in its cell (30px of dead width) are neutralized;
- the "no recent value" badge folds on two balanced lines instead of stealing half the row (suggested on the forum topic);
- the `select` fallback of the adaptive option controls gets a min/max width so a long name can't crush it to its arrow.
The buttons→dropdown adaptive mechanism (`acAdaptiveControls`) keeps working: `nowrap` control cells never shrink below their natural width, so an oversized button group still overflows the `.table-responsive` box, which is what the coordinator measures.
Verified with real renderings (Chromium, 390px iPhone viewport, FR locale, demo mode) on a widget mixing 8 feature families with long MQTT names — switch, sensor value, no-recent-value badge, shutter button group, slider, adaptive mode control, setpoint stepper, merged light row — plus the short-name widgets (no regression) and a narrow 3-column desktop card.
| Before (mobile) | After (mobile) |
|---|---|
| Every name cut to ~5 characters (`Prise…`, `Temp…`, `Humi…`) against the width claimed by the widest control of the card | Names readable on 2-3 lines, controls unchanged, dead gaps gone |
## Forum
Forum: https://community.gladysassistant.com/t/sur-mobile-noms-dappareils-mqtt-tronque-sur-le-dashboard/10746
### Checklist
- [x] Tests pass: server untouched (front CSS + one className only); Cypress suite not run in this environment — the change is visual, verified with real browser renderings at mobile and desktop viewports
- [x] Linter and prettier pass on both front and server (`npm run eslint`, `npm run prettier`)
- [x] No undocumented breaking change
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01Lkhkpg8WqqMWxyPULoBtao
---
_Generated by [Claude Code](https://claude.ai/code/session_01Lkhkpg8WqqMWxyPULoBtao)_
N’hésitez pas à suivre la PR, à tester (optionnel, surtout pour les petites demandes) et à faire vos retours ici si besoin.
Preneur de testeurs sur cette URL :
Testé, et je valide. Merci
Cette méthode de test est super pratique, mais par contre, je passe l’étape 2FA avec des codes de récupération, parce que je ne me rappelle plus avoir configuré une appli 2FA pour Gladys.
Top ! Je merge.
Je viens de te désactiver la 2FA, tu peux te reconnecter et il faudra la reconfigurer
