Announcement

Collapse
No announcement yet.

Support for Carrier Infinity / Bryant Evolution / ION HVAC Smart Thermostats

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Michael McSharry
    replied
    Implementation discussion via mcsMQTT is continued at https://forums.homeseer.com/forum/hs...at-integration

    Leave a comment:


  • Michael McSharry
    replied
    Since I have Carrier unit I will be able to do most of the testing locally. At this point I have confirmed that I am able to run the Python library with the Python script I developed and can see the data delivered via MQTT into HS mcsMQTTT. The risk element was the Python script. It is now functional for at least startup login and ability to retrieve data from the Carrier server.

    Next step is the wrapper around the data to create the HS Devices and Features, a UI to let users enter their account credentials, and then trying to control the thermostat from HS which will also require some Python scripting.

    Leave a comment:


  • skhs
    replied
    Originally posted by Michael McSharry View Post
    I applied to Carrier for API access and was ignored. This confirmed what my local HVAC dealer told me about Carrier dropping the API circa COVID.

    There are two GitHub repositories. Both are Python. One is for a wrapper around the Carrier API. The other is an integration into HA that uses the Carrier API.

    The HA integration is of not much value other than as a reference. The Carrier API should be of value as it handles the authentication and access to the Carrier API. I have done Python integrations with Emporia to overcome AWS authentication difficulties and with Hubspace to support the device API.

    Since Carrier is not responsive, my next step is to try to leverage the Carrier API Python in a manner that I did with Hubspace (Home Depot) and provide a HS integration with the Carrier cloud server.

    For those that tune-out of Cloud-based solutions, they should look into Infinitude for the integration. In essence, Infinitude is a reverse-engineer of the RS-485 communications being used between the HVAC equipment and the SAM module (SAM provides the cloud communications so Carrier knows what is going on with their equipment). I tracked Infinitude in the early days of the development and at that time was good enough to support the primary user needs. I do not know the current status. It, of course, is dependent upon any firmware updates that Carrier/Bryant may elect to install in their installed equipment.
    Great summary, thank you! Look forward to your work, let me know if I can help test. I technically have the "Ion" system which is just a whitelabled version of it for brands such as Heil, Tempstar, etc. I'm assuming if you solve for one, you solve for all.

    My understanding is that Infinitude is unlikely to be a sustainable solution as firmware for at least the last year+ has rendered it ineffective and tbh, while I hate the idea of companies intentionally hobbling functionality like this via firmware updates, I also hate letting firmware bitrot and miss important fixes, feature enhancements or security fixes to keep functionality like this. So to me, I'm more than happy to take the cloud route knowing there's risk there as well (cough, MyQ).

    Let me know if I can help test.

    Leave a comment:


  • Michael McSharry
    replied
    I do not want to take the Infinitude route as that is not something I want to do with my own HVAC equipment. Others that are not as adventuresses will also not what to install equipment that may meet warranty objections from their dealer.

    I have been experimenting with the Carrier-API repository available on GitHub using the approach that I took with HomeDepot/Hubspace integration. The good news is that the obstacles that I feared with ability to get the data from the Carrier server have been overcome. I am now struggling with getting Python to deliver valid JSON syntax via MQTT. Once I overcome this then I can put a user interface to enter the account email and password into mcsMQTT and complete the integration. Overall I am happy with the progress and how I can leverage the work done for Hubspace to be applied here and in general to all Python-based integrations that are typically targeted to Home Assistant, Hubitat/SmartThings, OpenHab or Apple/Homekit.

    While not complete at this time, the obstacles that I feared have been overcome.

    Leave a comment:


  • avpman
    replied
    Originally posted by Michael McSharry View Post
    I applied to Carrier for API access and was ignored. This confirmed what my local HVAC dealer told me about Carrier dropping the API circa COVID.

    There are two GitHub repositories. Both are Python. One is for a wrapper around the Carrier API. The other is an integration into HA that uses the Carrier API.

    The HA integration is of not much value other than as a reference. The Carrier API should be of value as it handles the authentication and access to the Carrier API. I have done Python integrations with Emporia to overcome AWS authentication difficulties and with Hubspace to support the device API.

    Since Carrier is not responsive, my next step is to try to leverage the Carrier API Python in a manner that I did with Hubspace (Home Depot) and provide a HS integration with the Carrier cloud server.

    For those that tune-out of Cloud-based solutions, they should look into Infinitude for the integration. In essence, Infinitude is a reverse-engineer of the RS-485 communications being used between the HVAC equipment and the SAM module (SAM provides the cloud communications so Carrier knows what is going on with their equipment). I tracked Infinitude in the early days of the development and at that time was good enough to support the primary user needs. I do not know the current status. It, of course, is dependent upon any firmware updates that Carrier/Bryant may elect to install in their installed equipment.
    The SAM module can receive ASCII commands through its RS232 port. That's how I had my HAI Omni-II controlling my Infinitude system. When I moved I didn't re-install the Omni-II. But we have a Carrier Infinitude system in the new location and I still have the SAM.If you guys decide to go the RS232 (or other route) via the SAM, I'm set up to test.

    Leave a comment:


  • Michael McSharry
    replied
    I applied to Carrier for API access and was ignored. This confirmed what my local HVAC dealer told me about Carrier dropping the API circa COVID.

    There are two GitHub repositories. Both are Python. One is for a wrapper around the Carrier API. The other is an integration into HA that uses the Carrier API.

    The HA integration is of not much value other than as a reference. The Carrier API should be of value as it handles the authentication and access to the Carrier API. I have done Python integrations with Emporia to overcome AWS authentication difficulties and with Hubspace to support the device API.

    Since Carrier is not responsive, my next step is to try to leverage the Carrier API Python in a manner that I did with Hubspace (Home Depot) and provide a HS integration with the Carrier cloud server.

    For those that tune-out of Cloud-based solutions, they should look into Infinitude for the integration. In essence, Infinitude is a reverse-engineer of the RS-485 communications being used between the HVAC equipment and the SAM module (SAM provides the cloud communications so Carrier knows what is going on with their equipment). I tracked Infinitude in the early days of the development and at that time was good enough to support the primary user needs. I do not know the current status. It, of course, is dependent upon any firmware updates that Carrier/Bryant may elect to install in their installed equipment.

    Leave a comment:


  • SteveW
    replied
    just wish I could control my thermostat without all the duct tape
    Of course, I realize people want to locally integrate everything with their HS system, but sometimes, it just isn't worth all the time spent on trying to do it. I use the Carrier app for Android, and it works great. You can do most everything on the app that you can do on the thermostat's touchscreen.

    Leave a comment:


  • skhs
    replied
    Originally posted by alexbk66 View Post
    From original post
    Thanks, but infinitude only works on certain older firmwares and requires essentially a proxy to operate as well - it's very hacky and is not future proof. That said, maybe the link I posted above could work with the AK plugin. I may give it a try in a few weeks, but just wish I could control my thermostat without all the duct tape (not that it's anyone's fault other than Carriers/IONs). Thanks!

    Leave a comment:


  • alexbk66
    replied
    Originally posted by avpman View Post

    I have not found a Carrier/Bryant integration in HA. So I don't know how the AK plugin will help. Have I missed something? I am running this version:

    Click image for larger version  Name:	image.png Views:	0 Size:	18.6 KB ID:	1643502
    From original post
    - home assistant plugin here: https://github.com/MizterB/homeassistant-infinitude

    Leave a comment:


  • avpman
    replied
    Originally posted by alexbk66 View Post

    You may try AKHomeAssistant plugin https://forums.homeseer.com/forum/hs...nt-plugin-hass
    I have not found a Carrier/Bryant integration in HA. So I don't know how the AK plugin will help. Have I missed something? I am running this version:

    Click image for larger version

Name:	image.png
Views:	150
Size:	18.6 KB
ID:	1643502

    Leave a comment:


  • alexbk66
    replied
    Originally posted by skhs View Post
    I've seen a few (very dated) threads on this topic, but I have an ION thermostat, which is the same system as Carrier Infinity / Bryant Evolution. It looks like some folks here have tried to get the APIs working but quickly gave up. However, there's a few plugs for other HA systems that appear to have compatibility:
    - home bridge plugin here: https://github.com/grivkees/homebridge-carrier-infinity
    - home assistant plugin here: https://github.com/MizterB/homeassistant-infinitude

    Anyone willing and able to give it a go to fork it to a HomeSeer plugin? I've invested so much time and money in to HS that I have little desire to leave, but there are some key limitations in what I need to control that I'm finding some other HA hubs are easily supporting and HVAC is a key one. I can't easily adopt a different thermostat as these were brand new and are "communicating thermostats" that use a proprietary wiring schematic to the units.
    You may try AKHomeAssistant plugin https://forums.homeseer.com/forum/hs...nt-plugin-hass

    Leave a comment:


  • Michael McSharry
    replied
    I was not aware of it. If Carrier turns down my application this will be worth a look. It may even be a good reference in either case.

    Leave a comment:


  • skhs
    replied
    Michael McSharry - have you seen this? https://github.com/dahlb/ha_carrier

    Think there's potential there?

    Leave a comment:


  • skhs
    replied
    Thanks for a commendable effort!

    Leave a comment:


  • Michael McSharry
    replied
    I looked at the nodejs code for use with homebridge. It uses the earlier oAuth protocol vs. the oAuth2 protocol that is described in the API.

    I used both Postman and a small test program to replicate the initial login step at the same URL used in the js code that requires on more than the account username and password. I assumed the account to use is the one setup with Carrier when using their smartphone or web app to gain access to the thermostat. I received "Not Authorized" response from the Carrier server in both approaches.

    I then proceeded to install homebridge on a RPi using the RPi installer that included the homebridge application. I can run the application without issue, but I cannot get any homebridge plugin to install. Only the pre-packaged UI shows up. If I do a search for homebridge-carrier-infinity it just returns a blank screen.

    Click image for larger version

Name:	image.png
Views:	251
Size:	23.4 KB
ID:	1617364

    I tried to manually install homebridge-carrier-infinity plugin using npm and it seemed to execute the command for a global install, but nothing apeared in the Homebridge UI. I also tried to install it locally, but that resulted in a JavaScript heap out of memory error.

    I also made a second application for access, but this time to Bryant rather than Carrier. No response from Bryant.

    I do not know what else to try.

    Leave a comment:

Working...
X