Hi!
Having a problem here accessing the API. I have an app with hardcoded URL http://[IP]/admin/api.php. But in my installation the API is available at http://[IP]/api.php.
There is no admin-login at all? When opening the webUI from outside homeassistant the URL shown has no path /admin as well although I’m logged in with user homeassistant.
Container Host Description
4865/tcp 4865 API endpoint (For HA integration)
53/udp 53 DNS server port
80/tcp 80 Web interface (Not required for Ingress)
@Klagio If you configure your Pi-Hole integration and switch using “localhost:4865”, then access from your Home Assistant instance should just work.
At least, once I read the docs (including the parts I missed the first time), made the changes, and rebooted Home Assistant (full restart), it’s working for me.
My integration is bog standard, but here’s what I’m using for my switch:
# "Simple" method for disabling Pi-Hole on both instances
# This method requires hard-coded strings for the commands, no secrets
switch:
- platform: command_line
scan_interval: 10
switches:
pihole_switch_hassio:
friendly_name: "Ad Blocking (HA)"
command_on: "curl -X GET 'http://localhost:4865/admin/api.php?enable&auth='"
command_off: "curl -X GET 'http://localhost:4865/admin/api.php?disable=60&auth='"
command_state: "curl -X GET 'http://localhost:4865/admin/api.php?status'"
value_template: "{{ value_json.status == 'enabled' }}"
As you can see, just using the empty API key auth= (along with localhost) is the trick.
mmhhh I have two instances of HASSIO, on my main I use Adguard, on my second I use pi-hole. And then I use as DNS address 1 the address of HASSIO main, and DNS address 2, the address of HASSIO second
SO from HASSIO main, I guess I can’t access the HASSIo/PI-HOLE on the second? Because I wish to have the 2 switches (to turn on/off Adguard and turn on/off pihole), only in HASSIO main
Of course I will not use localhost, but just the IP address 192.168.1.x
Hello,
is there a way to start pihole addon not from Supervisor ?
I use portainer and everytime i try to start pihole addon from portainer, pihole starts and then stop it.
This is useful in case of docker upgrade, since pihole will not restart by itself and will not turn it on automatically.
Or maybe i’m blind, if there is a way let me know, thanks.
ah, an HA script, i thought it was a bash script
Thanks for that, will do some tests.
It’s really strange why some docker containers can’t start by itself via cli or gui while other containers can
I’m not really a fan of “let low level tasks be done via HA” and hope it could be fixed a day.
no error, but only pihole is not restarting.
i’m starting to really hate pihole
EDIT: seems not working via script or automation, but works with nodered.
Just make an http request node to fire when any pihole sensor became “unavailable” ( events state node ).
The http node needs to send a POST to:
Authtentication Type bearer and insert a long live token ( generate one from HA ).
As soon as nodered read the unavailable state for the sensor, pihole is restarted.
A bit tricky but this one works.
Really not sure why but I cannot get my Pi Hole stats to display in my Lovelace cards - it just says everything is unavailable. It used to work but stopped last year and now I cannot work out why. Pi Hole itself works fine.
I’ve Googled it and tried every suggestion I could see - every host variation with / without port, putting verify_ssl = true, etc. Does anyone have anything else I could try?
2020-03-23 20:05:56 ERROR (MainThread) [homeassistant.components.pi_hole] Unable to fetch data from Pi-hole
2020-03-23 20:11:06 ERROR (MainThread) [hole] Can not load data from *hole: localhost:4865
