Browse by type
<img src="https://brands.home-assistant.io/_/pi_hole_v6/logo.png">
Original component : Pi-hole
The Pi-hole integration allows you to retrieve statistics and interact with a Pi-hole system.
Due to major changes in the Pi-hole API, the native integration with Home Assistant was no longer functional for several months in 2025, until August 2025.
The 'Pi-hole V6 Integration' added compatibility with the new API in Home Assistant. This integration aimed to restore compatibility and provide Pi-hole management directly from Home Assistant.
[!NOTE] Today, this integration remains active and not only restores full functionality but also offers additional and complementary features to the native integration. Users can now enjoy enhanced capabilities and a seamless experience when managing Pi-hole through Home Assistant.
The following sensors are currently implemented :
<img src="https://raw.githubusercontent.com/bastgau/ha-pi-hole-v6/main/img/entities-overview.png" width="800">
A complete list with explanations is available on this page.
The integration is currently translated in few langages :
After installing this integration, you can enhance your Home Assistant setup with the Pi-hole Card.
This lovelace card offers a comprehensive and user-friendly dashboard designed specifically for managing and monitoring your Pi-hole DNS ad blocker. It provides real-time statistics and intuitive controls, all presented in a visually appealing interface that aligns with Pi-hole's design aesthetics.
The card is developed by @warmfire540.
The installation instructions are available on the repository: homeassistant-extras / pi-hole-card.
<img src="https://raw.githubusercontent.com/bastgau/ha-pi-hole-v6/main/img/pihole-card.png" width="300">
It is possible to show the info and debug logs for the Pi-hole V6 integration, to do this you need to enable logging in the configuration.yaml, example below:
logger:
default: warning
logs:
# Log for Pi-hole V6 integation
custom_components.pi_hole_v6: debug
Logs do not remove sensitive information so careful what you share, check what you are about to share and blank identifying information.
By default, the data is updated every 5 minutes. You can configure a different frequency as explained on the following page.
Some additional information is available if you encounter any problems while adding a new service on this page.
A quick example to integrate controls in a dashboard is available on this page.
A useful tip to exclude unnecessary sensors from the Recorder is available on this page.
I listed the implemented features in the HA Pi-hole V6 Integration and the Core Integration.
| Compatibility | Pi-hole V6 Integration | Core Integration |
|---|---|---|
| Pi-hole v5 (Latest release: December 29, 2024) | ❌ | ✅ |
| Pi-hole v6 (current version) | ✅ | ✅ |
| Category | Entity Type | Pi-hole V6 Integration | Core Integration |
|---|---|---|---|
| Binary Sensor | Status | ✅ | ✅ |
| Button | Flush the DNS logs | ✅ | ❌ |
| Flush the network table | ✅ | ❌ | |
| Purge FTL diagnosis messages | ✅ | ❌ | |
| Refresh data | ✅ | ❌ | |
| Restart pihole-FTL | ✅ | ❌ | |
| Run gravity | ✅ | ❌ | |
| Sensor | Active DHCP leases | ✅ + ℹ️ | ❌ |
| Active sessions | ✅ + ℹ️ | ❌ | |
| Ads blocked during the last 24 hours | ✅ | ✅ | |
| Ads percentage blocked during the last 24h | ✅ | ✅ | |
| Average number of DNS queries (queries/min) | ✅ | ❌ | |
| Configured clients | ✅ + ℹ️ | ❌ | |
| CPU usage | ✅ + ℹ️ | ❌ | |
| DNS queries cached | ✅ | ✅ | |
| DNS queries during the last 24 hours | ✅ | ✅ | |
| DNS queries forwarded | ✅ | ✅ | |
| DNS unique clients | ✅ | ✅ | |
| DNS unique domains | ✅ | ✅ | |
| Domains blocked | ✅ | ✅ | |
| FTL diagnosis messages count | ✅ + ℹ️ | ❌ | |
| Latest data refresh | ✅ | ❌ | |
| Memory usage | ✅ | ❌ | |
| Remaining until blocking mode | ✅ + 🕜 | ❌ | |
| Seen clients | ✅ | ✅ | |
| Switch | Global | ✅ | ✅ |
| Group {group_name} | ✅ + ℹ️ + 🕜 | ❌ | |
| Update | [Core update](https://github.com/bastgau/ha-pi-hole-v6/blob/de |
$ claude mcp add ha-pi-hole-v6 \
-- python -m otcore.mcp_server <graph>