Ethernet / Local IP Thermostats

[residualimages]

Anyone have experience or recommendations with Ethernet or IP based Thermostats? 
EDIT for clarity: this is in pursuit of Local API control within the ISY (Native, NodeLink, Polyglot, or even Network Resource compatible hooks).

UP32H-IP runs around $500 MSRP but supposedly allows remote sensors and local API.
Think these are more likely based around commercial applications but if it works for residential... I'm seeing them for less than $300 on some sites.

Other options?

[paulbates]

I’ve been using 2 venstar colortouch T7900 thermostats for 4+ years. Local only api, reasonable hvac depth (humidity control, multiple heat cool stages, configurable stages calls, wired and wireless sensors- indoor and out... more). My wife uses the app to control temp, it supports Alexa. 

I use ISY firmware v5 and nodelink to control them. There’s a significant amount of features ISY programs can control. I’ve seen them for $170 delivered 

https://venstar.com/

Paul

[residualimages]

16 minutes ago, paulbates said:

significant amount of features ISY programs can control

Hey Paul - would it be a bother to show a quick screenshot of one of the thermostat devices from the Admin Console to get a visual on the node types? Edit: reread and you use Nodelink, something I haven't done yet. I've been a Polyglot user which exposes the devices as real devices in the tree to the ISY. I'll go read up on Nodelink. From what I see, it also creates virtual devices and nodes?

And do you have any wired / wireless sensors paired to it and / or integrated to your ISY?

(glad to see you've already answered my V5 firmware question. I run it too)

[paulbates]

Nodelink is another node platform. It requires .net. I use a Pi and Mono. Its one exe, a very install via a provided install script. Its one exe and a config.xml file which the web interface maintains. I have both polyglot and nodelink on a single RPI 2B, which is taking a nap on that load.

I have 2 thermostats and 3 wireless sensors :  2 internal, each installed in living spaces on the opposite floor than the thermostat, set to averaging between thermostat and sensor. 1 external installed on my deck and shared between the thermostats. The thermostats use the external temp, and the ISY can read it to anticipate high heat or very cold affecting the living spaces. I also use it for the ISY to kick off a "hot zones" sprinkling program

Here are some images:

One thermostat's nodes

Runtime node

 

Wireless Sensor Node

 

Paul

 

 

[residualimages]

I really appreciate the response, Paul. I started digging through the forums and saw some of your other posts but this is nicely succinct and looks to replicate or improve upon what Nest + Polyglot has (until the Aug 31 2019 Nest API kill date). 

Anything particularly "special" or problematic about these devices you've found in your 4+ years?

[paulbates]

I don't have any problems with them.

Cons:

• The screen can be a little overwhelming to the family as opposed to a Nest. But my approach is for the thermostat, sensors and ISY programs to keep the house comfortable so that no one is wanting to change it. Probably my most complex programs determine how much cycle time for the fan to keep temp in check based on external temp and temp difference between floors. Also, if you turn on the cloud feature (separate from local api), the app can be used to control it.
   
• It took time to get used to configuring it when calibrating stage 2 kick in for heat. The 2 areas of my house, each with HVAC system and thermostat, required different deadband degrees / delay time. Also working how much humidity to deliver without frosting windows. I used the runtime programs posted in nodelink to observe how hard each system was working for heat and humidity. Once I had it set, I haven't touched either in a number of years.

Paul

 

 

[lilyoyo1]

I use the ecobee3 and love it. Mine isn't added to my Isy as it works fine for me on its own. However if you want to control it with your Isy there is a node server for it. 

Should any of them go down, I'd love to try Glas. Not for any particular reason other than I like how it looks. 

[residualimages]

@lilyoyo1 - thanks for the recommendation, but from what I've read on ecobee sites and this forum, the ecobee API is cloud based, not local IP?

Glas uses Windows 10 IoT as its OS so maybe it can be accessed locally but I can't find any API documentation other than voice assistant "skills". 

 

 

[lilyoyo1]

54 minutes ago, residualimages said:

@lilyoyo1 - thanks for the recommendation, but from what I've read on ecobee sites and this forum, the ecobee API is cloud based, not local IP?

Glas uses Windows 10 IoT as its OS so maybe it can be accessed locally but I can't find any API documentation other than voice assistant "skills". 

 

 

I didn't know that was one of your requirements. It is cloud based so it wouldn't fit your needs

[residualimages]

3 minutes ago, lilyoyo1 said:

I didn't know that was one of your requirements

Well, that's what happens when you think the forum is a mind reader. 
Corrected the oversight in the original post, thanks.