AdGuard Home integration set-up

Third party integrations
1

Hello,

I want to integrate AdGuard Home into Home Assistant. AdGuard Home is running on a different IP address than Home Assistant.
If I want to add AdGuard Home in Integrations it asks for a host, port, user and password. The default host is 3000, but when I go to 192.168.178.221:3000 it shows me that the page is not reachable. When I just go to 192.168.178.221 it shows me the correct AdGuard page. How is this possible?
And then I want to add the AdGuard integration, but when I fill in all the details, it shows that it’s not able to make a connection.
How can I fix this?

Thanks!

2

How do you normally reach your Adguard Home instance? I have it integrated as well but you’ll need to use the correct port.
You’re saying that just going to the IP address works, this means Adguard is running on port 80 (or 443 for HTTPS).

1 Like
3

Well, I already tried with port 80, but now it magically started working :laughing:
So thanks, for having me trying it another time!

4

I am having similar issues…
I am running both Home Assistant an AdGuard Home in a Docker Conteiner. AdGuard uses it’s own Macvlan.

I can access Adguard via the Browser by putting:
http://192.168.###.###

However I cannot get the Adguard Integration to work in Home Assistant, no matter what Port I fill in.

This is what I put in the Home Assistant frontend:

image
image547Ă—649 18.1 KB

I cannot figure out the checkboxes…
The first own says “use SSL” and the second one says check SSL. To me that sounds like the same :woman_shrugging:

5

I’m having the same problem. I put in the IP of my AdGuard Home server, set it to port 80, uncheck the SSL stuff, and it doesn’t work.

6

I am also running into this issue.

Home assistant in container. Adguard Home in different container.
If I exec into the Home Assistant container I can ping/traceroute adguard over the macvlan.
image
I can also ping it over the bridge network:

image
image695Ă—61 2.67 KB

Adguard is accessible directly in the browser at that IP. Implying it is using port 80. And indeed navigating to 192.168.1.4:80 also brings up the adguard UI.

I can’t get it to connect to the Adguard server in the integration:

image
image496Ă—686 18.7 KB

I have tried with/without http:// prefix, all IPs. And all combinations of checkign and unchecking SSL.

If i don’t put a Username it at least gives an “unknown error occurred” instead of a failed to connect:

image
image485Ă—712 18.7 KB

Are there logs I can access somewhere that print when you try and add integrations?

7

Seems to be 403 forbidden error from the logs:

image
image996Ă—761 40.9 KB

Which is weird because I am able to log in using the same credentials in the browser UI.

8

Hello,
are there news on this? I am running into the same issue and have no clue, how to solve it.

thanks and best regards.

2 Likes
9

I initially had similar problems but was able to address it by using the following settings…

Server: 127.0.0.1
Port: 45158 (found in AdGuard Add-On log)
Username: (see below)
Password:
Uses SSL: unchecked
Verify SSL: unchecked

I enabled the hidden configuration option (leave_front_door_open) which allows the integration without username and password. After reading about this setting, I ended up deleting the integration, disabling leave_front_door_open, created a separate HA user, and set the integration up a second time with the HA user account I created. Works great.

Configuration:
HA Virtual Machine running Adguard 4.8.14 Add-on
Home Assistant 2023.8.4
Supervisor 2023.08.1
Operating System 10.5
Frontend 20230802.1 - latest

2 Likes
10

I manage to use port 80 and just the IP address (without http://)

2 Likes
11

I am having the same dramas with no way to resolve it yet.

12

i had the same issues as above, so it took me to install the GitHub - frenck/python-adguardhome: Asynchronous Python client for the AdGuard Home API locally to brute-test until i realized that the HA configuration process is misleading when it has placeholder port value 3000. Port 3000 is for API calls, so i was mapping it to my portainer port routing to AdGuard Home port 3000, which is wrong.

You need to specify port to point the admin portal, not api port. So in my case it’s just:

        host="192.168.1.5", # <--- IP of AdGuard behind portainer
        port=8580,  # <--- port mapped to AdGuard container's port 80
        verify_ssl=False,
        tls=False,
        username="...",
        password="...",
13

This worked for me.

I used port 80

14

In the meantime I tried Pi-hole as an alternative solution to AdGuard Home.
However, The outcome is the same: I cannot connect neither Adguard nor Pi-hole via their respective integrations.

Now this might be just coincidance, but I am starting to get suspicious. Maybe it’s due to my setup (Openmediavault on top of Raspberry Pi OS, Home Assistant (port-bound) and Adguard/Pihole (macvlan) in Docker).

Update
I got another Pi and moved Pi-hole over there and it works right away.
I will try to run the Adguard container on that as well and let you know, if it works.