Nexia and Trane XL1050 / XL850 thermostat

It’s my understanding this only works for a limited set of American Standard or Trane thermostats. I think xl824 and up.

I originally had the xl624 which is a zwave thermostat and it didn’t work. I upgraded to the xl824 and it works great. The difference is the later is zwave and Wi-Fi. I believe it uses the same api as the iOS app.

through the Nexia app I can control the z-wave thermostat, but it doesn’t show up in my HA as a device. only the xl824 shows up

The following thermostats are supported: XL1050 , XL850 , XL824

The following thermostats are not supported: XL624

The XL624 uses different endpoints in the api which require a bit of live testing to get right. I started adding support for it in https://github.com/bdraco/nexia a while ago. If someone with the device wants to finish it off, I’d be happy to review a PR.

The home assistant nexia integration suddenly stopped working today. I don’t think I did anything that would break it. Anyone else having issues?

Nexia made some changes this weekend. Everything worked after a restart for me, I’ve started work to account for the changes here:

Okay. I restarted and it started working again.

Just got my XL1050 setup and running with HA. I have noticed an issue when i setup a thermostat card in lovelace. It does not show if its heat or cooling it just shows idle. There are two status one called Thermostat 1 NativeZone Zone Status and another called Thermostat 1 System Status. System status shows cooling, heating, ect… which is what the lovelace card should be showing but instead it looks like it is using the native zone status which for me has always showed Idle. Not sure if this is an issue with the lovelace cards or the nexia addon. It is this way on both the standard thermostat card and the hacs simple thermostat so i belive that its more likely the nexia information. Is there a way to switch which status point the cards are using or a way to get the add on to update the entity Thermostat 1 NativeZone Zone Status with the heating and cooling info. I hope this makes sense and if you need more info let me know.

Thanks Tim

Here is a picture of what i am talking about.


Notice how it says idle instead of cooling. In the nexia app it says cooling. and you can see the two status.
idle status

Thanks
Tim

Still have not got this to display properly and would like to know if anyone else has it working with the actual proper status.

I can confirm that I have the same issue. It would be nice to have fixed but I learned to live with it. I simply created a Glance card below the thermostat where I can see the status generated by the System Status.

i could guinea pig the 724, but maybe its already supported…im trying to add a new XR724 w/ wifi (Nexia). This isnt one of the zwave versions of 724 (like the XL624) so i would assume it should work the same as the 824? I’m not seeing the device after installing the Nexia integration so I’m wondering if this is a simple configuration issue on my end or a full on device support / API difference issue. I’d be happy to help add support but dont have the programming chops to take it on myself. I might have the hvac guy switch it to an XL824 but dont want to jump to that if not needed, especially if I’m just missing something simple. thanks all. HA noob and loving it so far.

There is a script to create a dump of the home data that could be used to build support for the 724 if it uses the new apis.

Is there still No support for direct communication with unit?

thanks @bdraco I’ll see where that leads. Just to confirm no human error on my end, the Nexia devices should show up automatically if supported in the integration correct?

If it’s supported it will just show up

I’m not sure if this is the right place to be asking… I cannot get entities to show up using the proper Nexia integration whereas the HACS-Nexia is working fine for me (except with issues of no updates to compressor speed unless I’m simultaneously logged into the Android app). @bdraco - I see your comment saying the XL624 uses different endpoints in the api… I have the XL950 (no integrated zwave, precursor to XL1050). I am not smart like you guys but willing to roll up my sleeves if someone could point me in the right direction to troubleshoot. I turned on DEBUG level logging but not seeing anything obvious…

Thanks for the latest commits and diagnostic help @bdraco, @ryannazaretian, KyleA… finally got my Xl950 working (I was getting automations but no entitites). My issue was I had created a ‘Group’ on mynexia.com which in turn created a nested json dictionary layer. After I deleted the Group on mynexia.com, it started working. Also love the dump_home_json.py – helped a lot!

@bdraco - Are you aware they are phasing out the Nexia brand later this year? I received an email from Nexia/American Standard (Trane) that they are rolling out a new mobile app call “American Standard Home” later this month. I assume this will break the current integration. Please let me know if I can help port the existing app over to the new version. I suspect Trane will have a similar change.

Let’s hope it’s just a rebranding and the api is staying the same.

We really won’t know until the new app comes out.

1 Like

FWIW - I got the same email, then went ahead and searched for American Standard Home in the iOS app store.

The app appears to be a duplicate of Nexia, right down to the “needs upgrade” warning I get on one of my temperature sensors since I refuse to pay the sub.

I’m a newbie at HA, just thought I’d sign up for the forum to add that in.