[Feature Request] Support for AdGuardHome

[TheCableGuy99]

Hey,

Just wondering if you can add support for AdGuardHome as an alternative to Pi.Hole?

Thanks.

[leiweibau]

I can take a look at it. The Python module is already marked as “unmaintained”, which is why I would refrain from using it. That means I'll have to deal with the API directly. With my “Homelab conversion” to Proxmox, I was planning to have a look at Adguard anyway. Maybe something will come of it, but I can't make any promises. I can't find any “Demo Ouputs” of the API to see if the desired information is even output.

[TheCableGuy99]

No worries, there's no rush... I just prefer it to Pi.Hole and have 2 AdguardHome servers setup so it would be nice. So if you do implement it please can it support multiple installations of AdguardHome? Thanks :)

[leiweibau]

I'm just playing around with the API. If DHCP is not active, I currently only get limited information.

{
  "whois_info": {},
  "ip": "10.1.3.148",
  "name": "Nothing-Phone-2a.lan",
  "source": "rDNS"
}

At least I've figured out how to check whether a client has made a query in the last 5 minutes. That would be well suited for implementing presence detection.

2025-08-08T16:38:03.919691+02:00 - Nothing-Phone-2a.lan: app-measurement.com

[leiweibau]

I'm already this far with the prototyping.

[*] 14 Clients gefunden:
 - 10.1.3.105 (tasmota-351a56-6742)
...
 - 10.1.3.101 (10-1-3-101)
 - 10.1.3.100 (10.1.3.100)
 - 10.1.3.102 (10.1.3.102)
 - 10.1.3.148 (Nothing-Phone-2a.lan)

[*] Keine DNS Queries der letzten 5 Minuten erhalten

[*] Gefundene DHCP-Leases: 2
MAC: 82:3e:d4:a0:ee:9c - IP: 10.1.3.101 - Hostname: 10-1-3-101 - Expires: 2025-08-08T21:45:48+02:00
MAC: 40:f5:20:35:1a:56 - IP: 10.1.3.105 - Hostname: tasmota-351a56-6742 - Expires: 2025-08-08T21:46:35+02:00

I understand the request for support from multiple instances, and in principle it should be possible without too many problems. I could make it easy for myself and, instead of a single value for host, username, and password, create a list with the data for instance 1 in first place, the data for instance 2 in second place, and so on. However, I am afraid that this will lead to questions about supporting multiple instances for other sources as well. 🫣

[leiweibau]

adguard.py.zip

@jokob-sk
You are welcome to contribute your ideas, because in the end, I believe we would both benefit from a sensible implementation.

Regarding the issue.
In the section above, I have already demonstrated what can be obtained via the API. Here, you can see that MACs can only be obtained via DHCP leases. Hosts with a static IP that use AdGuard only leave their IP in a separate client list.
However, the client list also contains hosts that may have been inactive for some time. For this reason, I thought of filtering all hosts from the DNS queries of the last 5 minutes (max. 1000 queries).

With this list, you could then perform a kind of presence check, but only for devices that are already known or that are in the DHCP list.
The client list would only be used for name resolution, as would the DHCP lease. Within all these evaluations, you would then be forced to work with the IP instead of the MAC.

[TheCableGuy99]

Thanks for looking into this, I appreciate the details you’ve already shared of your work.

I should mention that for my setup, supporting two AdGuard Home servers is essential as I use them in a load-balanced/failover configuration for applications, devices, and operating systems that support multiple DNS resolvers. Both work hand-in-hand for the network 99% of the time.

I’m happy to test when you have something ready if you need me to, but right now I’m very busy setting up my own Proxmox server as well.

[leiweibau]

@TheCableGuy99 perhaps you could test this Python script. There is a place in the main() block where you can enter the login details for the Adguard instances. I have only entered two for now, but you could enter more.

HOSTS = [“IP1”, “IP2”]
PORTS = [“Port1”, “Port2”]
USERNAMES = [“User1”, “User2”]
PASSWORDS = [r“Password1”, r“Password2”]

