Announcement

Collapse
No announcement yet.

Minor issue with upgrade to 1.4.0.0

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

  • Minor issue with upgrade to 1.4.0.0

    This is just an FYI. I recently upgraded to 1.4.0.0. I noticed yesterday that none of my events that involved changing set points on my 3 thermostats was working. For each event (and there were many), the set point had been stripped. The problem was fixed by going into each event and selecting the set point again for each. Elliott

  • #2
    So you're saying wait for 1.4.0.1?

    Comment


    • #3
      Originally posted by wkearney99 View Post
      So you're saying wait for 1.4.0.1?
      Interesting, because on my Manage Plug-Ins page it only shows 1.4.0.0. It would make sense that it should be 1.4.0.1, but it doesn't show that presently.

      Comment


      • #4
        I think that's a reference to my need to CREATE a 1.4.0.1.

        Comment


        • #5
          Ok, think I figured this out - if you were using "Control a Device" to set the setpoint, this would have happened because I dropped the "°F/C" from the values to make sure I didn't have problems with Google Home/Alexa.

          If you're using the plugin-specific action to "change setpoint", then you won't be affected by this.

          I'm working on an update that will be more flexible in matching the value. [EDIT: Duh - I can't. This is in a built-in HomeSeer event, not something I can control or influence.]

          Comment


          • #6
            Originally posted by shill View Post
            Ok, think I figured this out - if you were using "Control a Device" to set the setpoint, this would have happened because I dropped the "°F/C" from the values to make sure I didn't have problems with Google Home/Alexa.

            If you're using the plugin-specific action to "change setpoint", then you won't be affected by this.

            I'm working on an update that will be more flexible in matching the value. [EDIT: Duh - I can't. This is in a built-in HomeSeer event, not something I can control or influence.]
            That is exactly how I have been doing this ("Control a Device"). I did not appreciate that there was a plugin-specific action to do this until now.

            Comment

            Working...
            X