Home Assistant Community Add-on: Pi-hole

I’m currently using a local DNS to resolve a local hostname within my network. Is there a way I can get the same functionality in the pi-hole addon?

1 Like

That is actually a pretty good suggestion!

The Pi-hole interface does not provide such an option (it is requested on their GitHub project, but not implemented).

I could add that feature. Could you please create an issue on our GitHub project for the Pi-hole add-on?

Thx!

:tada: Add-on: Pi-hole v0.2.0

Full Changelog

Added

  • SSL requirements check on add-on startup

Changed

  • Upgraded base image to v1.1.0

Fixed

  • Not using virtual host #6
  • Can’t remove blacklisted domains #7

Removed

  • Custom list.sh. Now using Pi-holes original version.
  • services script, which is now provided by the base image

This update is now available in your Hass.io panel.

1 Like

:tada: Add-on: Pi-hole v0.2.1

Full Changelog

Changed

  • Removal of X-Frame-Options header to avoid embedding issues with SSL #10
  • Changed forums link in README
  • Upgraded project stage from “experimental” into “development”

This update is now available in your Hass.io panel.

Hi,

I just installed this add-on. When I start it up I get the following in the log:

Pulling source lists into range… done!
:::
::: Getting raw.githubusercontent.com list… done
::: Status: Status 000
::: Download failed and no cached list available (list will not be considered)
::: Getting mirror1.malwaredomains.com list… done
::: Status: Status 000
::: Download failed and no cached list available (list will not be considered)
::: Getting sysctl.org list… done
::: Status: Status 000
::: Download failed and no cached list available (list will not be considered)
::: Getting zeustracker.abuse.ch list… done
::: Status: Status 000
::: Download failed and no cached list available (list will not be considered)
::: Getting s3.amazonaws.com list… done
::: Status: Status 000
::: Download failed and no cached list available (list will not be considered)
::: Getting s3.amazonaws.com list… done
::: Status: Status 000
::: Download failed and no cached list available (list will not be considered)
::: Getting hosts-file.net list… done
::: Status: Status 000
::: Download failed and no cached list available (list will not be considered)
:::

I can also access the admin console without any issues. What could cause it to not download the lists?

Thanks,
Kaz

Thank you for another great addon!

Finally had the opportunity to install and configure it and its working great!

1 Like

I’m sorry, cannot tell that from this log. But it seems like a connection issue with your network (DNS?)

Thank you for letting me know! :sunglasses:

I just did a fresh install of the add-on and I’m seeing the same issue. I can get to the lists if I go them directly, but pi-hole doesn’t seem to be able to download any list.

[edit] Nevermind, turns out I had a much bigger issue. My pi wasn’t able to connect to anything https. I just ended up flashing the whole thing and it’s working now.

:tada: Add-on: Pi-hole v0.3.0

Full Changelog

This release adds the ability to add custom DNS entries to the system. For example, you could point printer.local to the IP of your printer 192.168.1.34. :sunglasses:

Added

  • Support for configuring and resolving custom domains #9 #11

Changed

  • Upgrades add-on base image to v1.2.0
  • Updates add-on URLs to new community forum URL
  • Moves copy of rootfs at a later stage

This update is now available in your Hass.io panel.

2 Likes

:tada: Add-on: Pi-hole v0.4.0

This release upgrades Pi-hole to v3.2.
Introduces Long-term Statistics, An Audit Log, and More!

More information is in the Pi-hole v3.2 announcement blog

Full Changelog

Added

  • Added debug mode to Pi-hole FTL

Changed

  • Upgraded Pi-hole core to v3.2 #13
  • Upgraded Pi-hole AdminLTE to v3.2 #13
  • Upgraded Pi-hole FTL to v2.12 #13
  • Fixed typo in panel_iframe example config in the README #16

Removed

  • Removed unused detect_ftl_binary.sh script

This update is now available in your Hass.io panel.

2 Likes

