Log is full of FYTA coordinator request timeouts

[mayrbenjamin92]

The problem

I am using the FYTA plant-sensor integration and my logs are spammed with the following:

2024-08-26 14:37:55.953 ERROR (MainThread) [homeassistant.components.fyta.coordinator] Error fetching FYTA Coordinator data: Timeout occurred while connecting to Fyta-server

There is no single other error in my logs besides the above. I have already re-authenticated FYTA, removed + re-added the integration - no solution so far.

What version of Home Assistant Core has the issue?

2024.8.3

What was the last working version of Home Assistant Core?

none - older versions also have the issue for me

What type of installation are you running?

Home Assistant OS

Integration causing the issue

FYTA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fyta/

Diagnostics information

FYTA integration is running into constant timeout which leads to "entities not available".

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-08-26 15:44:22.210 ERROR (MainThread) [homeassistant.components.fyta.coordinator] Error fetching FYTA Coordinator data: Timeout occurred while connecting to Fyta-server
2024-08-26 15:46:32.422 ERROR (MainThread) [homeassistant.components.fyta.coordinator] Error fetching FYTA Coordinator data: Timeout occurred while connecting to Fyta-server
2024-08-26 15:51:41.953 ERROR (MainThread) [homeassistant.components.fyta.coordinator] Error fetching FYTA Coordinator data: Timeout occurred while connecting to Fyta-server
2024-08-26 15:56:01.953 ERROR (MainThread) [homeassistant.components.fyta.coordinator] Error fetching FYTA Coordinator data: Timeout occurred while connecting to Fyta-server

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of fyta 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 fyta 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)}}

---

fyta documentation fyta source _{^{(message by IssueLinks)}}

[joostlek]

Please don't do anything with the previous comment. Github is struggling with a bot attack

[vonBrizien]

Same here. I think it was working properly before 2024.8.

[dontinelli]

I have the same issue. Interestingly it seems that sometimes the server still seems reachable, leading to the sensors switching between available and unavailable. According to FYTA there was no change on their servers. I will therefore try if increasing the timeout from 10s to 15s or 20s will resolve the issue.

Interestingly also at least one other HA components seem to be affected (https://github.com/home-assistant/core/pull/124597). In my log I also have some entries regarding timeout error of slide (local api) and RESTful. As they are not that often, I'm not sure if this is related or a coincidence.

[BurningSheep1]

I got the same problem with fyta since the update to 2024.8.