adguard_multi.py.zip

[TheCableGuy99]

@TheCableGuy99 perhaps you could test this Python script. There is a place in the main() block where you can enter the login details for the Adguard instances. I have only entered two for now, but you could enter more.

HOSTS = [“IP1”, “IP2”]
PORTS = [“Port1”, “Port2”]
USERNAMES = [“User1”, “User2”]
PASSWORDS = [r“Password1”, r“Password2”]

adguard_multi.py.zip

Hey,

Could you just explain how it works?

Do I put the example code above in the pialert.conf and run this script along side of pi.alert?

Thanks.

[leiweibau]

Unpack this archive. You will find this section in the script. Edit it according to your configuration. Then save the script.

It is best to copy it to the Pi.Alert host, because Python is installed there in any case. Then run it with “python3 Path/thisScript.py”

This script is initially only a proof-of-concept and is completely independent of Pi.Alert.

For the time being, it only serves to check whether all desired data can be collected independently of my test environment. This does not mean that you should post the data here. A simple “works” is sufficient.

[TheCableGuy99]

Here you go... I ran I twice, one on port 80 and the other on port 443 when going through my the reverse proxy with the hostname so it's secure (I don't believe you can connect to API unless it's port 80 by default so not secure). Local Lan I know but why not secure it if you can?

The leases will be zero as I don't use it as a DHCP server, I use pfSense for that:

[*] Gesamtanzahl Clients: 5
 - 192.168.20.254 (192.168.20.254)
 - 192.168.20.241 (192.168.20.241)
 - 192.168.20.238 (192.168.20.238)
 - 127.0.1.1 (ns2)
 - 192.168.20.240 (192.168.20.240)

[*] Anzahl neuester Queries pro Client: 18
2025-08-11T18:30:03.109799+01:00 - 192.168.20.238 (192.168.20.238): myipv4.p1.ope***.com
2025-08-11T18:29:58.980015+01:00 - 192.168.1.56 (192.168.1.56): play.goo***.com
2025-08-11T18:29:55.762322+01:00 - 192.168.35.77 (192.168.35.77): discovery.mee***.com
2025-08-11T18:29:53.331801+01:00 - 192.168.5.38 (192.168.5.38): ftp2.ambien***.net
2025-08-11T18:30:02.184979+01:00 - 192.168.1.249 (192.168.1.249): tautulli.dav****.com
2025-08-11T18:29:49.018788+01:00 - 192.168.10.22 (192.168.10.22): logsink.devices.nes***.com
2025-08-11T18:29:24.003079+01:00 - 192.168.1.54 (192.168.1.54): mask.apple-dns.net
2025-08-11T18:29:15.570393+01:00 - 192.168.10.21 (192.168.10.21): data.mee***.com
2025-08-11T18:29:05.714710+01:00 - 192.168.10.57 (192.168.10.57): 7f74...7dd.us-east-1.prod.service.min***.a2z.com
2025-08-11T18:29:03.782571+01:00 - 192.168.1.241 (192.168.1.241): api.ambien***.net
2025-08-11T18:28:57.309025+01:00 - 192.168.10.51 (192.168.10.51): d3p8...t17.cloud***.net
2025-08-11T18:28:37.581623+01:00 - 192.168.10.246 (192.168.10.246): 3.pool.ntp.org
2025-08-11T18:28:23.455928+01:00 - 192.168.35.57 (192.168.35.57): app-analytics-serv***.com
2025-08-11T18:28:03.503927+01:00 - 192.168.20.254 (192.168.20.254): files.netg***.com
2025-08-11T18:26:39.481426+01:00 - 192.168.10.147 (192.168.10.147): d3p8...t17.cloud***.net
2025-08-11T18:25:29.798878+01:00 - 192.168.10.50 (192.168.10.50): e3913.cd.akamai***.net
2025-08-11T18:29:56.208314+01:00 - 192.168.1.248 (192.168.1.248): ui.com
2025-08-11T18:27:31.173568+01:00 - 192.168.10.20 (192.168.10.20): pubsub.pub***.com

