We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Honeywell Total Connect Comfort is causing my HA to lock up and have to boot in safe mode. Then the Honeywell Total Connect Comfort will not load.
I would expect it to boot normally and show the thermostats config_entry-honeywell-e92b500e9f540283ea828d922a7d6b78.json
1.After it locks up, Unplug the HA 2.It boots in safemode 3. reload all yaml again. Still not working ...
2024.12.5
2024.12.2 or 2024.12.3
Chrome
Win 11
No response
The text was updated successfully, but these errors were encountered:
This doesn't sound like anything to do with the frontend. If your server is crashing, that would need to be a core issue.
Sorry, something went wrong.
No branches or pull requests
Checklist
Describe the issue you are experiencing
Honeywell Total Connect Comfort is causing my HA to lock up and have to boot in safe mode. Then the Honeywell Total Connect Comfort will not load.
Describe the behavior you expected
I would expect it to boot normally and show the thermostats
config_entry-honeywell-e92b500e9f540283ea828d922a7d6b78.json
Steps to reproduce the issue
1.After it locks up, Unplug the HA
2.It boots in safemode
3. reload all yaml again. Still not working
...
What version of Home Assistant Core has the issue?
2024.12.5
What was the last working version of Home Assistant Core?
2024.12.2 or 2024.12.3
In which browser are you experiencing the issue with?
Chrome
Which operating system are you using to run this browser?
Win 11
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: