# atmosphericPressureMeasurement Capability is Displayed Without Decimals in Android or iOs Apps **URL:** \ **Category:** Apps & Clients\ **Created:** [January 9, 2024, 12:56pm UTC](https://community.smartthings.com/t/atmosphericpressuremeasurement-capability-is-displayed-without-decimals-in-android-or-ios-apps/276389 "2024-01-09T12:56:43Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Mariano\_Colmenarejo](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/mariano_colmenarejo/32/220132_2.png) [@Mariano\_Colmenarejo](https://community.smartthings.com/u/Mariano_Colmenarejo)\ **Post date:** [January 9, 2024, 12:56pm UTC](https://community.smartthings.com/t/atmosphericpressuremeasurement-capability-is-displayed-without-decimals-in-android-or-ios-apps/276389/1 "2024-01-09T12:56:43Z")
Hi @nayelyz The atmosphericPressureMeasurement capability has the default unit “kPa” and a value of type number. A while ago, 1 or 2 years ago, could not send decimal values to the capability, it gave an type error. **Decimal values can now be sent and they are accepted correctly**. The App device history shows the value with 1 decimal, but the app details view does not show the decimal value. ![1000012569](https://global.discourse-cdn.com/smartthings/original/3X/d/5/d59b3c53ef72013533164bfa11ed25a0ea1e6932.png) ![1000012568](https://global.discourse-cdn.com/smartthings/original/3X/4/5/4560b22893a43af48e3a8b96586ba2427e3ec2f1.png) On [my.samrtthings.com](http://my.samrtthings.com) it is also shown with 1 decimal ![1000012570](https://global.discourse-cdn.com/smartthings/original/3X/3/6/3662e2b2f4ffaa7e156dd967819e1a18eba147d9.png) ---
**Author:** ![Johnnybegoode](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/johnnybegoode/32/172925_2.png) [@Johnnybegoode](https://community.smartthings.com/u/Johnnybegoode)\ **Post date:** [January 9, 2024, 3:53pm UTC](https://community.smartthings.com/t/atmosphericpressuremeasurement-capability-is-displayed-without-decimals-in-android-or-ios-apps/276389/2 "2024-01-09T15:53:43Z")
> [@Mariano\_Colmenarejo](#): > > The App device history shows the value with 1 decimal, but the app details view does not show the decimal value. The same case with the iOS app. ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [January 9, 2024, 4:41pm UTC](https://community.smartthings.com/t/atmosphericpressuremeasurement-capability-is-displayed-without-decimals-in-android-or-ios-apps/276389/3 "2024-01-09T16:41:06Z")
Hi, @Mariano_Colmenarejo Thank you for reporting this. I think this is related to the app’s plugin, I don’t know if it was intentional or not because in this view is where numbers are rounded, so, I’ll ask the corresponding team ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [April 2, 2024, 3:33pm UTC](https://community.smartthings.com/t/atmosphericpressuremeasurement-capability-is-displayed-without-decimals-in-android-or-ios-apps/276389/4 "2024-04-02T15:33:07Z")
Hi, @Mariano_Colmenarejo The latest app release has one decimal support for `atmosphericPressureMeasurement`, `gasMeter` and custom capabilities with the “numberField” display type which was also missing as mentioned here: > [@Capabilities with numeric type in Android App details view have a range from 0 to 100, by default](https://community.smartthings.com/t/capabilities-with-numeric-type-in-android-app-details-view-have-a-range-from-0-to-100-by-default/276899/9): > > Ok, then I don’t think it will be modified and instead, we’ll create a ticket to add a note in the documentation about it. The issue about the value being rounded is in a separate ticket along with the capabilities of atmosphericPressure and gasMeter Please, let us know if you see something different. ---
**Author:** ![Mariano\_Colmenarejo](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/mariano_colmenarejo/32/220132_2.png) [@Mariano\_Colmenarejo](https://community.smartthings.com/u/Mariano_Colmenarejo)\ **Post date:** [April 2, 2024, 4:00pm UTC](https://community.smartthings.com/t/atmosphericpressuremeasurement-capability-is-displayed-without-decimals-in-android-or-ios-apps/276389/5 "2024-04-02T16:00:35Z")
> [@nayelyz](#): > > Please, let us know if you see something different. Hi @nayelyz Numeric type capabilities are already shown in the details view with one decimal. but now it does not distinguish between the capabilities that have an **integer** and **numeric** type defined in the capability. Now they are all displayed with a decimal. > [@SmartThings Android App Updates - Version 1.8.13.22 (Mar ‘24)](https://community.smartthings.com/t/smartthings-android-app-updates-version-1-8-13-22-mar-24/279630/10): > > Hi @nayelyz @AlejandroPadilla The latest version of the App solved some things, such as that the numeric type capabilities are already shown in the details view with decimals but now it does not distinguish between the capabilities that have an integer and numeric type defined in the capability. Now they are all displayed with a decimal. Also, the text type capabilities have stopped displaying text in HTML format, which was the only known way to display text in more than two lines and with different font sizes in the App capabilities. It doesn’t make much sense that text-type capablities can be created with no character limit and then they can’t be displayed in the details view of the App. Is there a way to make the capability size expand to show the ful… ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [April 2, 2024, 6:05pm UTC](https://community.smartthings.com/t/atmosphericpressuremeasurement-capability-is-displayed-without-decimals-in-android-or-ios-apps/276389/6 "2024-04-02T18:05:19Z")
> [@Mariano\_Colmenarejo](#): > > t now it does not distinguish between the capabilities that have an **integer** and **numeric** type defined in the capability. ah, right. Sorry I didn’t remember this one and the team notified me yesterday, I asked them about this behavior to see if it’s expected.