[*] Gesamtanzahl Leases: 0

root@pialert:~# vi adguard_multi.py
root@pialert:~# python3 adguard_multi.py

[*] Gesamtanzahl Clients: 5
 - 192.168.20.254 (192.168.20.254)
 - 192.168.20.241 (192.168.20.241)
 - 192.168.20.238 (192.168.20.238)
 - 127.0.1.1 (ns2)
 - 192.168.20.240 (192.168.20.240)

[*] Anzahl neuester Queries pro Client: 21
2025-08-11T18:31:36.609038+01:00 - 192.168.20.238 (192.168.20.238): ns1.dav****.com
2025-08-11T18:31:34.380897+01:00 - 192.168.35.77 (192.168.35.77): connectivitycheck.gst***.com
2025-08-11T18:31:33.207262+01:00 - 192.168.35.10 (192.168.35.10): api-prod1.platform.fre***.tv
2025-08-11T18:31:31.962297+01:00 - 192.168.1.56 (192.168.1.56): proxmox.dav****.com
2025-08-11T18:31:11.026792+01:00 - 192.168.1.241 (192.168.1.241): wow.metoffice.gov.uk
2025-08-11T18:31:00.990208+01:00 - 192.168.35.57 (192.168.35.57): time.app***.com
2025-08-11T18:30:53.497965+01:00 - 192.168.35.63 (192.168.35.63): bag.itu***.apple.com
2025-08-11T18:30:53.320273+01:00 - 192.168.5.38 (192.168.5.38): ftp2.ambien***.net
2025-08-11T18:31:32.304365+01:00 - 192.168.1.249 (192.168.1.249): www.privat****.uk
2025-08-11T18:30:45.579939+01:00 - 192.168.10.30 (192.168.10.30): logs.netf***.com
2025-08-11T18:30:40.099325+01:00 - 192.168.1.44 (192.168.1.44): v10.vortex-win.data.micro***.com
2025-08-11T18:30:06.172061+01:00 - 192.168.10.57 (192.168.10.57): ipv4only.arpa.dav****.com
2025-08-11T18:29:49.018788+01:00 - 192.168.10.22 (192.168.10.22): logsink.devices.nes***.com
2025-08-11T18:29:24.003079+01:00 - 192.168.1.54 (192.168.1.54): mask.apple-dns.net
2025-08-11T18:29:15.570393+01:00 - 192.168.10.21 (192.168.10.21): data.mee***.com
2025-08-11T18:28:57.309025+01:00 - 192.168.10.51 (192.168.10.51): d3p8...t17.cloud***.net
2025-08-11T18:28:37.581623+01:00 - 192.168.10.246 (192.168.10.246): 3.pool.ntp.org
2025-08-11T18:28:03.503927+01:00 - 192.168.20.254 (192.168.20.254): files.netg***.com
2025-08-11T18:26:39.481426+01:00 - 192.168.10.147 (192.168.10.147): d3p8...t17.cloud***.net
2025-08-11T18:30:56.217210+01:00 - 192.168.1.248 (192.168.1.248): ui.com
2025-08-11T18:27:31.173568+01:00 - 192.168.10.20 (192.168.10.20): pubsub.pub***.com

[*] Gesamtanzahl Leases: 0```

Thanks.

[leiweibau]

Great. The AdGuard API is undemanding. I first test a connection via https, and if that doesn't work, then via http.

Then I can continue on this basis.

[TheCableGuy99]

Yeah that should cover me adding it under the hostname for the reverse proxy... thanks.

[leiweibau]

However, I would like to point out once again that, apart from DHCP leases, I can only use the information for the “online” detection of already known hosts, because I cannot obtain any MAC addresses from this information. This means that it is not possible to detect new hosts using AdGuard Import.

[TheCableGuy99]

ahh i must have missed that. I mean it's great still for people who use the DHCP server of adguardhome, it's a very popular DNS, but how accurate in time is the "online" detection? 10 minutes? 5 minutes? can it be customised?

Cheers.