Pi-hole Integration Issue

Configuration
1

Pi-hole integration is not working for me at all. I have a Pi-hole at a fixed IP, no problems with it running. When I try and add the Pi-hole to Home Assistant. It looks like it worked, without even prompting for my password, but all entities are unresponsive (Unknown). I have tried this with a newly spun up pi-hole on a different devices and I see the same thing. I am running home assistant OS using the community script for a proxmox install. Any ideas what I can do to make sure I get prompted for a password and therefore allow me to authorise the connection. At some point in the past, I had Pi-hole connected, but I changed the pihole instance so tried to reconfigure a new connection from home assistant.

2

Pi-hole version 6 and later uses a new API that is currently not supported by Home Assistantā€™s built in integration.

There is an integration in HACS that works with the newer Pi-hole API.

Thereā€™s also notes in the current beta that the built in integration will gain support for the new API in the 2025.8 release of Home Assistant.

1 Like
3

As said above if using HACS Pi-hole V6 Integration for Home Assistant works quite well with Pi-hole v.6x.

Completing the above with Pi-hole Card gives you a nice dashboard card for managing and monitoring your Pi-hole.

1 Like
4

I think that was just updatedā€¦

5

The integration is working vor v6 starting with HA Core 2025.8. But as with the old v5 api, changes on the Pi-Hole side are not updated fast enough in Home Assistant:

When I disable/enable Pi-Hole from outside HA, it often takes minutes (!) for the change to get reflected in HA.

For this as a workaround in the past I had this CL sensor:

command_line:
  - sensor:
      name: "Pi-Hole Status"
      unique_id: xxx
      scan_interval: 10
      command: curl -X GET 'http://xxx.xxx.xxx.xxx/admin/api.php?status&auth=API-KEY'
      value_template: >
        {{ value_json.status }}

Now with v6 API and the need for a session ID in combination with running that CL sensor every 10 seconds this creates a lot new session ids, reaching Pi-Hole`s ā€œmax_sessionsā€ limit (default: 16).

I tried many many MANY ways to continue using this workaround (CL sensor) with the new v6 API, but it does not work.

So the core question is:

Why does it take so long for HA to discover changes? Is the polling that slowly? Really, it must be something like 4 to 5 minutes!

(edit: it is 5 minutes. hard coded default polling interval. fine for statistics, bad for switch status.)