-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Carrier Cor? TP-WEM01 #25
Comments
Hello @thatvirtualboy, I think if the plugin managed to run all the way to this error message, there's a decent chance that you might get it working, but as usual you're on your own there. Good place where to start hacking is the thermostat model check in Have fun! |
Thanks for the tip! Will play around |
I changed line 231 to read $ homebridge [7/18/2018, 4:25:07 PM] Homebridge is running on port 51826. |
In further testing, something in the HB config for this plugin is causing Homekit to not connect to HB. I removed the documented data from config.json (so it was as before with just my garage door data), cleared accessories and persist folder, and HB was able to be added to Homekit again. |
Ok I've narrowed it down some. As soon as I add the App to my Cor's App page (by authorizing it with the code given when starting HB) it fails, and HB stops responding. |
I believe it has something to do with the sensors. Since all I have is the thermostat, it causes HB to fail, and/or cause Homekit to not want to connect to HB.. like it fails once it sees it has devices to configure (sensors) that it can't. I've set all the exclusions in config.json to true, except for thermostat temp but same behavior. |
If I add homebridge before authorizing the app at the Cor's webpage, HB gets added, but says |
Well that's my journey so far. We're so close! If I can provide any logs or information to help troubleshoot, please let me know! @vojtamolda |
It looks like a fun project and I'd love to take a look, @thatvirtualboy, but I'm not sure when I'll be able to find the time to do it, so I can't promise anything. |
That you'd find this comical.. I opened an unrelated support case with Carrier regarding the Cor and the support tech's email and sig was plastered with "ecobee Support" |
I realize this is an old "issue", but I've just started experimenting with HomeBridge and have a Carrier TP-WEM01 just like the one discussed in this thread. I may have gotten further than @thatvirtualboy. I've attached a debug log snippet below that shows the activity when a refresh is requested once every 30 seconds: I have this configured with the default config.json platform configuration, with all 'exclude_*' properties set to false. The net result is I've got a Temperature Sensor showing up that seems to be reading the correct temperature, but I don't have a Thermostat with the ability to change the usual thermostat related properties. Seems like we are really close! Is there anything anybody can suggest to get this stubborn device working? |
From what I've read, the Carrier Cor (corSmart) is essentially a rebranded Ecobee. I was able to get this plugin installed on Homebridge, successfully add the authorization code in my "Apps" on the Cor login page (everything is basically the same as ecobee).. but when launching homebridge, I get
Not supported thermostat | My home (corSmart
I don't have sensors, just trying to get the Cor setup with homebridge. It's the TP-WEM01 Model which doesn't have native Homekit compatibility. The TP-WEM01-A (which came out years later) is what has native compatibility.
Is this something we can tweak to make work, or am I barking up the wrong tree?
The text was updated successfully, but these errors were encountered: