home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.07k stars 29.73k forks source link

Error requesting lyric_coordinator data #115509

Closed cbrngrz closed 1 month ago

cbrngrz commented 4 months ago

The problem

Honeywell Lyric (Thermostat) frequently becomes unavailable.

Since the 8th of April my integration with Honeywell Lyric has been repeatedly failing multiple times a day with the error

Error requesting lyric_coordinator data: Cannot connect to host api.honeywell.com:443 ssl:default [Try again]

appearing in the logs. After 5 to 10 minutes, the connection is established and everything starts functioning as normal. However the issue repeats every 30 to 120minutes or so.

Integration was working fine prior to the 8th with at most 1 failure per day.

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

Attempted a rollback to core-2024.3.3, but did not resolve issue.

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?

Error requesting lyric_coordinator data: Cannot connect to host api.honeywell.com:443 ssl:default [Try again]

Additional information

The issue only started to occur on the 8th. No changes in hardware were made and everything was working great prior. I attempted disabling all custom integrations but that did not resolve the issue.

No response

home-assistant[bot] commented 4 months ago

Hey there @timmo001, mind taking a look at this issue as it has been labeled with an integration (lyric) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `lyric` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign lyric` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


lyric documentation lyric source (message by IssueLinks)

timmo001 commented 4 months ago

The honeywell api appears to have issues from time to time. I would reccomend using the homekit integration for everything but schedules

cbrngrz commented 4 months ago

I see, I'm not sure if my thermostat is capable of that, but I personally don't have any apple devices so I know nothing about homekit.

For what it's worth, this issue has been occurring on ALL cloud based integrations that I have including Total Connect as well as the weather forecast.

For lyric specifically, the log is pointing to this file Source: helpers/update_coordinator.py:328

The forecast integration points to the same file, but line 347

satnitfver commented 4 months ago

Same issue after 2024.5.0

'schedules': [{'time': [{'start': '15:00:00', 'end': '17:00:00'}], 'days': ['Sunday', 'Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday']}]}}, 'stateName': 'California}] 2024-05-02 20:29:00.684 DEBUG (MainThread) [homeassistant.components.lyric] Finished fetching lyric_coordinator data in 0.380 seconds (success: False)

issue-triage-workflows[bot] commented 1 month ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.