# Min/max in text values

**URL:** <https://community.gladysassistant.com/t/min-max-dans-les-valeurs-texte/11593>\
**Category:** Développement\
**Created:** [November 15, 2026, 9:31pm UTC](https://community.gladysassistant.com/t/min-max-dans-les-valeurs-texte/11593 "2026-11-15T21:31:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\
**Post date:** [November 15, 2026, 9:31pm UTC](https://community.gladysassistant.com/t/min-max-dans-les-valeurs-texte/11593/1 "2026-11-15T21:31:58Z")

</div>

When developing an external integration, an error “HTTP 422 — UNPROCESSABLE\_ENTITY — t\_device\_feature.min cannot be null; t\_device\_feature.max cannot be null” consistently occurs when registering a device containing a text feature.

The PRs:

> <https://github.com/GladysAssistant/Gladys/pull/3382>
>
> …tion would refuse
> 
> POST /api/integration/v1/discovered\_device accepted a featur…e without min / max (typically a text feature), without name, read\_only or has\_feedback. The Discovery screen listed the device, and the user only got "HTTP 422 t\_device\_feature.min cannot be null" when clicking "Add", far from the integration's code and its developer.
> 
> The host API now checks the NOT NULL columns of t\_device\_feature that have no default value: a non-empty name, booleans read\_only and has\_feedback, finite numbers min and max (0 / 0 for a feature without a range). A violation is a 400 naming the feature, like an unknown category or unit, visible in the integration logs at publication.
> 
> Spec: contracts/host-api-endpoints.md (POST /discovered\_device rules).
> 
> 
> Claude-Session: https://claude.ai/code/session\_0134kXPPjevuPMP3oEuzaF3m
> 
> \### Description
> 
> 
> 
> \### Related request
> 
> Forum: https://community.gladysassistant.com/t/min-max-dans-les-valeurs-texte/11593
> 
> 
> \### Checklist
> 
> \- \[\] If a forum topic or GitHub issue exists, the description links it (\`Forum: https://community.gladysassistant.com/t/...\` or \`Closes #...\`)
> \- \[\] Tests pass: \`cd server && npm run coverage\` (Codecov requires 100% coverage on changed lines) and Cypress (\`npm run cypress:run\`) if the UI changed
> \- \[\] Linter and prettier pass on both front and server (\`npm run eslint\`, \`npm run prettier\`)
> \- \[\] No undocumented breaking change

> <https://github.com/GladysAssistant/integration-sdk-js/pull/49>
>
> The fake Gladys accepted a discovered feature without min / max (a text feature,… typically), without name, read\_only or has\_feedback. Gladys stores those columns as NOT NULL: the device was then refused when the user clicked "Add" on the Discovery screen ("t\_device\_feature.min cannot be null"), a bug the integration's own tests could never catch.
> 
> validateDiscoveredDevices now checks them like the Gladys host API does since GladysAssistant/Gladys (companion PR): a non-empty name, booleans read\_only and has\_feedback, finite numbers min and max (0 / 0 for a feature without a range). The DeviceFeature typing and the README say so.
> 
> 
> Claude-Session: https://claude.ai/code/session\_0134kXPPjevuPMP3oEuzaF3m
> 
> Forum : https://community.gladysassistant.com/t/min-max-dans-les-valeurs-texte/11593
