With the introduction of the widget creation tool, of course, I wanted to create my own simple small thermostat widget. I set it up to provide heat setpoint and turn red if the current mode is heat, and cold setpoint and turn blue if the current mode is cool. For some reason though, nevo doesn't want to switch between the two cleanly...

If I run the widget while the heat is on, it turns red and displays the heat setpoint - works great. Unfortunately, when I change the thermostat to cool mode, the widget turns blue, but is improperly getting the cool setpoint. At this point, I went into the ecosystem settings on the remote and tested the get setpoint for both heat and cool, and it checks out. As soon as I get out of the settings pages, the setpoint picks up properly. After that, when I flip back to heat mode, it turns red, but picks up the wrong setpoint again. If I repeat the steps for testing in the settings page and come back to the widget, it reports properly again.

Anyone else having issues with getting the setpoints correctly? This is a shlage/trane thermostat.

You may want to download the Widget User Guide which is now posted on MyNevo.com. It gives details on all of the blocks and some examples. The last example is for HVAC temp controls. The block diagram seems quite complex but you may be able to create what you need if you can decipher the image in the pdf file.

Eric

Not much help... actually the thermostat widget laid out in the widget guide indicates the get setpoint block having hex input and output (in red), but in fact, this block has blue integer input and output... strange...
I even tried creating 2 widgets on separate pages - one to check heat setpoint and one to check cool setpoint. They both pick up the same setpoint, depending on what the last setpoint was tested through the settings page.
Also, I tried installing the stock thermometer widgets and they work fine, so it seems unique to widgets I create.

OK... please help... I was able to simply recreate this with a setup similar to page 34 of the widget guide. If someone could confirm the same results, that would be super. Instead of using a "multilevel sensor get" block, I used a "thermostat setpoint get" with the default option of #1 heat.  I added it to a blank page and loaded onto the S70 and tested.  In the 50/50 chance it picked up the (correct) heat setpoint when I clicked the button, I went into the system settings on the S70 and went into Ecosystem, and then into the thermostat properties, clicked on test, and tested the get cool setpoint.  That picked up the cool setpoint.  Then I got out of setup screens and clicked the widget again, and now it's displaying the cool setpoint.
I can keep going back into the setup to the test screen and correctly poll both setpoints, but it seems the widget will only get the last setpoint that was polled through the set up screen.  Could someone please test this and confirm if this is happening to you???

I can email or post a copy of the simple widget design that I used to test this.

I got the same response as you; the widget can only get back the heating or cooling set points, but not both at the same time and when you go to the Ecosytem screen and test the other mode, it then only works for that new mode. I planned on eventually using nevo widgets for this purpose (I sometimes use the RCS z-wave thermostat), but I can't make it work the way it should either.

The alternative, and what I've done before NevoStudio Pro 3.0 came out, is to use only the heating and cooling set point pieces of the "HVAC #1 - Auto" module that you find in the Home Control tab. Just drag that module onto the interface, delete everything else besides the blue and red texted pieces and then associate the "Thermostat Setpoint Get" command to them (double click both pieces to make sure the Configuration Parameters tab settings are correct). This will allow you to get the correct heating and cooling set point values back. The only issue with this though, is that since it is outside of nevo widgets, I don't see how you'd be able to use that data in the widget for other purposes.

Thanks for confirming Ry... I decided to keep going with my widget this afternoon, figuring that I only change the mode twice a year, so I could update my remote, but discovered a new issue with the setpoints. Oddly enough, this issue also affects the thermostat setpoint set function as well. If I go into the setup and do a heating setpoint get, then all subsequent thermostat setpoint set functions called from a widget will set heating setpoints. Disappointing...