API problems after upgrade to 2024.03

[krzysztofnowak1972]

The problem

After the update, there are problems with the continuity of API data from external providers. The data is fragmented, with an average break of 4-5 minutes.

What version of Home Assistant Core has the issue?

2024.03

What was the last working version of Home Assistant Core?

2024.2.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

myuplink

Link to integration documentation on our website

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

Diagnostics information

home-assistant_myuplink_2024-03-19T18-55-24.939Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

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

---

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

[astrandb]

There are multiple communications errors in the attached log. The errors come from different integrations, e.g. home-connect, myuplink, hydrawise. I suggest that you disable the integrations and enable them one by one to see which one causes the trouble. I would also appreciate if you would upload a diagnostic file from myuplink device page and drag it into this issue.

[krzysztofnowak1972]

Now there are two topics, one here and a parallel one in myuplink on github

files below - debug and diagnostic

home-assistant_myuplink_2024-03-19T19-37-42.795Z.log config_entry-myuplink-06853b59d28b1c7ab6209902c9fad735.json

This all stopped working with core 2024.3

[krzysztofnowak1972]

Still not working properly. Everything that may interfere is turned off

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

Log and disgnostic - below - any sugestions ?

When come back to supervisor 2024.2 - all works fine

All errors are with port 443 SSL - what is wrong with this ?

home-assistant_myuplink_2024-03-24T19-27-33.654Z.log config_entry-myuplink-654d0bd62e1d240b6aaa279cf5003785.json

Maybe in the previous version, which worked correctly, it also interrupted, but HA mapped the last parameter, did not interrupt the chart and did not show the unavailability of the entity. Now, if there is no data from the API, there is a lack of continuity and the entities are unavailable.

[enoch85]

Have you tried the latest version?

I'm in 2024.4.3 an I don't see the same behavior (well little, but not that much):

[krzysztofnowak1972]

I found the problem. For me, the problem was with AdGuard. I had to remove it completely, then the problem disappeared. When I turned off the ADGuard service, the problem was still there. Total removal helped ;-)

[enoch85]

I found the problem. For me, the problem was with AdGuard. I had to remove it completely, then the problem disappeared. When I turned off the ADGuard service, the problem was still there. Total removal helped ;-)

Hehe, sommtimes antivirus/adblocker is the actual virus itself. 😅

[gsolem]

I don't have the AdGuard addon, so there must be something else also causing this issue. I made an automation to re-connect every hour if the API connection has dropped, and that happens every single hour.

[issue-triage-workflows[bot]]

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.