Home Assistant loosing connection to Adguard Home

apedance commented 4 years ago

Problem

I can connect the Adguard server to my Home Assistant, yet after some time, usually a few hours, the connection is lost with the below following error messages.

Connection to Linux based Adguard is lost after every restart and has to be manually removed and added again.

System information

Home Assistant Core release with the issue: Home Assistant 0.110.3
Last working Home Assistant Core release (if known): Home Assistant 0.110.3
Operating environment (Home Assistant/Supervised/Docker/venv): Docker
Integration causing this issue: Adguard Home
Link to integration documentation on our website: https://www.home-assistant.io/integrations/adguard/ https://github.com/home-assistant/core/tree/dev/homeassistant/components/adguard

Problem-relevant logs

Unable to find referenced entities switch.adguard_protection

Config entry for adguard not ready yet. Retrying in 10 seconds.
Config entry for adguard not ready yet. Retrying in 20 seconds.
Config entry for ipp not ready yet. Retrying in 20 seconds.
Config entry for ipp not ready yet. Retrying in 40 seconds.
Config entry for ipp not ready yet. Retrying in 80 seconds.

Entity id already exists - ignoring: switch.adguard_protection. Platform adguard does not generate unique IDs
Entity id already exists - ignoring: switch.adguard_filtering. Platform adguard does not generate unique IDs
Entity id already exists - ignoring: switch.adguard_parental_control. Platform adguard does not generate unique IDs
Entity id already exists - ignoring: switch.adguard_safe_browsing. Platform adguard does not generate unique IDs
Entity id already exists - ignoring: switch.adguard_safe_search. Platform adguard does not generate unique IDs

Additional information

dshokouhi commented 4 years ago

Looks like this issue is missing the issue template that gets presented when you create a new issue. Can you please edit your post and add back the template with all requested information filled in? Thanks in advance.

probot-home-assistant[bot] commented 4 years ago

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

apedance commented 4 years ago

Looks like this issue is missing the issue template that gets presented when you create a new issue. Can you please edit your post and add back the template with all requested information filled in? Thanks in advance.

Done.

probot-home-assistant[bot] commented 4 years ago

Hey there @frenck, mind taking a look at this issue as its been labeled with a integration (adguard) you are listed as a codeowner for? Thanks! _{^{(message by CodeOwnersMention)}}

frenck commented 4 years ago

Odd, as the AdGuard only allows one instance, it should not be possible to collide on ID level. Will definitely take a look.

apedance commented 4 years ago

If I get that right, as long as I do not connect to the Adguard home server web interface, I should be fine. This is exactly what I did and it is running without an issue for 2 days now.

apedance commented 4 years ago

It is happening fewer times now? Did anything change?

github-actions[bot] commented 3 years 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.

ncodee commented 3 years ago

Same issue here, any solutions?

apedance commented 3 years ago

Yes, issue is still present.

home-assistant / core