I currently have many setpoint in my sitemaps and I found out that pressing the down arrow doesn’t work. Up arrow or clicking on the value and using the slider work in both direction, but down arrow doesn’t work for degree ([%.1f °C]). Also, while my step are set to 0.5, it increment in 1 when I press the arrow. On the slider, it will round to *.0
I also have Setpoints to define my radiator valve SetTemperatures in 0.5 °C steps, defining the minValue and maxValue with one decimal as well though. Might that be your issue?
My guess is that the item’s state description defines a format without decimal digits (%d or %0.f). The app uses that format to format the commands sent.
A state description might also be pushed by the binding.
The simplest way to check is whether Main UI lists ‘state description’ in the metadata list for the respective item (found under Settings → Items → ).
The safest way to check (because it matches what the app is seeing) is to open the URL http://<ohserver>:8080/rest/items/<itemname> in a browser and checking the pattern field in the returned stateDescription field (if present).
I did just find out that it’s working for other setpoint and that now, that specific setpoint doesn’t show the “,x” value in the slider. I did found out with the rest link you set that “pattern”:"%.0f” instead of 1f. Weirdly, in the ui, there’s nowhere it’s set, unless this set it:
No, it’s not the tag. As mentioned, bindings can push a default state description, and in absence of that, OH core will do that. State description metadata will just override that default. It’s a bit unfortunate though that the default state description is not shown in the UI.
I did see when cloning them though that when I selected number then a description like temperature, it showed me the state description and I could set it right there. But if the item is already created, there’s a message saying it cannot be modified there and must be modified through state description. Maybe if at least, it would show as read only the current value
