¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Crestron
  2. Topics

TRANE XL1050 WiFi Thermostats

 

Hi All,
I'm working on a project with (3) Trane XL1050 WiFi TStats, attempting to use the 'TraneClimateLIB v1.0 Comm IP' Crestron module.
Has any one successfully done this (or alternative method)?
I have set the Tstats to reserved DHCP addresses via their Wifi interface matching this in their respective modules, and tried pairing but No Talkie...
The module help does not indicate any 'Vendor setup' other than the obvious IP addressing and the default port.
Of course we're trying to get a tech support number for Trane, but even if we do, I'm afraid I'll hear crickets from the staff on this subject.

Anyone have any experience with this??
TIA!
 
Edited

I believe that module has been pulled from the Crestron site, cause the current firmware has broken the SSL communication.
 

Thanks Jeff for the response - I have confirmed with TB regarding this (another hour wasted on the phone)

Such a Digital Age bummer! I love when I go to finish a project and find that I can't finish the project...:(
I think I have a temporary work-around (one that of course with cost me more $$$) as the developer has indicated that they are working with TRANE to resolve the AUTH issue that apparently was caused by newer processor FW...
I'm hopeful that they will have a fix soon...
The recommended *fix* is to put another 3-series proc in the site with 1.503 FW running the TRANE modules and EISC the signals to the main processor...Arrggghh...

What really frosts me is how we all seem to get blind-sided with this stuff. Did I miss the memo? or should I finally consider it normal to do all the work, trouble-shoot and then find out thru the 'Grape-Vine' that this is the case...

I will make it a point to update here, if/when I get a resolution...
 

Are you able to share the module with me? I've got a project that I need to integrate the Trane 1050s with.
 

Hi Tim,
Reach out to me directly to discuss...

chris at eicustom dot com
 

Just thought I'd update this thread, though not with any good news...
I have been communicating with Control Concepts, the CSP that built the module that worked fine until Crestron/Trane screwed things up. They have been working consistently to resolve this, but still have not had success.
Not sure that I understand how this can not be resolved or at least determined to be a lost cause...

I will say that Victoria at CC has been fantastic with communications and updates...

That said it looks like the only solution in the foreseeable future is to use an RMC3 with v1.503 - so lame!...
 

Thanks for the update, Chris!

I have a client that's been waiting over a year for this to be resolved, and just asked me about it (again) yesterday :-)

--- On Friday, January 7, 2022 at 1:17 PM, Chris Kangis wrote:

Just thought I'd update this thread, though not with any good news...

I have been communicating with Control Concepts, the CSP that built the module
that worked fine until Crestron/Trane screwed things up. They have been working
consistently to resolve this, but still have not had success.
Not sure that I understand how this can not be resolved or at least determined
to be a lost cause...

I will say that Victoria at CC has been fantastic with communications and
updates...

That said it looks like the only solution in the foreseeable future is to use
an RMC3 with v1.503 - so lame!...
 

To add to this, when True Blue was helping us with this issue last year, they found that although the 1.503 firmware did work, they could only get it to work with a single thermostat. It wouldn't work with multiple thermostats/modules in the same program, or even in different program slots.

I guess a separate RMC3 could be used for each thermostat... :-)

--- On Friday, January 7, 2022 at 1:17 PM, Chris Kangis wrote:

Just thought I'd update this thread, though not with any good news...

I have been communicating with Control Concepts, the CSP that built the module
that worked fine until Crestron/Trane screwed things up. They have been working
consistently to resolve this, but still have not had success.
Not sure that I understand how this can not be resolved or at least determined
to be a lost cause...

I will say that Victoria at CC has been fantastic with communications and
updates...

That said it looks like the only solution in the foreseeable future is to use
an RMC3 with v1.503 - so lame!...
 

UGGHH!! thanks for that update, Tony!? Once again, you've saved me some time...

FTR, I'm going to suggest that my client buys a separate house for each thermostat...that makes sense, right???


"What a World, What a World...Aggghhhhhhh..." - The wicked witch of the west.
 

Yeah, so far their are two issues. Crestron has pruned cypher suites that are compromised and weak. The thermostat needs to have get theirs updated to get a match. Also SSL uses client side certs, and this broken on the 3-series. Although I am told there is unreleased firmware that fixes this.

Jeff
 

I've run into the same results on this... Have a customer that has 2 of these thermostats and I have a DIN-AP3 Running old firmware and can get one of them working but not both...
I get no where with Crestron or Trane

Has anyone heard anything new on this front?
 

I believe that we're finally in the clear, with a short-term caveat - I'll verify that I can post what I know on monday...
 

Would love an update!
 

Crestron has just released new 3-series firmware that resolves the TLS handshaking problem. ?The version is 1.8001.0133. I?have been testing with the last known released module/demo program and it is working well. ?I also created a test program with two thermostats to test that each would connect and could be controlled independently - that is also working as expected.
 

That's great news, thanks!

What is the "last known released" version of the module? The one I have is "TraneClimateLIB v1.0 Comm IP.umc", from the "TraneClimate v1.0 Demo IP CP3" example program.

--- On Tuesday, March 1, 2022 at 5:30 PM, ajhan81 wrote:

Crestron has just released new 3-series firmware that resolves the TLS
handshaking problem. The version is 1.8001.0133. I have been testing with the
last known released module/demo program and it is working well. I also created
a test program with two thermostats to test that each would connect and could
be controlled independently - that is also working as expected.
 

The last known release was the one available from the application market before it was pulled. ?There has only been one release so far. ?You should the correct module!?
 

One important caveat!! There is a console command SUPPORTRSAAES128ciph that must be enabled for the secure TLS communication to work. ?This console command enables one of the ciphers Crestron removed from the firmware, but is required by the Trane thermostat. ?Type "supportrsaaes128 on" in the Crestron console and reboot your processor. ?You can check that it's enabled by typing "supportrsaaes128". ?Make sure you enable this before attempting to connect the module, otherwise the module will not connect.
 

This is good news!!
 

The app market has the updated interface now...
 
Edited

Just wanted to give this one a quick bump as we had to deal with these this week.? We ran into a bug during install on the module v1.1 which displayed this error sporadically when changing setpoints:

[ The setpoint requested violate the deadband set by the user. ]

Contacted the module creators (ControlConcepts) and Jen was quick to send us the hotfix clz file to correct it and all appears to working properly now.? She mentioned they will be updating the app market module, but until that point, I would reach out to them to get the hotfix if you run into this issue.? Thanks again Jen!

1 - 20 of 21