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

MyTotalConnectComfort.com Compatibility #5771

Merged
merged 2 commits into from
Jul 13, 2018
Merged

Conversation

arretx
Copy link
Contributor

@arretx arretx commented Jul 12, 2018

Clarification for those who are looking to control other Honeywell WIFI Thermostats.

Description:
I was only able to get my Honeywell Thermostat to work by controlling it through IFTTT with a webhook. The MyTotalConnectComfort.com site is not the same site that the Honeywell component uses.

Pull request in home-assistant (if applicable): home-assistant/home-assistant#

Checklist:

  • Branch: Fixes, changes and adjustments should be created against current. New documentation for platforms/components and features should go to next.
  • The documentation follow the standards.

Clarification for those who are looking to control other Honeywell WIFI Thermostats.
@ghost ghost added the to-do label Jul 12, 2018
@frenck frenck added enhancement ready-for-review This PR needs to be reviewed current This PR goes into the current branch and removed to-do labels Jul 12, 2018
@ghost ghost assigned frenck Jul 13, 2018
@frenck
Copy link
Member

frenck commented Jul 13, 2018

Thank you, @arretx!

✅ Approved. Can be merged as soon as the build passes.

@frenck frenck merged commit 647c913 into home-assistant:current Jul 13, 2018
@ghost ghost removed the ready-for-review This PR needs to be reviewed label Jul 13, 2018
@dshokouhi
Copy link
Member

dshokouhi commented Jul 13, 2018

@arretx and @frenck I don't know if this is entirely true I was able to control my Honeywell Wifi RTH8580WF model which is definitely on the totalconnectcomfort site. I recently switching to zwave to avoid the API rate limits discussed in the docs. This may have something to do with the region defined based on my experience.

Edit: maybe we should list the actual models supported?

@frenck
Copy link
Member

frenck commented Jul 13, 2018

@dshokouhi Maybe create a separate issue for this, since this PR has been handled.

osirisinferi added a commit to osirisinferi/home-assistant.io that referenced this pull request Nov 24, 2018
The `honeywell.py` code uses either EvohomeClient *or* somecomfort
client code to connect to Honeywell, depending on the region (`eu`
or `us` respectively). The somecomfort client exclusively uses
mytotalconnectcomfort.com as API. Therefore, this warning seems a
little bit premature if you'd ask me.
frenck pushed a commit that referenced this pull request Dec 25, 2018
The `honeywell.py` code uses either EvohomeClient *or* somecomfort
client code to connect to Honeywell, depending on the region (`eu`
or `us` respectively). The somecomfort client exclusively uses
mytotalconnectcomfort.com as API. Therefore, this warning seems a
little bit premature if you'd ask me.
alengwenus pushed a commit to alengwenus/home-assistant.io that referenced this pull request Feb 24, 2019
home-assistant#7619)

The `honeywell.py` code uses either EvohomeClient *or* somecomfort
client code to connect to Honeywell, depending on the region (`eu`
or `us` respectively). The somecomfort client exclusively uses
mytotalconnectcomfort.com as API. Therefore, this warning seems a
little bit premature if you'd ask me.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
current This PR goes into the current branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants