Announcement

Collapse
No announcement yet.

Thermostat Heating Setpoint Bug

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Thermostat Heating Setpoint Bug

    Hi, I think found another bug, pretty bad.

    I work in Celsius. Have a z-wave thermostat and it shows properly on the device page with the Heating 1 Setpoint set to 20C. I use the ui to change it to 19C and the change goes through, however, the ui now shows my setpoint as 66.2C = very bad. Basically it now shows Fahrenheit equivalent, but as if it is Celsius.

    What makes this really bad, is that i have scripts that read current setpoint and then increment or decrement it by 1. So next time my script reads it, it sees 66.2, increases it to 67.2 and sets it in CELSIUS!. That is freakishly hot.

    Anybody seen this?

    EDIT: I think this is the same bug as this:
    http://homeseer.com/bugzilla/show_bug.cgi?id=1280
    Last edited by Silentcossack; December 14, 2013, 03:07 PM.

    #2
    Just check and http://homeseer.com/bugzilla/ is working for me. Sorry I can't help with your problem.

    Barry

    Comment


      #3
      My evolve thermostat was converting from Ferenheight to celsius until tink fixed it. It had something to do with the way manufactuer was handling stuff. submit a bug report so he is aware.
      https://forums.homeseer.com/forum/de...plifier-plugin

      Comment


        #4
        my intermatic spa control is also converting Ferenheight to celsius
        Ubuntu on the Intel NUC ( 8i5BEK ), 32 G, 250G SSD, V4 Pro 😎

        Comment

        Working...
        X