Sorry I wasn’t clear. It wasn’t the integration, it was me working on my network that was causing the loss of connection. I haven’t had any issues now that I have finished restarting my server and software based firewall.
The Homekit controller integration is by far the most stable connection that i have had to my lyric t5 stats in years! I used Brams method and many modified versions over the years and none of them compare in stability or features on my system.
Hi. Is this still working for you? If so, would you mind sharing how you got it going? I’m trying to install the homekit controller integration, but it is failing and haven’t been able to figure out why
So I loaded up an old snapshot the other the day that still had the hacs lyric component installed. It seems all the api call errors are gone. Maybe the problems were on the home assistant side? I’m running a t9 everything seems to be working- set points, mode, etc just not the remote sensors.
That’s great news. What a long journey. Judging by the github threads it looks like a sizable amount of work went into getting something that the developers were willing to merge that. Hopefully the result is something that should be robust.
Unfortunately, it looks like fan control might not be there yet. Someone else is working on trying to get that implemented.
Personally I can’t use the new the Lyric integration with my T9 thermostat (yet). It connects and sets up just fine, and all the sensor data seems to function perfectly as well… and that appears to be it. I cannot make any changes to the system via HA. On the Lovelace card, changing the temperature doesn’t change anything on the actual thermostat, and the mode setting buttons on the card seem frozen (i.e. clicking them gets no reaction). Reloaded to the previous HA version backup which had the HACS Lyric addon, and everything works and updates to the thermostats just fine. Need to check later if this issue was added on the Core github page… if so I hope it gets figured out quickly, as the additional sensor info (outside temp, humidity, etc.) was nice to have!
Yeah it definitely isn’t working right, T9. If I click on the three dots on the thermostat card and bring up the additional dialog page, I can then change the temperature. It helps when you manually choose hold until.
I don’t have it in an automatons yet but I’d suspect that if you include setting heat until in the actions it might work.
I have a few Node Red automations I use in conjunction with some Wyze contact sensors that will turn off and then back on the AC if someone leaves an exterior door open for an extended period of time, but I haven’t tested them yet. I’ll try everything again this weekend, as I immediately went back to my v2021.2.3 snapshot when I couldn’t get it working properly. There doesn’t appear to be an open issue posted for this exact issue yet on the HA Core github, so I’ll probably create that tomorrow as well if someone doesn’t beat me to it.
I have a little different use case scenario than most. This is in an apartment building so I have to maintain temp through out, regardless of occupancy. I also run steam vs radiant hot water. This is also the source for domestic hot water.
So what I have set up is 5 dallas temp that monitor steam header out, steam return, hot water supply, cold supply and mixed domestic hot water. I have 2 k type thermocouplings, one in the fire box and one in the flue.
The k types are considerably more than dallas $2 vs $35 but they have a much higher operating temp. They are also quicker to respond. I’ve found that dallas lag about minute behind the k type. The dallas will miss peaks because of this albeit only a few degrees.
I have 2 ct clamps that monitor power to the burner and the pressuretrol, it turns the boiler on/off depending on steam pressure levels. This is really the only thing I have identified to possibly optimize efficiency. It’s a 50+ yo boiler so I didn’t expect much.
Basically I will override the T9 once it kicks on. I will use a relay to then close the thermostat call wire that will not open until the pressuretrol reaches it’s cut out. At cut out most of the radiators in the building are full. I figure it would be more efficient to over shoot my set point since the boiler is most efficient when it’s hot. Those little spikes are what I want to eliminate.
That said everything has to be specific to your equipment. Circulated hot water can benefit from a PID controller, esphome and there is an addon in hacs for software PID. How much depends on the system and if it can be modulated.
Did you update the Developer site app URL? For the new integration, the URL changed from “/api/lyric/authenticate” used in the HACS version, to “/auth/external/callback” for example:
http://192.168.1.123:8123/auth/external/callback
Did you restart HA after updating the configuration.yaml? I know this one is kind of duh, but it’s amazing how often people accidently forget to do that one.
Hi @Technowizard thanks for the reply. I just tested it again. (Its been a few days) and its now working. Not sure if it was a Honeywell API issue or I didnt wait long enough after restart to test.
Has anyone gotten the new Honeywell Lyric integration (as of 2021.3) to work with a Lyric Round thermostat? I set it up, and on the surface it appears to work, I can see the thermostat setpoint, outdoor temp, and have a climate.thermostat entity. However, I cannot change any settings on the thermostat from Home Assistant. Changing, temp or mode throws an error.
Had the same issue with my T9s. Try deleting and recreating the app on the Honeywell developer site. That fixed it for me, as it turns out the site is a tad glitchy in their creation sometimes. Just remember to put your new credentials in your configuration.yaml afterwards.