App messes up setpoint values that end in zero

So my thermostat setpoint is now a number:temperature type. And when the setpoint value is changed in any other method to a value that ends in a zero it someone gets changed or corrputed. For instance if changed from 71 to 70 in basic UI and then viewed in the iOS app it changed to being stored as 7E+1 and shows up as a 7 in the app.

Here is a view of the events. Here i changed it in the basic UI and then viewed in the iOS app then chagned the value back in the basic UI without refreshing the page. A refresh of the basic UI page would revert the setpoint value to 60.

2018-07-30 13:54:41.001 [ome.event.ItemCommandEvent] - Item 'HVAC_CoolSetPoint' received command 71 °F
2018-07-30 13:54:41.003 [vent.ItemStateChangedEvent] - HVAC_CoolSetPoint changed from 70.0 °F to 71 °F
2018-07-30 13:54:44.602 [ome.event.ItemCommandEvent] - Item 'HVAC_CoolSetPoint' received command 70 °F
2018-07-30 13:54:44.607 [vent.ItemStateChangedEvent] - HVAC_CoolSetPoint changed from 71 °F to 70 °F
2018-07-30 13:54:46.489 [vent.ItemStateChangedEvent] - HVAC_Operating_State changed from 0 to 2
2018-07-30 13:54:47.037 [vent.ItemStateChangedEvent] - HVAC_Fan_State changed from 0 to 1
2018-07-30 13:55:13.698 [ome.event.ItemCommandEvent] - Item 'HVAC_CoolSetPoint' received command 71 °F
2018-07-30 13:55:13.704 [vent.ItemStateChangedEvent] - HVAC_CoolSetPoint changed from 7E+1 °F to 71 °F

Anyone else seeing this issue?

What formatting (if any) strings are you using in your item/sitemap definitions for HVAC_CoolSetPoint? Try using “%.1f °F” so it always shows a decimal point (and isn’t converted to a string).

here is my item and sitemap definitions. I think i am already using your suggestion.

Number:Temperature HVAC_HeatSetPoint        "Setpoint [%.1f °F]"                            <thermostat>    (All,HVAC,gMyOpenHAB)                  {channel="zwave:device:512:node2:thermostat_setpoint_heating"}

Setpoint item=HVAC_CoolSetPoint visibility=[HVAC_Mode==2]  label="Cool setpoint[%.1f °F]" icon="temperature" minValue=60 maxValue=90 step=1

Which version of openhab are you running? I seem to remember an issue in a previous build where the step setting had to be a non-integer value (I had mine set to 0.9), otherwise strange things were happening to the setpoint value. If that’s the case, upgrade to the latest version (or change the step=1 to step=0.5 or similar as a workaround).

I’m running 2.3. I’ll change the step to 0.5 to see if that changes anything. But I also see this issue when the temperature is changed directly to anything with a zero via a rule.

If it continues happening after the change, consider opening an issue on the project’s Github page (UoM are a new addition since 2.3, so there’s a possibility you’ve identified an issue that got through testing).

So changing the setpoint value makes the issue go away.

Seems like a kludgy work around and like something is still broken for me. I would much prefer to have a step of 1 degree for my setpoint sliders?