You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stepping the temperature setpoint on a thermostat with the BasicUI controls, with the thermostat configured for Celsius, frequently results in a floating-point value with a lot of decimals being sent to the channel, even if the starting value was an integer. This causes an exception in the binding, which seems to error out on high-precision numbers.
There is of course no value in keeping all these decimals, they are just a rounding artefact. I think the binding should discard them.
Observed behavior: The change does not take effect.
Expected behavior: Lowering the temperature works. Rounding happens where needed (presumably in the binding).
Stepping the temperature setpoint on a thermostat with the BasicUI controls, with the thermostat configured for Celsius, frequently results in a floating-point value with a lot of decimals being sent to the channel, even if the starting value was an integer. This causes an exception in the binding, which seems to error out on high-precision numbers.
There is of course no value in keeping all these decimals, they are just a rounding artefact. I think the binding should discard them.
Observed behavior: The change does not take effect.
Expected behavior: Lowering the temperature works. Rounding happens where needed (presumably in the binding).
Debug log:
This appears to be the same bug as openhab/openhab1-addons#3794.
The text was updated successfully, but these errors were encountered: