Yeah, I have it connected to my wifi currently and I can use the Nexia app to control it. I can create automations in the Nexia app and use IFTTT to trigger them. So I can control it through HE if I wanted (have not currently set it up to do so though), but it would be nice to have the communication be local and not have to rely on 2 separate cloud servers.
We've had issues with the thermostat ever since we got it, and if you look around on the Internet, there's lot of people with the same problem. If I had known getting a variable speed system would lock me into a certain thermostat, I would have looked around for the most efficient 2-stage system instead and used something like an Ecobee.
The issue is that it consistently shows the indoor temp as warmer than it actually is, so the AC doesn't shut off until it gets well below what the temperature is set to. There's several threads about it on forums if you google something like "trane xl 850 runs hot". One prevailing theory is that the wifi chip generates enough heat that it messes with the thermostat. Some people have said that when they disable wifi, it works correctly. But that defeats one of the purposes of having a smart thermostat.
I plan on building up my zwave network with some devices that can also report temperature, and then I can just use those to trigger turning the AC on or off.
EDIT: The automations I can currently create are a little limited. For example, I can't create one to "lower the temp by 2 degrees" and trigger it when the oven turns on. I have to create a "profile" and give it a set temperature value and then I can trigger that profile to run. So if the temp is currently 74 and the automation is set to 74, nothing changes. Even if I set it up in HE using IFTTT, that won't change. This is the main reason I'd like zwave control. I think it would be possible to have more control.
