-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Problem adjusting Honeywell Lyric Temperature #114237
Comments
Hey there @timmo001, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) lyric documentation |
Also having this problem as of this morning.
Edit: I would like to note that I am able to change the temperature in the Resideo app itself. |
I have just had this as well, tried a reinstall of the integration and at the point after configuration where it takes you to the residio website (https://api.honeywell.com/oauth2/app/login?apikey=) there is a login prompt (not sure if that was the case previously). |
Hello, |
I am having the same problem started yesterday (3/25) around 11am. Everything on the intergradation temp card works but changing the temp. Automations don't work either. Resideo app works and the Honeywell TH6320WF2003 works at the device. |
27 hours latter HA is in control again. |
For me too |
Yes, it seems like it is back again. Let's see for how long :) |
I also wanted to report that it is working again. |
It stopped working again for me. But any temperature change made in the Home Assistant environment will not have any effect. |
I switch to HomeKit to control my T6 Honeywell got ride of the Honeywell servers that never work. HomeKit directly accesses them directly.
…----- Original Message -----
From: "pvdhoek" ***@***.***>
To: "home-assistant/core" ***@***.***>
Cc: "kllerbees" ***@***.***>, "Comment" ***@***.***>
Sent: Monday, May 27, 2024 11:35:52 AM
Subject: Re: [home-assistant/core] Problem adjusting Honeywell Lyric Temperature (Issue #114237)
It stopped working again for me.
It does show current temperature and State. I can toggle between on/off and heat and these changes will show in the Lyric thermostat.
But any temperature change made in the Home Assistant environment will not have any effect.
--
Reply to this email directly or view it on GitHub:
#114237 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
Thanks @kllerbees, great tip! |
Same here. Noticed this last night. I do not use HomeKit, any other suggestions? |
Same with me, looks like this is an issue with Honeywell themselves rather than the integration. |
Where would I get the link? When setting up the 'HomeKit Device' integration, I just get a list of my WeMo and Kasa plugs. There is no option to add a link and the thermostat does not show up in the list. |
If you have T6 you go to Thermostat and go to settings go to reset go to homekit reset go to HA it will appear start the configuration go back to Thermostat will display the code petit in HA DONESent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Justin ***@***.***> Date: 5/28/24 7:52 AM (GMT-07:00) To: home-assistant/core ***@***.***> Cc: kllerbees ***@***.***>, Mention ***@***.***> Subject: Re: [home-assistant/core] Problem adjusting Honeywell Lyric
Temperature (Issue #114237)
You just need to get the link code from your lyric thermostat
Where would I get the link? When setting up the 'HomeKit Device' integration, I just get a list of my WeMo and Kasa plugs. There is no option to add a link and the thermostat does not show up in the list.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
You may need to reset the homekit code on the thermostat. I have a T6, and it is pretty much menu->settings->reset homekit |
@kllerbees & @grahamakennedy thank you! I was able to figure it out. However, there is no option in the app to reset HomeKit, but there is within the settings of the thermostat itself. So, for those with a T5, you'll want to go to: menu -> reset -> homekit -> yes -> a new code will appear Are you missing settings though within Home Assistant? I only have "Mode" now and no option to change the "Fan mode" or "Preset." |
Yes, I did mention it was the thermostat for resetting the homekit access. |
Yes, you did... I totally interpreted that as through the app for some reason. Following those steps in the app takes you to a place where you can reset WiFi though, just not HomeKit. The fan is only important for circulating the air throughout the house, which we typically do at night. I guess I could just use both integrations. HomeKit for the temperature and Honeywell for fan. Thank you again! |
Have the same exact issue. Anyone have an idea on a local API approach? |
HomeKit Device
…----- Original Message -----
From: "zonyl" ***@***.***>
To: "home-assistant/core" ***@***.***>
Cc: "kllerbees" ***@***.***>, "Mention" ***@***.***>
Sent: Tuesday, May 28, 2024 5:57:49 PM
Subject: Re: [home-assistant/core] Problem adjusting Honeywell Lyric Temperature (Issue #114237)
Have the same exact issue. Anyone have an idea on a local API approach?
--
Reply to this email directly or view it on GitHub:
#114237 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
The problem
I've noticed in the last week or 2 that I am unable to adjust the Honeywell Lyric thermostat for heating. When I check the logs, there seems to be an error that is received at that time.
What version of Home Assistant Core has the issue?
2024.3.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Honeywell Lyric
Link to integration documentation on our website
https://www.home-assistant.io/integrations/lyric
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: