Would be possible to enhance this custom component to show the current state of the fan? I always have the fan_mode set to Auto and would like to know when the fan is actually running. I think that information is available in the response received from Honeywell site (I may be wrong).
Thanks for putting this together!
The network requirements/network topology needed to make this work doesnāt seem to be documented. This seems to have raised a number of questions.
From the comments here it looks like you need to enter an HTTPS (SSL) URL for your home assistant installation into the Honeywell developer site.
Is SSL required?
If so, does a self signed SSL cert work?
But itās not clear what will be using that HTTPS URL to connect to Home Assistant. Is it the Honeywell (cloud) servers, or is it the thermostat it self?
If it is the Honeywell (cloud) servers, I believe the requirements are:
If it is the thermostat itself that connects to Home Assistant, then external connectivity isnāt required, but an SSL certificate would still be needed if only HTTPS is supported.
Thanks to everyone who has worked on this.
Iāve hopefully fixed the fan issues reported above in the custom_component. Also resubmitted a PR to homeassistant: https://github.com/home-assistant/home-assistant/pull/31387
To the question about the fan stuff: There doesnāt appear to be a good way to display that info that is baked into the home-assistant widget. At least I donāt know how to do it. If you click the three dots at the top right, you can set the fan, and see the current status. The fan settings are pretty limited, and the API from Honeywell doesnāt give you a lot of fan status updates, so Iāve done the best I can.
Iām now on HA 0.104.3 and have had the native homekit controller component working flawlessly for a couple of weeks (no custom component).
There has been a lot of work done on the homekit component, and my thermostat (Lyric T5) seems to be supported now.
I simply reset the homekit pairing on the thermostat and used the HA front end to add it. Worked perfect first try.
For anyone not familiar, this allows for local control and sidesteps all the Honeywell api issues folks have had.
Hi shellster, I updated to your from the previous release (Dec 24) to your new changes you pushed last night and now I canāt connect to my T9. Any tips? I am asked to reconnect my Honeywell Dev account and it finishes successfully on the website. However, after Iām instructed to close my window, configurator is giving me this error: Failed to configure, please try again.
@elikorh Thanks for the feedback. Can you enable debugging in your configuration, and restart and check the log for any errors? I canāt imagine any of my changes breaking that particular piece unless I inadvertantly introduced a bug when porting the code back to a custom plugin.
Hey shellster,
Would you be in a position to try using the native homekit component (as Iād mentioned above) instead of the custom integration? Iām really curious if this is working for any other users as we wouldnāt need to make a specific Lyric component then.
I thought that was depreciated as per this thread? Honeywell Lyric thermostat with Homekit_controller(Deprecated)
theres 2 ways to integrate lyric. with homekit or with the honeywell lyric web api(included in hacs) If you donāt want to use cloud based stuff, homekit is the way to go.
That was a custom homekit controller component. At the time the official HA component didnāt support many devices. In the meantime support has gotten much better.
The official integration has been working fine for me for awhile now.
To setup go to the integrations page in the front-end and follow the steps for adding a āHomekit Accessoryā
If you had tried the deprecated homekit custom component you might have to reset the homekit pairing on your thermostat so it generates a new pairing code. This was easy to find in the settings menu on my T5.
Iāve used the homekit way before but had some minor issuesā¦maybe time to go back to that if itās gotten better.
Part of going with HA (for me) was that I was tired of the cloud and reliability issues (mostly due to Winkās problems)ā¦the less I have to rely on anyoneās cloud the better!
Sure, I can try to get that to you. Iāve been meaning to look at my logs anyways. Havenāt had time 
the custom one I did wasnāt perfect indeed 
The whole homekit thing was quite buggy at the time. But afaik the official one is 100% reliable now, so might be a good idea.
Some help neededā¦ I installed the Lyric component with HACS but when following the instructions I receive a 500 error after the authentication in the Honeywell develop site. Then I replaced the HACS code with the github repository of Shellster ā¦ Now I get a message that authentication has been succesfull and I can close the authentication window en to push the button Continue to finish the setup. But after this I get the message āFailed to configure, please try againā. So now the card is not displayed. Any tips?
Got it, itās the thread thatās depreciated and not the actual component, makes sense now.
Hey Hendry, Iām having this exact same āFailed to configureā¦ā error as well. I PMād my logs to @shellster so maybe he can chime in when he gets the time.
In the meantime, you can try taking his code from the Dec 24th commit and see how that works. It was fine for me and I might try it this weekend.
Hey guys, Iāll take a look this next weekend and report back, providing I am no longer sick as a dog. Sounds like I may have introduced a new bug.
Thanks, tried the version of 24th of Decemberā¦ Then the component is not able to setup. When switching back to the version of 4 days ago I do get the authentication process again (but also again no way to complete this)
Iām curious as to what errors youāre receiving. Can you post them? I forked the repo and reverted to the Dec 24th commit and itās working for me again. @shellster donāt get stressed over this! Get well soon.