Closed cribskip closed 5 years ago
This seems to boil down to be an issue with labels defined in .items
vs labels defined in .sitemap
. Can you change your item definition to Number TSBad "Bad [%.1f °C]"
?
@mueller-ma Wow. Amazing. Perfect fit!
I changed my item definition as you proposed and after a little while, the selction dialog appears correctly.
We probably shouldn't crash due to the broken format specifier though...we should catch IllegalFormatPrecisionException as well.
Also: the format string in the sitemap should be prioritised.
the format string in the sitemap should be prioritised
IIRC that one isn't part of the sitemap API response
Maybe the App should not send Units when the item's definition does not include such as this confuses the rules engine e.g. "Number TSBad..." vs. "Number:temperature TSBad".
That would make sense, but the 'maybe' part still irks me a bit. Is there any documentation on the expected client behavior with UoM somewhere?
IIRC that one isn't part of the sitemap API response
Indeed, it isn't. The crash is fixed in #1235.
Actual behaviour
When trying to set a temperature, the selection dialog only offers integer values, before there have been numbers in .1 precision.
Expected behaviour
Selection dialog should display new value in .1 precision.
Steps to reproduce
Number TSBad "Bad [%.0f °C]"
Setpoint item=TSBad label="Bad [%02.1f °C]" step=0.1 maxValue=25.5 minValue=20
Item 'TSBad' received command 20 °C
[5. Furthermore, openhab seems to interpret the number as a really big number as my heating rule shows -272,25 °C temperature missing in the room]Can you reproduce the issue in demo mode?
Could not open the demo server in the app
Notes
The issue was introduced somewhere between App version 2.5.0 and 2.5.16.
Environment data
Client
Server
openHAB Cloud
Logs
App log
openHAB Server log