core: Pi_hole integration doesn't work on pi_hole V6
The problem
On pi-hole V6, of which release is imminent, the integration no longer works. This is probably because the API has moved from pi.hole/admin/api to pi.hole/api
See:
Please make the integration recognize the new location.
What version of Home Assistant Core has the issue?
core-2024.11.1
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?
File "/usr/src/homeassistant/homeassistant/components/pi_hole/sensor.py", line 111, in native_value
return round(self.api.data[self.entity_description.key], 2) # type: ignore[no-any-return]
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'ads_blocked_today'
=========================================================
2024-11-09 21:48:25.790 DEBUG (MainThread) [hole] Response from *hole: 400
2024-11-09 21:48:25.791 DEBUG (MainThread) [hole] {'error': {'key': 'bad_request', 'message': 'Bad request', 'hint': 'The API is hosted at pi.hole/api, not pi.hole/admin/api'}, 'took': 0.0004820823669433594}
2024-11-09 21:48:25.863 DEBUG (MainThread) [hole] Response from *hole: 400
2024-11-09 21:48:25.863 DEBUG (MainThread) [hole] {'error': {'key': 'bad_request', 'message': 'Bad request', 'hint': 'The API is hosted at pi.hole/api, not pi.hole/admin/api'}, 'took': 0.0003046989440917969}
2024-11-09 21:48:25.864 DEBUG (MainThread) [homeassistant.components.pi_hole] Finished fetching Pi-Hole data in 0.154 seconds (success: True)
2024-11-09 21:48:25.865 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 266, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 481, in _async_refresh
self.async_update_listeners()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 176, in async_update_listeners
update_callback()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 561, in _handle_coordinator_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1007, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1132, in _async_write_ha_state
self.__async_calculate_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1069, in __async_calculate_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1013, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 544, in state
value = self.native_value
^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/pi_hole/sensor.py", line 111, in native_value
return round(self.api.data[self.entity_description.key], 2) # type: ignore[no-any-return]
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'ads_blocked_today'
=========================================================
Logger: homeassistant.components.binary_sensor
Source: helpers/entity_platform.py:728
integration: Binary sensor (documentation, issues)
First occurred: 14:03:25 (2 occurrences)
Last logged: 21:31:33
pi_hole: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 728, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1302, in async_device_update
await self.async_update()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 599, in async_update
await self.coordinator.async_request_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 273, in async_request_refresh
await self._debounced_refresh.async_call()
File "/usr/src/homeassistant/homeassistant/helpers/debounce.py", line 114, in async_call
await task
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 358, in async_refresh
await self._async_refresh(log_failures=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 481, in _async_refresh
self.async_update_listeners()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 176, in async_update_listeners
update_callback()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 561, in _handle_coordinator_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1007, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1132, in _async_write_ha_state
self.__async_calculate_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1069, in __async_calculate_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1013, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 544, in state
value = self.native_value
^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/pi_hole/sensor.py", line 111, in native_value
return round(self.api.data[self.entity_description.key], 2) # type: ignore[no-any-return]
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'ads_blocked_today'
=====================================================
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:918
integration: Sensor (documentation, issues)
First occurred: 14:03:25 (18 occurrences)
Last logged: 21:31:33
Error adding entity sensor.pi_hole_domains_blocked_2 for domain sensor with platform pi_hole
Error adding entity sensor.pi_hole_dns_queries_cached_2 for domain sensor with platform pi_hole
Error adding entity sensor.pi_hole_dns_queries_forwarded_2 for domain sensor with platform pi_hole
Error adding entity sensor.pi_hole_dns_unique_clients_2 for domain sensor with platform pi_hole
Error adding entity sensor.pi_hole_dns_unique_domains_2 for domain sensor with platform pi_hole
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 918, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1368, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1007, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1132, in _async_write_ha_state
self.__async_calculate_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1069, in __async_calculate_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1013, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 544, in state
value = self.native_value
^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/pi_hole/sensor.py", line 111, in native_value
return round(self.api.data[self.entity_description.key], 2) # type: ignore[no-any-return]
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'ads_blocked_today'
Additional information
The integration setup only allows a hostname or ip adress, but it doesn’t allow to point the api to pi.hole/api instead of pi.hole/admin/api
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 135
- Comments: 147 (18 by maintainers)
hey folks!
I’m not sure flooding this issue with more “it’s broken now” kind of replies will do any good. subscribe to the issue using this button
or just add your 👍🏻 reaction.
I guess someone from the Core team is aware but since there is a fix (e.g. do no upgrade yet), this issue might not be a priority soon
I’ve successfully implemented support for the Pi-hole v6 API in the original Python library python-hole. The main changes include:
pi.hole/admin/apitopi.hole/apiThe changes are currently in PR and can be referenced for implementing similar updates in the Home Assistant integration. The key change was updating the base API endpoint and adjusting the data parsing to match the v6 API structure.
Feel free to check out the implementation for reference: https://github.com/LeonKohli/python-hole/pull/new/feature/v6-api
No offense to the guys creating these workarounds, as they are great, but it’s kind of ridiculous that this is an official HA integration and the core team is entirely MIA. I understand these things take time and the teams are small, but at least some acknowledgement that it’s an issue would be nice
Just swapped over to @bastgau Pi-Hole-V6 integration, didn’t even have to change anything on the dashboard, just worked ! Removed the old “official” integration, added new via HACS and back in action.
Will be sticking to this going forward
Hello.
I have implemented the new Pi-home API inside a custom integration available here : https://github.com/bastgau/ha-pi-hole-v6
Only a few main sensors and two services to enable or disable blocking are currently implemented.
/!\ The Home Assistant v2025.03 is required to use the integration (released next week).
The
python-holedependency now officially supports v6, as the pull request has finally been merged: https://github.com/home-assistant-ecosystem/python-hole/pull/29#event-16980813327A few ours ago the dependency with the latest Pi-hole V6 changes has been released: https://github.com/home-assistant-ecosystem/python-hole/releases/tag/0.9.0
Guess it is possible to move forward and update the core integration in Home Assistant then?
I thought about modifying the original library @shenxn used, but I decided to write a separate client library for this new version of pi-hole’s API. I plan on adding more endpoints soon, but most of the ones “hole” was using are there.
pyhole6
I hope you guys find it useful.
Basically a good point.
Feel free to minimize this comment as it does not add anything substantial to fix this issue. It just puts the issue’s relevance into context.
2025.8
seems like the code owner for this integration has abandoned it; so now there is a fork to fix it.
The card is just a card stack, with an image and an entities card at the top, and bar-cards at the bottom that use Glances to show hard disk, memory, and processor information.
The middle part is a HTML Template card, with the following settings and content to match the Pi-hole web UI:
To create sid, use this curl request –
with totp if configured –
More info on here – https://docs.pi-hole.net/api/auth/
Since changes seem to be required for both the integration and the underlying library, I put togehter a POC (https://github.com/user-08-151/hole_v6) which works for my HA instance togehter with my PiHole v6 instance.
As hinted prior, the padd endpoint has most of the wanted data:
Originally posted by @mwoolweaver in #130245
Thanks for all the hard work HarvsG. Greatly appreciated.
I have finished the first draft of the pull request. #145890 If you are able please do review the code to speed up the chance of a merge. Particularly look at the tests, I do not have experience mocking APIs before and getting the tests working appropriately was a real struggle. If you are not able to contribute to the PR, please do not comment on the PR, but you can react to the first post if you wish.
Guys, please remember to star the repo to give the shout-out it deserves.
For the time being I removed the integration and implemented this: https://docs.pi-hole.net/guides/misc/homeassistant/
Better than nothing.
I have started a PR - I hoped it would only be a path change, but many of the endpoints have also been chanaged, so this will be quite a lot of work. So for I have got the sensors working but the following still needs doing:
Guys - this has been open since November '24???
@bastgau maybe you can answer that remaining question. Thanks a lot 👍
Otherwise on a long-term view I’m only highly interested in what happens with this official/core integration.
I’m still a bit surprised on the lack of information (official statement) regarding a broken and unmaintained official/core integration. All that ratings like silver/gold/… level of integrations sound kind of strange in this context. Somehow I expected a bit more. Maybe official 2.1 % usage of active installations is not enough to be relevant.
I have implemented the blocking mechanism as well as update status, using purely yaml.
@CoolnsX Would you mind posting your YAML config for those sensors? Thanks.
I only used Pi-Hole integration to notify me on a dashboard (conditional display) whether there is an update to Pi-Hole. That functionality is gone for now.
V6 is officially out today. It’s time
Support for both V5 and V6 would be trivial for now as there are still a lot of devices with V5 in production.
I have not received any reply for my attempts to contact @shenxn. I am afraid this repo is abandoned by its author.
@frenck sorry to ping you directly, but what happens when an integration is abandoned by its author? Would it be possible for someone else to become the code owner?
Just to clarify this statement, “they” (assuming you’re referring to official HomeAssistant team) are not working on the fix.
The community that built the integration is responsible for keeping it up to date. But – as we’ve seen – all it takes is one unresponsive/absent dependency owner to break the entire chain and keep things from moving forward.
@Sawtaytoes
No the native home assistant PiHole integration has not been updated, everyone just switched to newer plugin that someone else made: https://github.com/bastgau/ha-pi-hole-v6
I would like to also confirm that Bastgau HACS integration works perfectly and is very easy to set-up. My existing cards were all auto-updated, with no need to edit any of them.
Thank you!
Thanks for the new HACS v6 integration! I’m back up and running without having to tinker with my dashboard or automations.
Sorry to hear about your illness, and I don’t disagree that things happen that get in the way of maintaining these integrations, especially as many are done on a volunteer basis. What is frustrating is having no sort of fallback process for when that happens. Part of making something an official integration vs something in HACS should be a more robust process for when these things come up. Some way to escalate, transfer ownership, etc. Again even so much as having somebody pop in and say, “yes, we see you, we are trying to find somebody to work on the issue”. To me, that would be enough.
There was even a PR created a couple of weeks ago that would likely resolve the issue, but without having somebody to approve and merge it, we’re still stuck.
The Home Assistant core repo has much more stringent standards for its code, which includes the official plugins. While this is nice and good for code quality, I can totally understand how it might make a maintainer less likely to want to come back to it.
HACS integrations, each in their own repos have no such standard of code quality. It’s basically, “you get what you get and you don’t get upset”. But at the same time, a plugin implementation can be rolled out very quickly, as is the case with the new pi-hole, HACS-based plugin.
There is good and bad with both models.
note : I use shields, which is actually the dns blocking, please don’t get confused. Right now, only blocking enable/disable works, I haven’t integrated live status of pihole dns blocking (though u can see the rest api in configuration below).
Configuration
Also you have to make some more inputs in helper
Automation
Core [v6.0.4] FTL [v6.0.2] Web interface [v6.0.1] No PASS
test in JSON format:
curl -X GET "http://IP_Pi-Hole/api/stats/summary"Doesn’t help that PiHole wont let you roll back to v5 easily. Then since this issue was raised in November when the first beta’s came out its not like this comes as a surprise.
Without a release tag, it cannot be included through pip/uv (technically it could but all HA requirements are referenced using release tags). Also the HA pihole integration code needs to reflect that users must choose if they’re using v5 or v6 of Pihole. So it’s not a mere replacement of the underlying hole lib.
Since Pi-hole v5 isn’t supported by Pi-hole developers anymore due to v6 being released the v5 HA Integration should likely be removed.
Pi-hole v5 is basically EOL at this point.
NordFreak, please ping back if you find the “buyacoffee link”. I’m grateful.
TBH, we don’t know what happened to shenxn, the developer of the previous PiHole Integration (which no longer works). Sometimes people get tired of maintaining their creations, sometimes life gets in the way (child being born, family calamity, cancer [ my own personal case, stage 4 ]), or just overwhelmed w/ new job. Not a weepy violin tune from me, but it is just how it is…
On Thu, Mar 6, 2025 at 2:34 AM NordFreak @.***> wrote:
at the end of the day there is no difference between HACS and Official integrations
The last piece to the puzzle, syncing button to pihole dns blocking status –
I ditched this integration and went to the way of controlling pihole via restful integration. So far I have successfully setup pihole stats. Now working on controlling pihole using restful command integration.
how to use this?
V6 is here https://pi-hole.net/blog/2025/02/18/introducing-pi-hole-v6
Luckily I was having that “let’s see if HA side is ready for that major release” thought and found this issue very quickly. Unfortunately it seems like there’s not a solution for the Pi-Hole integration yet. What a pity 😦
So I can and will simply not upgrade Pi-Hole until HA has adopted to the V6 API changes (if that’s the only change needed).
Looking at the diagnostics you can download from the integration in Home Assistant, I see there following in the JSON file:
So it looks like it the api URL has changed at least. Hope this helps for any updates to the integration.
I’m not sure anyone is working on fixing it?? Instead, you should switch to @bastgau new unofficial v6 integration which is easily installed via HACS (it’s really very good).
https://github.com/bastgau/ha-pi-hole-v6
I’d suspect a replacement for the official integration would need to both support v5 and v6 to be compatible with existing installations that might still connect to a pihole 5 instance. You wouldn’t want to break those installations on a Home Assistant update.
What would be nice, but don’t know if it is possible, is an addition to the https://www.home-assistant.io/integrations/pi_hole/ site to add an info box that this only works with pihole v5 and have a link to the custom integration for v6 users. Might make it easier to discover and solve issues for users that update their pihole instance.
Keep in mind, to disable for ‘n’ seconds, please input value first (0 for indefinite), then toggle the switch to off.
the lovelace card…
It’s just a craft integration.
Just sharing in response to my own need.
+1
Correct. I tested it out in Home Assistant this weekend.
Then I realized I can’t run Gravity with the official version and went back to my unofficial integration 😕.
done, thanks for the hint 😉
I held out hope for a long time that the official integration would get updated, but it seems that the owner of the python-hole repo isn’t very active or responsive, so I bit the bullet and switched to the unofficial integration. Works like a charm and has all the same functionality that the official one did.
https://github.com/bastgau/ha-pi-hole-v6?tab=readme-ov-file
This works great thank you!!
@ccheath in stable the earliest you will see it is in 2025.4 which is scheduled for 2nd April (first Wednesday of the month). there is however no guarantee that it will be included at this stage. There is a process and its happening.
I don’t know why this is “on the other hand” – short of a dev stepping up to make the official integration compatible with both v5 and v6, or even pulling a v6 version together under HA’s official process as a breaking change (honestly, that’s probably the most viable approach, since the two are so very different), this is the best solution we could hope for… short of full removal of the v5 version from ha-core.
Hey!
The integration development was based on the HA beta version 2025.03.
When I installed the integration on HA 2025.02 an error occurs and I have not tried to resolve it 🤣
After that, I made the integration publicly available.
There are many constraints (or there should be) to being an official integration. I prefer to maintain a custom integration.
In my opinion, all core integrations should be gold or more : https://www.home-assistant.io/docs/quality_scale/
Can you point me to that card?
Click on ADD SERVICE Depending on whether or not you’re using SSL, it’d be either http or https
Try http://XXX.XXX.XXX.XXX:8080/api
Your port might also be 80 (instead of 8080, in this case)
Does anyone have a suggestion for why i dont get anything out of the integration?
(edit) It is bastgau’s new integration, and i am logged on the Pi-hole API with Home Assistant
The stronger likelihood is they pull the official integration out if the current code owner doesn’t make any moves to update it.
Some of these smaller integrations are throwbacks to when there wasn’t a HACS option.
I don’t plan to submit my work to become the official basic version, as there are a lot of constraints. Maintaining an alternative version seems simpler, even if one day it may become deprecated because of an official version. That’s life 😄
Don’t hesitate to help me for translation or new ideas.
@NordFreak @davygravy : Just added a buyacoffee link 😉
https://github.com/bastgau/ha-pi-hole-v6
My opinion: Forget the official one. Take the HACS version 😉
OHHHH, I thought you meant the official core integration. Yes, the HACS one works great.
Absolutely true, their integrations are just like in HACS when the developer doesn’t take care of them nothing works they need to write everywhere that they will only work if the community takes care of it, I reported a bug in the integration for more than half a year no one is doing anything about it, and I got a reply that they are working hard on it and there has been no change for half a year XDDD, I expect hate without argument.
This looks good. Thank you for sharing!
I will test it. Hopefully this can replace the current core integration of pi-hole.
For a PiHole 6 integration, I’m hoping to see more integration with the PiHole API to allow for advanced scenarios.
One scenario I’d like to be able to tackle is conditionally enabling/disabling groups on the PiHole. I use this to block certain websites at certain times (eg: YouTube on devices the kids have access to, such as tv’s, while they are not at school). With PiHole 5 there’s no API to do this, I do it by executing SQLite commands via SSH and updating HA entities to report state, but it looks to be achievable via the new APIs that are available.
At the very least, having actions that can be called to pull the state of a group and update group states would be a good first step.
@NordFreak - Probably best to take this off of this thread and into a new issue https://github.com/user-08-151/hole_v6/issues/new. ~Though, I am also running into the same problem.~
Edit: ~See https://github.com/user-08-151/hole_v6/issues/1~ Make sure to use your password rather than API key here.
In addition to that, docs can be found here: https://ftl.pi-hole.net/development/docs/
@shenxn I can confirm @Marcoevich’s issue as well. Fresh install of Pihole v6 with its new API is completely broken.
Pull request updated and ready for review again
@Sawtaytoes
Its likely that they have many issues and things they have to focus on right now, and this is probably a low priority especially since the community already has “a fix”.
But seeing as this ticked has been open since [Nov 9, 2024], (6 months and 6 days ago) perhaps there arent any core homeassistant developers right now using pihole toggles in their own setup 🤷
The current status is still that the library had the fix merged but has not yet had a release which is needed for it to filter down the chain. there is an issue about creating a release here https://github.com/home-assistant-ecosystem/python-hole/issues/31
Assume you never heard from @frenck or @shenxn . The python library being updated should resolve but looking at this thread there are many who would contribute but like an untended part of your lawn it goes to weeds making the whole lawn look untidy (i.e. my wife liked being able to use Home Assistant to turn on ads and gave me grief). I can count a meaningful percentage of abandoned integrations in the CORE and thats like leaving old farm equipment to rot in the field. Prolly doesnt hurt but you have to plow around it and people notice it. Dont want to see Home Assistant get crushed by its own weight.
Merged != released
Just as a FYI for anyone who tried this initially on 2025.02 (I suspect there are very, very few), I installed the beta integration while on 2025.02 and encountered some errors. This was before the minimum version was fixed to 2025.03 only.
After upgrading to 2025.03, I ran into an odd “Unknown error” issue that would not allow the integration to work properly.
It turns out I started too many active sessions on my pi-hole while on 2025.02. I needed to go to pihole Web Interface - API Settings and delete the multiple old active sessions to get it to work.
100 % agree, an official integration should support both v6 and <v6 setups.
That docs edit is easily possible (done similar edits few times already) - once someone approves the PR. I think that’s a good idea and would probably also pin this thread so it is more easily discoverable in the issues section (Gitahub + official docs: best thing possible, next to maybe releasing a new version without any changes but putting a hint in the release notes, maybe promoting the custom integration).
On the other hand it optimizes a suboptimal situation. My previous post was about a technical and communications solution on this. In short: what is happening with this broken and unmaintained, still labeled as official/core integration.
Thank you @bastgau Works out of the box!
For me, it was a 100% drop-in replacement, as per the image everything I needed worked on my dashboard for PI-Hole. I can’t comment on the minimum version required as I’m running 2025.3+
Glad it worked.
Thanks!! my mistake was not adding http: I just copied from the old setup
On devrait lui acheter des cafés ☕️! Your choice is yours… I bought him a few coffees. 👍🙏☕️Sent from my iPhoneOn Mar 8, 2025, at 10:36 AM, Rick @.> wrote: @bastgau You are the best. This new integration works perfectly 🥳🙏—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>
Marcoevich left a comment (home-assistant/core#130245) @bastgau You are the best. This new integration works perfectly 🥳🙏
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
@bastgau You are the best. This new integration works perfectly 🥳🙏
Please open a new issue if you need new features 😉
https://github.com/bastgau/ha-pi-hole-v6/issues/2#issue-2888750805
But then I would think you have a completely different problem. With the new core and the new version of here: https://github.com/bastgau/ha-pi-hole-v6 (I installed it via HACS) it worked right away. Even better than the old integration.
What exactly is your error? What do the logs say?
thanks for your work, pihole v6 is working with the new core version of ha.
i’m searching for your buyacoffee link 😉
Just a small correction for the version template
You either need the latest beta version 2025.3.0b0 or wait till next week when 2025.3.0 is officially released.
that is shown here
https://docs.pi-hole.net/guides/misc/homeassistant/?h=home
hey @user-08-151 !
Thank you for sharing this with us. I have also integrated this directly and am now integrating it. However, when I try to connect, I get the error below.
Do you have a tip for me?
[%key:common::config_flow::error::cannot_connect%]
I tested that fork and it still doesn’t work. It doesn’t handle the session properly. I tested the package by itself with the “example.py” file and no luck.
I’ll see if I can get it working and submit a PR.
I dug into this today and it looks like the issue is very likely to be related to the hole package, which is a dependency that is used to make the actual api call. It doesn’t look like the package has been updated for v6.
Mine rolled back ok. Started with a teleport/backup before doing the docker image pull. After I decided to roll back, just change:
Then teleport/restore. I think I had to manually restart DHCP, but it’s back to how it was an hour ago.
the
paddendpoint might be a good starting point as well.it’s what is used for PADD to reduce the number of API calls. Should give enough data to provide a small dashboard in home assistant.
Since the integration maintainer @shenxn seems to be not responding, what can we do to get this fixed? Can we get someone to take over the integration?