-
Notifications
You must be signed in to change notification settings - Fork 49
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
Bryant Thermostat won't talk to Infinitude #163
Comments
I am also in the same situation, although on an ubuntu/docker install. I've tried various ports and both host and bridge network configurations to no avail. Mine is with a Carrier Touch thermostat, but I have to imagine the root problem is the same. |
If you haven't already done so, You should look at the firmware version of the thermostat. If you have the most recent release, that may be the root cause of your problem. See #159 for more info on how to revert to an earlier version. |
This worked, thank you so much. |
I've recently been overwhelmed by other events, but am happy to accept PRs against the README as well as edits to the wiki! Don't be shy! |
I'm having essentially the same issue as described by #129, however the solution from that issue does not apply to my situation.
My Infinitude is running on a Raspberry Pi with a Raspbian install. I followed the instructions on the wiki page that is linked in the Infinitude readme to set it up.
I can access Infinitude from other computers on my LAN, however it does not appear that my thermostat is actually communicating with Infinitude at all. The page looks like this all the time:
I've tried this on port 80 and on port 3000 (by omitting the
-l
argument entirely), neither works. I have changed the proxy address and port accordingly on my thermostat.I did have the Bryant Android app set up prior to attempting to set up Infinitude, and I'm wondering if that might be causing a problem somehow? In any case, I would appreciate any assistance that can be provided. My ultimate goal is to connect the thermostat with Home Assistant. Thank you in advance!
The text was updated successfully, but these errors were encountered: