Somehow this discussion flew under my radar…
I have a couple of software-only solutions that allow HA to control my Infinity thermostat, which I’ve been using for close to year.
I went a down a couple of paths in this journey:
Using Infinitude as a proxy.
I wrapped the Infinitude proxy server in a docker container, and wrote a custom climate component that used its web API. But during the development, a firmware update broke Infinitude, and there was not an active response to resolve the issue. As a result, I ended up writing my own proxy (read more below). Long story short, development eventually resumed on Infinitude, and everything seems to work again. I was already considering a cleanup of my custom component, which I could then release to the public. This thread is probably the push I need to get that done.
Using my InfinityTouch proxy
As mentioned above, when Infinitude broke, I decided to write my own custom proxy entirely in Python. This is the solution I am currently using at home, and it exposes a more robust REST API than Infinitude. It can read & write every available option on the thermostat. The only gap in functionality is that it does not support the “passthrough” mode of Infinitude, in which the proxy will sync back to the Carrier cloud, allowing you to continue using the Carrier web/app controls in addition to HomeAssistant. At this point, I don’t think I’m going to release that feature - too many quirks to work out, and I have other areas of HA that I’d like to focus my time on. But the core proxy works great - I just need to provide some basic “How to Use” instructions, and package up the corresponding custom HA component.
Anyway, just wanted to raise some awareness to other working options. I’ll try to release the missing code shortly.