Thermostat choices - NodeLink and local API

[telljcl]

Was looking at the Ecobee 'stats (since they appear to work with Nodelink) but read a thread about the Ecobee API (assume local) being lousy.

Currently using Venstar T5900s and one T7900, but wondering what the current state of 'stats / NodeLink / ISY is?

ISY / Nodelink integration and communication seems to be pretty good in my experience (esp. with v5 ISY update, using Nodelink instead of Venlink), but I'm not the biggest fan of the 'stat operation - it works though.

So I assume that any of the newer Honeywell and Ecobee units will also fold into NodeLink via a local API?

Can somebody quickly enumerate pros / cons of each choice at the moment (or maybe point me to a previous but recent discussion of same?)

Thanks!

[io_guy]

New Venstars work fine.  All Ecobees are cloud.  

[telljcl]

1 hour ago, io_guy said:

New Venstars work fine.  All Ecobees are cloud.  

Don't want that... So are the Venstars the only thing out there (that work with NodeLink) that have a local API?

That's why I ended up with them originally (so I could use your Venstar pgm.)

Thanks

 

 

[io_guy]

Yep, only option.  

[telljcl]

2 hours ago, io_guy said:

Yep, only option.  

Quick question on Venstar T7900 and NodeLink, if I can:

On my T5900 (with a wired remote temp sensor attached), in ISY I have a node for the thermostat, and another for the remote temp sensor for it.

I'm wondering if on the T7900, with 1 or more of the optional wifi remote temp sensors set up, if they each have their own node in the ISY / NodeLink?

I was thinking that might be an easy way to add temp sensors for things other than HVAC, if I don't set up the stat to use them in the temperature averaging, but they report to ISY / NodeLink.

Is this doable?

Thanks

[io_guy]

Yep,

Each wireless is auto-added as an additional subnode.  

[telljcl]

17 minutes ago, io_guy said:

Yep,

Each wireless is auto-added as an additional subnode.  

Nice... Thanks!