Get ready to make the switch!

[GSzabados (Gabor Szabados)]

@blake.arnold, @jody.albritton, @Brad_ST

Actually I don’t know that is it a bug or just an oversight by someone, who has just tickled with the UX pluggin. But it can be an other point in the previous list, high on the top.

@Philippe_Portes brought to my attention, that in the OneApp you cannot set temperatures to .5 values, what is a common practice when you measure temperature in Celsius.

I have tried it with my TRVs’ custom DH, which hasn’t been converted or changed for the past year and I have tried it with the other custom DH which uses vid:“generic-radiator-thermostat2”, what is used by the Everspring and Popp Zwave TRVs’ official ST DH.

@Philippe_Portes tried to set setPoint through the automation builder, but it is not allowing decimal point values.

@Philippe_Portes

That’s not about the DTH but about the new app rules builder.
At If stage, select a thermostat device, then temperature. That opens the editor but “.” is disable. Worlks fine in Farenheit but not in Celsius. I save $100 heating 18.5 rather than 19.

Myself tried with the aforementioned options in the Device’s tile/display. The classics app allows decimal values of .5. The new app shows the .5 value as it was set, but when I try to change by the slider or by pressing the value and trying to define them by the numerical input, when .5 added at the end the set function is disabled. So basically it is inpossible to define any value with .5 end. (I use Hungarian as my phone’s language and cannot test with English (United States) now. As some bugs were only affecting foreign languages.)
But the new app with this missing feature puts the temperature settings back to an analog turn-knob thermostats level. My 15-20 years old Computherm digital thermostat was able to use .5 values as standard. 5-6 years ago when I replaced that with a 1st Gen NEST thermostat, that was able to handle .5 values as standard. But the new OneApp and the connected UX plugin can set only numbers without decimal point, where the .5 values is a basic feature for decades in digital thermostats.

Although the answer of support is quite interesting “I’ll consider this request and forward it to the concerned team”.

@Philippe_Portes

“As of now, entering the decimal dot to the input is not possible and the feature is not available in the SmartThings application. However, i’ll consider this request and forward it to concerned team. Hoping it must be addressed at the earliest.”

I don’t understand what should be considered in this feature. Most of the world uses Celsius as standard and even the Samsung ACs could be set to .5 temperatures a few years ago, when I had one. I cannot see how is this feature/standard could be missed.