Done. And thanks.
Thanks for this. Done
That did not fix my problem. =(
pi_hole:
host: pi.hole
verify_ssl: false
so does pi.hole resolve on your system?
My pi-hole works but I get these errors. I am using the pihole addon through the add-on store.
I have a command to get the pihole status and that works.
- platform: command_line
name: PiHole Status
command: curl -X GET 'http://XXX.XX.XX.XX:4865/admin/api.php?status'
value_template: >
{{ value_json.status }}
I’ve tried
pi_hole:
pi_hole:
host: pi.hole
pi_hole:
host: XXX.XX.XX.X:4685
pi_hole:
host: 'localhost:4685'
pi_hole:
host: pi.hole
verify_ssl: false
the entities for it remain unavailable but show up
Hello everyone,
After the latest update to 0.99.3 version, out of the blue I started to receive the following error:
Any ideas how I can fix it?
That is not what I asked you. I asked whether pi.hole resolves, ie resolves to an ip address.
Sorry didn’t quite understand but since the command works
http://XXX.XX.XX.XX:4865/admin/api.php?status
I can type it into a browser and get info
does that answer what you’re asking?
No I mean does the address pi.hole resolve to an ip address? What is the response to the following in a terminal on your home assistant computer?
nslookup pi.hole
Execute shell command
Command executed: nslookup pi.hole: 1
Server: 127.0.0.11
Address: 127.0.0.11#53
** server can't find pi.hole: NXDOMAIN
There’s multiple possible issues here. The current refactored code doesn’t support multiple pi_hole instances - but this bug shows that the developer is working on it
There’s another one if you attempt to connect to a system that validates to a self signed certificate the verify_ssl: false does not work
Which I logged - I proposed a workaround in the code on that bug check.
I think there is another one where if you want to add a hass.io pihole instance the port number needs to be specified with the host e.g. host:pi.hole:4685
I also believe there’s an issue where it does not collect the data at startup - the first time it worked for me was 5 minutes after startup.
Set SSL to false in the Pi Hole config, not your configuration.yaml
file.
{
"update_lists_on_start": true,
"ssl": false,
"certfile": "",
"keyfile": "",
"interface": "",
"ipv6": true,
"ipv4_address": "",
"ipv6_address": "",
"virtual_host": "myddns.service.net",
"hosts": [],
"password": "PASSWORD",
"admin_port": 4865,
"dns_port": 53
}
After update I get alot connection timed out with my Logitech Harmony.
2019-09-27 19:26:55 ERROR (MainThread) [aioharmony.hubconnector] XXX.XXX.X.XX: Connection timed out for hub XXXXXX1
2019-09-27 19:31:45 ERROR (MainThread) [aioharmony.hubconnector] XXX.XXX.X.XXX: Connection timed out for hub XXXXXX2
pi_hole:
host: '1xx.1xx.x.x:4865'
verify_ssl: false
This ended up working in my configuration.yaml
. I didn’t change the Pihole configuration at the time but I did now just for consistency.
Thank you.
Your zwave hub has likely changed USB port.
hi all, I have an issue with pihole integration since that version (as mentioned by @Literoya),
I’m using Hass.io but pihole is installed on another server.
the configuration of the pihole is with SSL (not self-signed).
Ping is working from the console of the docker to the pihole ip.
my configuration is with domain name in the host,
tried to run the example from hole (available in GitHub) and it works for me, when running it through the HA, i get the following error: [hole] Can not load data from *hole: pi.DOMAIN.NAME
pi_hole:
name: "name"
host: pi.DOMAIN.NAME
location: "admin"
ssl: true
verify_ssl: false
Does pi.DOMAIN.NAME resolve to an IP address on the HA machine?
from the same box can you connect to https://PI.domain.name/admin?
wait 5 minutes after startup - does that provide any further messages?
Yes, also managed to run the example code from hole github over there and managed to get results, from with HA it fails