This is awesome! thanks for such cool addon!!!

This setup however is creating some sort of conflict with my samba sharing. It works fine as long as only samba, or Pi-hole is enabled. If I try to run both, only pi-hole works…

Any thoughts?

Thanks in advance!

I had the same problem. admin was working on SSL but port 80. Now it works with this config:

- platform: pi_hole
  host: xxx.duckdns.org:80
  ssl: true
  verify_ssl: false

Not able to get the ad-serving domains list download from the update list

[i] Neutrino emissions detected…
[i] Pulling blocklist source list into range…
[✓] Pulling blocklist source list into range

[i] Target: raw.githubusercontent.com (hosts)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available

[i] Target: mirror1.malwaredomains.com (justdomains)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available

[i] Target: sysctl.org (hosts)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available

[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available

[i] Target: s3.amazonaws.com (simple_tracking.txt)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available

[i] Target: s3.amazonaws.com (simple_ad.txt)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available

[i] Target: hosts-file.net (ad_servers.txt)
[i] Status: Pending…
[✗] Status: Connection Refused
[✗] List download failed: no cached list available

[i] Consolidating blocklists…
[✓] Consolidating blocklists
[i] Extracting domains from blocklists…
[✓] Extracting domains from blocklists
[i] 0 domains being pulled in by gravity
[i] Removing duplicate domains…
[✓] Removing duplicate domains
[i] 0 unique domains trapped in the Event Horizon

[i] Adding 6 blocklist source domains to the whitelist…
[✓] Adding 6 blocklist source domains to the whitelist
[i] Whitelisting 0 domains…
[✓] Whitelisting 0 domains
[i] Parsing domains into hosts format…
[✓] Parsing domains into hosts format
[i] Cleaning up stray matter…
[✓] Cleaning up stray matter

[✗] dnsmasq: no process found
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

1 Like

I’m having the same problem. I think the update to 0.4.0 did it because it was previously working.

im on 0.40 and im seeing the same when i update lists as @jakes.

also im getting a ton of errors in my logs - essentially looks like my hassio install cant resolve any external DNS entries. Network devices that are using the HASS (0.60) /Pihole for DNS are ok, but it seems like “on device” DNS is borked. (myq, darksky, lutron, yr, all return similar to these:)

Log Details (ERROR)
Tue Dec 19 2017 08:56:28 GMT-0400 (Atlantic Standard Time)

Unable to connect to Dark Sky. HTTPSConnectionPool(host='api.darksky.net', port=443): Max retries exceeded with url: /forecast/8dd5ef52407677c9066c430ea218be36/44.669419,-63.816837?units=si (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x734d7950>: Failed to establish a new connection: [Errno -3] Try again',))

Do you recommend updating to HASS 0.60?

Hi,
I find out some strange behavior with active Pi-Hole DNS.

My Setup:

  • Raspberry Pi 3 with Hassio and Pi-hole addon 0.4.0
  • Setting up pi-Hole IP to my DHCP DNS Server.

Things not working so far with active pi-hole DNS on my hassio pi:

  • MariaDB addon not possible to load (recorder/history/logbook not working)
  • Node-Red addon not possible to install any modules
  • hostname resolution not working in pi-hole WEB UI

I’m not sure if its a problem with Pi-hole it self or the addon or hassio.

Edit:
I think a solution is to set an non pi-hole DNS Server to the ResinOS Network configuration file.
https://docs.resin.io/deployment/network/2.x/

@kolossboss that is the route i was going down - My PI was pulling from DHCP, but i think i need to set it static in the network config. My DHCP reservation was keeping it on the same IP.

once i flipped the DNS to my old pihole everything came back up with no issues - So i think its something with the passthrough or failover to the 2nd or upstream DNS (in mycase google)

I tested it too. If I use a separat raspberry for pi-hole, there are no problems.
Must be something todo with the pi-hole addon.

I think its time to make an issue request on github. I can to it tomorrow.