Home Assistant Community Add-on: AdGuard Home

I don’t believe there’s an option to do that on a per-device basis.

You could set a filter which just blocks every domain, but that’s a bit counter productive. You can also turn on an off certain filters inside HA (or atleast add/remove it), so if you made that total blacklist filter, you could control it via HA I think, but that seems like a rather cumbersome way of doing it honestly.

1 Like

Trying the new HA integration running Hass.io. AdGuard is discovered but when I click the configure and then submit button I get a failed to connect message.

For me I had to restart the AdGuard add-on and then connected the integration. Doing a full system reboot would have accomplished the same thing.

Thanks. Restart of AdGuard fixed it

1 Like

I have Hass.io installed in docker. Should this work on that kind of setup without tricks? I only get my internet killed when I try this.

The difference between correct (static ip/dns) and Not-correct (client of it self) is massive in performance, and the network become stable.

So remember to follow documentation, and with the SSH & terminal addon now have nmcli which make setting static ip and dns so easy :pray: (I used Hass.io on Intel NUC for inspiration for setting the ip/dns)

Thanks to @frenck for awesome work which make my life easier and better :heart::pray:

1 Like

I’ve installed the add-on. I already had static IP for my Pi on which I’m running hass.io. I am able to start the add-on and to see the Dashboard in the Web UI for AdGuard Home.

I tried putting my Pi’s IP address (192.168.1.245) into my router’s DHCP configuration as the DNS Server. But when I did that I lost all Internet access on from my home network. What am I doing wrong? Here’s my IP setup on my Pi:

nmcli> print ipv4
[‘ipv4’ setting values]
ipv4.method: manual
ipv4.dns: 8.8.8.8
ipv4.dns-search: –
ipv4.dns-options: “”
ipv4.dns-priority: 0
ipv4.addresses: 192.168.1.245/24
ipv4.gateway: 192.168.1.1
ipv4.routes: –
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.routing-rules: –
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: –
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: –
ipv4.dhcp-fqdn: –
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.dad-timeout: -1 (default)

1 Like

hey @Frenck thanks for the video on Adguard Home setup and config on Hassio. I need some direction on an issue. I had it installed on a PI3 and worked so well, but yesterday I’ve migrated my Hassio from my PI3 to VMWare ESXI / Ubuntu Server 18.04 / Docker. Installed restored the backup of my Hassio onto there, it complained about the port 53 so I’ve moved it t port 54 which is fine, but then my issue that I need help with is getting my clients/devices to talk to it again since under my “Top Clients” box on Adguard dashboard all I have now is “localhost (127.0.0.1)” and none of my rules seem to work anymore such as resolving any dns names or blocking anything using the same filters as before …
I’m guessing might be to do with the fact that it is now running inside docker ? did a bunch of research on this but I’m a little stuck, all other addons seem to work fine. Thanks in advance.

ok, problem fixed using the above post Home Assistant Community Add-on: AdGuard Home using the command on my host:
sudo systemctl disable systemd-resolved.service
followed by a reboot command
sudo reboot now
thanks @mjoshd and thanks @Silicon_Avatar

1 Like

:tada: Release v2.0.1

Full Changelog

This is a general maintenance release.

:hammer: Changes

  • :arrow_up: Upgrades add-on base image to v4.0.2
  • :arrow_up: Upgrades AdGuard to 0.97.1

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

I dont no if you solved this. But I’m running into the same problem.

Hassio is installed in Ubuntu with Docker. The problem is. Ubuntu used port 53 for the DNS server, so Adguard cant use port 53.

Thats what I have done and its working.

1 Like

I live in the Uk and my ISP is BT who restricts its customers to use their own DNS servers and this cannot be changed. Does that render this addon useless for me?

I use hassio on a pi

you could change route router to something that would let you change yoru DNS server.

You could disable DHCP on your router and replace it with AdGuard as well…

1 Like

Or just change it on a per-device setting. I’m on BT too and just override it on each device.

I’ve raised an issue on git:
https://github.com/hassio-addons/addon-adguard-home/issues/28

Has anyone else here encountered?

1 Like

I’m having a bit of trouble after installing duckdns on my hassio, the add on start but the only “client” I get is 127.0.0.1 which is wrong, obviously. Before I had Duckdns running it worked flawless, but I don’t know what the difference should be in the settings

Edit: I’m running this:
Add-on version: 2.0.1
You are running the latest version of this add-on.
System: HassOS 2.8 (armv7 / raspberrypi3)
Home Assistant version: 0.96.5
Supervisor version: 170

And are getting this alert when booting

nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
1 Like

:tada: Release v2.0.2

Full Changelog

This is a general maintenance release.

:hammer: Changes

  • :arrow_up: Upgrades add-on base image to v4.0.3

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

Frenck you Great, and your awesome masterpiece maybe makes people happy.

Always Thank you.

:tada: Release v2.1.0

Full Changelog

This is a general maintenance release, that now ships with AdGuard Home v0.98.1!

This new version comes with tons of new features, see the release note by AdGuard for more information.

https://github.com/AdguardTeam/AdGuardHome/releases/tag/v0.98.0

:hammer: Changes

  • :arrow_up: Upgrades nginx to 1.16.1-r0
  • :arrow_up: Upgrades add-on base image to v4.1.1
  • :ambulance: Fixes path handling for SSL certificates
  • :hammer: Updates HA Auth URL in NGinx LUA sccript
  • :hammer: Use Hass.io DNS as NGinx resolver
  • :hammer: Update HA Discovery with latest Bashio
  • :fire: Removes now obsolete hosts configuration
  • :arrow_up: Upgrade AdGuard Home to v0.98.1 (#32)
  • :hammer: Enable use of AdGuard Home work-dir option

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck