# August 27, 2025 - Strict validation of unit values in the measurement fragments
**URL:** https://community.cumulocity.com/t/august-27-2025-strict-validation-of-unit-values-in-the-measurement-fragments/12697
**Category:** Platform services
**Tags:** Announcement, platform-services, core-platform
**Created:** [August 30, 2025, 7:04am UTC](https://community.cumulocity.com/t/august-27-2025-strict-validation-of-unit-values-in-the-measurement-fragments/12697 "2025-08-30T07:04:01Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@cumulocity](https://community.cumulocity.com/u/cumulocity)
#### Post date: [August 30, 2025, 7:04am UTC](https://community.cumulocity.com/t/august-27-2025-strict-validation-of-unit-values-in-the-measurement-fragments/12697/1 "2025-08-30T07:04:02Z")
## Context
* * *
**Change Type:** Announcement
**Product area:** Platform services
**Component:** Core platform
> **Technical details**
>
> **Build artifact:** cumulocity
> **Internal ID:** MTM-64519
## Description
* * *
In future releases, the Cumulocity platform will strictly validate unit values in measurement fragments.
If a measurement fragment contains a unit value that is null or an empty string, the platform will ignore such unit values and won’t persist them. The measurement itself will still be stored, but without the invalid unit.
This change improves data quality and consistency. Review your integrations and make sure that all measurement fragments use valid, non-empty unit values or omit the unit field entirely.
---
### Author:  [@ChristophRose](https://community.cumulocity.com/u/ChristophRose)
#### Post date: [September 1, 2025, 10:56am UTC](https://community.cumulocity.com/t/august-27-2025-strict-validation-of-unit-values-in-the-measurement-fragments/12697/2 "2025-09-01T10:56:13Z")
Just to be 100% certain I understand this correctly:
Allowed:
tedge mqtt pub ‘te/device/main///m/environment’ ‘{“Temperature”: { “value”: 42.7, “unit”: “°C” }}’
but also
tedge mqtt pub ‘te/device/main///m/environment’ ‘{ “Temperature”: 25}’
Not allowed:
tedge mqtt pub ‘te/device/main///m/environment’ ‘{“Temperature”: { “value”: 42.7, “unit”: “” }}’
---
### Author:  [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)
#### Post date: [September 1, 2025, 8:59pm UTC](https://community.cumulocity.com/t/august-27-2025-strict-validation-of-unit-values-in-the-measurement-fragments/12697/3 "2025-09-01T20:59:04Z")
This is a change for the platform APIs and you are using Thin Edge to illustrate the matter. While I am not sure exactly how Thin Edge behaves in these cases, your summary of the platform behavior is accurate. Though “not allowed” means only the unit is not stored. The measurement itself will be stored and there will be no error message.
---
### Author:  [@Didier\_Wenzek](https://community.cumulocity.com/u/Didier_Wenzek)
#### Post date: [September 2, 2025, 7:28am UTC](https://community.cumulocity.com/t/august-27-2025-strict-validation-of-unit-values-in-the-measurement-fragments/12697/4 "2025-09-02T07:28:34Z")
thin-edge doesn’t currently support units.
So only the following is a valid thin-edge input:
`tedge mqtt pub te/device/main///m/environment ‘{ “Temperature”: 25}’`
leading to the following message sent to c8y:
`{`
` “Temperature”:{“Temperature”:{“value”:25.0}},`
` “time”:“2025-09-02T07:21:55.521501557Z”,`
` “type”:“environment”`
`}`
And as far as I understand this post, this message will be accepted by C8Y , the unit field being omitted entirely.
There is a plan for thin-edge to support units. Unfortunately this has not been implemented yet. See [MQTT API | Thin-edge](https://thin-edge.github.io/thin-edge.io/references/mqtt-api/#telemetry-type-metadata) . We are open to discussion.
---
### Author:  [@ChristophRose](https://community.cumulocity.com/u/ChristophRose)
#### Post date: [September 2, 2025, 10:14am UTC](https://community.cumulocity.com/t/august-27-2025-strict-validation-of-unit-values-in-the-measurement-fragments/12697/5 "2025-09-02T10:14:48Z")
> Though “not allowed” means only the unit is not stored. The measurement itself will be stored and there will be no error message.
Thanks for that clarification.
I created a new topic for the thin edge measurement topic: [Thin Edge and units](https://community.cumulocity.com/t/thin-edge-and-units/12701)