Pi-Hole Logs at Startup

The problem

At startup of Home Assistant, I consistently get the following logs:

Logger: hole
Source: /usr/local/lib/python3.9/site-packages/hole/__init__.py:53
First occurred: 8:06:35 PM (1 occurrences)
Last logged: 8:06:35 PM

Can not load data from *hole: pihole.domain.local

Logger: homeassistant.components.pi_hole
Source: components/pi_hole/__init__.py:115
Integration: Pi-hole (documentation, issues)
First occurred: 8:06:35 PM (1 occurrences)
Last logged: 8:06:35 PM

Failed to connect: Can not load data from *hole: pihole.domain.local

Then 4 seconds later

Logger: homeassistant.config_entries
Source: config_entries.py:366
First occurred: 8:06:35 PM (2 occurrences)
Last logged: 8:06:39 PM

Config entry 'Pi-Hole' for pi_hole integration not ready yet: Can not load data from *hole: pihole.domain.local; Retrying in background

The configuration does work. Name resolution is fine (as metioned in other closed issues). Eventually everything does appear. Under Settings Info, Pi-hole takes 25.84 seconds for Setup Time. Don’t think that anything is necessarily wrong with the integration because it does eventually load, I get all my sensors, but perhaps a delay to start so that the error doesn’t come up? Especially since eventually it does work. Didn’t see a report of this, so wanted to log it. Thanks!

What version of Home Assistant Core has the issue?

core-2002.3.8

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

pi-hole

Link to integration documentation on our website

https://www.home-assistant.io/integrations/pi_hole

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[Gloomyeye]

This issue still exists in core-2022.8.6.

[github-actions[bot]]

There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.