Currently it is set to 20° C. Then I click up (or down) in der Basic UI and this happens in the log:
2018-11-01 15:55:05.695 [ome.event.ItemCommandEvent] - Item ‘temp_wohnzimmer_soll’ received command 8 °C
2018-11-01 15:55:05.723 [nt.ItemStatePredictedEvent] - temp_wohnzimmer_soll predicted to become 8 °C
2018-11-01 15:55:05.735 [vent.ItemStateChangedEvent] - temp_wohnzimmer_soll changed from 2E+1 °C to 8 °C
It seems that for some reason, the value is saved as scientific notation an that the basic ui can’t handle this and goes to the lowest possible value.
Any idea? Is this a bug?
I’m currently thinking of a workaround that, wenn the setpoint is changed to 8° I change it per rule to 20°, but that is just a workaround, not a real solution
I had the same problem yesterday with them.
You must attach °C or °F to the setpoint value.
For me this works in a rule:
rule "updateHeizungWohnzimmer"
when
Item temp_wohnzimmer_soll changed
then
val setPointValue = temp_wohnzimmer_soll.state
temp_wohnzimmer_soll.sendCommand(setPointValue + "°C")
end
Yes. Everything works - except changing from 20° at the basic UI at some times. I have now implemented the following rule als workaround:
rule "Fix WohnSoll"
when
Item temp_wohnzimmer_soll changed
then
if (temp_wohnzimmer_soll.state == 8|"°C"
&& previousState == 2E+1|"°C") {
temp_wohnzimmer_soll.sendCommand(20|"°C")
}
end
I have similar behaviour with the same device. I didn’t care that much about the basic UI issue though.
Where I have issues is in habpanel where the widget looks like this:
I know how to strip the unit but how can I convince openhab to not use 2E+1 but 20?