HA Integration Pi-Hole Timeout at startup

[rocket4321]

Some users (myself included) are seeing the following error in the HA Log at startup:

Can not load data from *hole: xxxxxxxxxxxxx:80

Within the 'hole' package, the definition of 'async def get_data(self)' includes a hard-code timeout value of 5 seconds, which cannot be overridden from the pi_hole component in HA.

My preference would be to allow the HA pi_hole component to set/override this timeout value, especially since at startup, it may need to be adjusted due to increased resource demands or user hardware limitations.

It should be clarified that this issue doesn't appear to impact hole component usage, but rather just until the following data update (typically 5 min later), so very little impact is caused by this issue for most people.

Personally, I did run into an situation that caused this timeout to not allow a new pi_hole integration to be added to a running HA instance, when trying to add via the older yaml config entry method. Eventually, I had to install via the user interface's config entry method. But, no other reports of this situation have been reported, AFAIK.

I'm willing to work on the PR, if code owner gives thumbs up.

[rocket4321]

Would it be helpful if I create a PR for code review?

[lindsaymarkward]

Thank you for starting this @rocket4321 . I would like the error to go away, so I hope this can be done!

[Coolie1101]

Has this ever been resolved?, I have been following all the threads on this issue, still have the log entry.

[viktak]

Still happening on 2022.4.6

[rjbudke]

Still happening on 2022.6.1

[ryt51V]

I have experienced a related issue in HA 2025.8.2 caused by python-hole's hardcoded 5 second timeout.

I have three Pi-hole v6 instances running for redundancy. I can add two of them to Home Assistant just fine, but cannot add one that is running on a Raspberry Pi 1B. The v6 API simply does not respond quickly enough before the 5 second timeout.

As far as I can tell, the Pi-hole project's only system requirements other than disk space are 512MB of RAM. This logically includes all Raspberry Pi "B" models (except for the super early 1Bs with 256MB of RAM).

Indeed, Pi-hole itself still runs fairly well on a 1B. DNS resolution is speedy enough. The web interface is perfectly usable over HTTP. It just seems to be the API that responds a bit slowly.

I agree with @rocket4321 that the timeout should be configurable rather than hardcoded. But I also think that python-hole's default timeout should be permissive enough to work with older hardware still logically supported by the Pi-hole project, so that it's accessible to as many people as possible.

I've raised pull request #34 to address both of these - adds a timeout variable to the class, and sets the default timeout to 15s.

I've only done this for v6, as I don't run any Pi-hole v5 instances to test with. But it should be fairly trivial to replicate for that if desired.

[nicjansma]

Seeing the same issue with my RPi 1B at home as well.

Correct password requests to /api/auth usually return in ~3 seconds.

Incorrect password requests to /api/auth (including the hard-coded "wrong_password" string used by HA to determine API level) take 5+ seconds.

Posted my details here: home-assistant/core#150151 (comment)

But agreed that making the timeout configurable (or 15+ seconds) is great, it's solved the issue for me

Thanks @ryt51V for #34