Skip to content
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

Multiple Carrier Touch Thermostats #94

Closed
xeroiv opened this issue May 11, 2020 · 6 comments
Closed

Multiple Carrier Touch Thermostats #94

xeroiv opened this issue May 11, 2020 · 6 comments

Comments

@xeroiv
Copy link

xeroiv commented May 11, 2020

Multiple carrier touch thermostats pointing at the same Infinitude instance do not seem to produce desirable results. Is there a setup step that I am missing by following the raspberry pi setup on the wiki?

@nebulous
Copy link
Owner

Infinitude mimics the Carrier API which only supports single-thermostat calls. You can run multiple instances of Infinitude on different ports, however. Kludgey, but the whole mess is kludgey. 😐

@xeroiv
Copy link
Author

xeroiv commented May 11, 2020

I setup two services Infinitude and Inifitude2. The only thing that differed between the two was the port number. However the data on the dashboard is only for the first thermostat. There something else in the config that I am missing or should I just run it as a separate container from the first?

@7ooL
Copy link

7ooL commented May 11, 2020

I run two instance in a single slim vm. I simply copied the cloned git repository and have it configured for different ports. I think I made two services. There are two web instances running. I have written a python api that I use to change the configurations if both web services.

@7ooL
Copy link

7ooL commented May 11, 2020

Oh on the two thermostats I configured each to point to one of my running instances. Everything is working as one would.

@nebulous
Copy link
Owner

You'll have to also ensure that they have different storage folders. Either via brute force, having two separate copies of Infinitude each with its own state folder, or by specifying a different root_dirin the config

@xeroiv
Copy link
Author

xeroiv commented May 11, 2020

Ahh... that was the key. I just copied the infinitude folder and pointed the new service at the second folder. Works like a charm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants