Ya lo había reportado por escenas y ya está corregido, pero hay el mismo fenómeno en los dispositivos mqtt: su nombre está truncado en mi iPhone.
Es porque el nombre es un poco largo o porque la información es muy amplia. Algunos ejemplos:
mutmut
29 Agosto, 2026 08:12
2
También lo he visto en modo Desktop los ....
Pondría el Sin valor reciente en dos líneas para ganar aún más espacio.
¡Hola a todos!
Este tema ahora está en desarrollo .
Se ha abierto una PR para mostrar los nombres MQTT demasiado largos en el widget de dispositivos del panel de control, en lugar de truncarlos:
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)_
## Summary by CodeRabbit
* **Style**
* Improved device widget layouts for narrow screens and responsive displays.
* Device names can wrap more naturally without truncation.
* Controls and selectors maintain usable sizing and spacing.
* “No recent value” badges can wrap cleanly.
* Sliders now retain a practical minimum width.
No duden en seguir la PR, probar (opcional, especialmente para pequeñas solicitudes) y dar sus comentarios aquí si es necesario.
Prueba de probadores en esta URL:
Testé, y lo valido. Gracias
Este método de prueba es muy práctico, pero, por otro lado, paso el paso 2FA con códigos de recuperación, porque no recuerdo haber configurado una aplicación 2FA para Gladys.
¡Genial! Lo he fusionado.
Te acabo de desactivar la autenticación en dos pasos, puedes volver a conectarte y tendrás que volver a configurarla
