External pi-holes and 0.99.2, cannot configure more than one

mattlward · September 21, 2019, 4:56pm

I have 2 pi-holes running and until now was able to monitor both. With the new configuration.yaml directive, I can configure only 1 of the units.

The first does not work because you can only use the key “host” 1 time and the second does not work because the name pi_hole2 is not valid.

Can someone explain how I can see both units?

pi_hole:
  host: 192.168.1.4
  host: 192.168.1.7

    
pi_hole2:
  host: 192.168.1.7

alander · September 21, 2019, 5:10pm

Me too - that’s one of my problems - although can’t get my Raspbian setup to even connect to one. I’m guessing it works for the hassbian version for a single pihole instance?

mattlward · September 21, 2019, 5:15pm

It does work for a single pi-hole. The sensor names even remained the same. I have also tried the following which the config editor is happy with… but it still throws an error at boot and results in none of the pi-holes showing up.

pi_hole:
  host: 
    - 192.168.1.4
    - 192.168.1.7

I am beginning to think that they made the assumption that a person would only run 1 pi-hole and did not include the option for 2.

Sounds like a bug to me.

mattlward · September 21, 2019, 5:18pm

Even more annoying, the configurator option to restart hass does not seem to do a full restart now. It is doing something as I get new notifications, but it is not restarting the whole thing. I am having to restart via the CLI.

alander · September 21, 2019, 5:32pm

I’ve seen it where a component causes it not to gracefully shutdown and keep running and you have to kill the hass daemon or restart the OS to fix it.

I think that they may have tested or chosen to support only a single pihole?

I’ve tried the following in configuration.yaml

pi_hole:
  host: pihole.local
  location: admin
  ssl: true
  verify_ssl: false

2019-09-21 18:20:34 ERROR (MainThread) [hole] Can not load data from *hole: pihole.local
2019-09-21 18:20:34 ERROR (MainThread) [homeassistant.components.pi_hole] Unable to fetch data from Pi-hole
2019-09-21 18:25:55 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed on verifying the certificate
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 625, in _on_handshake_complete
    raise handshake_exc
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 189, in feed_ssldata
    self._sslobj.do_handshake()
  File "/usr/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1056)
2019-09-21 18:25:55 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error in data received
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
    ssldata, appdata = self._sslpipe.feed_ssldata(data)
  File "/usr/lib/python3.7/asyncio/sslproto.py", line 189, in feed_ssldata
    self._sslobj.do_handshake()
  File "/usr/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1056)
2019-09-21 18:25:55 ERROR (MainThread) [hole] Can not load data from *hole: pihole.local
2019-09-21 18:25:55 ERROR (MainThread) [homeassistant.components.pi_hole] Unable to fetch data from Pi-hole

It seems to not accept the verify_ssl command that ignores that it is a self signed certificate (and it worked in previous versions when it was in sensors.yaml.

mattlward · September 21, 2019, 5:35pm

Oddly enough… adding the following as stated below finds my lowest ip numbered pi-hole but still does not find the second.

pi_hole:

alander · September 21, 2019, 5:39pm

According to https://www.home-assistant.io/components/pi_hole/
It defaults to pi.hole. If you resolve pi.hole I guess you’ll get that first IP address 192.168.1.4

mattlward · September 21, 2019, 5:42pm

That is exactly what is happening. An nslookup from the home assistant cli results in that ip address.

alander · September 21, 2019, 5:43pm

Looks like others are wanting to support more than one pihole and have reported it!

github.com/home-assistant/core

Refactor pihole integration

opened 09:02AM - 18 Sep 19 UTC

closed 06:43PM - 12 Dec 19 UTC

daveyrb

integration: pi_hole

**Home Assistant release with the issue:** 0.99.0b3  **Last working Home Assistant release (if known):** 0.98.5 **Operating environment (Hass.io/Docker/Windows/etc.):** Docker  **Component/platform:**  https://github.com/home-assistant/home-assistant/pull/25837 **Description of problem:** I currently have two Raspberry Pi's running Pi-Hole for resillience. I then add both sensors together in a template sensor to create totals for the below from both Pi-Holes - ads_blocked_today - ads_percentage_today - dns_queries_today With the new configuration I can only enter one host. **Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant):** ```yaml ############################################################################### # Pi Hole DNS Sensors ############################################################################### - platform: pi_hole host: !secret dns_1 location: !secret pi_hole_location monitored_conditions: - ads_blocked_today - ads_percentage_today - dns_queries_today #- domains_being_blocked #- queries_cached #- queries_forwarded #- unique_clients #- unique_domains #-----------------------------------------------------------------------------# - platform: pi_hole host: !secret dns_2 location: !secret pi_hole_location monitored_conditions: - ads_blocked_today - ads_percentage_today - dns_queries_today #- domains_being_blocked #- queries_cached #- queries_forwarded #- unique_clients #- unique_domains ############################################################################### ############################################################################### # Pi Hole DNS Template to add both sets of data together from both DNS's ############################################################################### - platform: template sensors: dns_queries: friendly_name: "DNS Queries" value_template: >- {{ ( (states('sensor.pi_hole_dns_queries_today')|float) + (states('sensor.pi_hole_dns_queries_today_2')|float) )|round(0) }} #-----------------------------------------------------------------------------# - platform: template sensors: adverts_blocked: friendly_name: "Adverts Blocked" value_template: >- {{ ( (states('sensor.pi_hole_ads_blocked_today')|float) + (states('sensor.pi_hole_ads_blocked_today_2')|float) )|round(0) }} #-----------------------------------------------------------------------------# - platform: template sensors: percent_of_adverts_blocked: friendly_name: "Percent of Adverts Blocked" unit_of_measurement: '%' value_template: >- {{ ( (states('sensor.pi_hole_ads_percentage_blocked_today')|float) + (states('sensor.pi_hole_ads_percentage_blocked_today_2')|float) )|round(2) }} ############################################################################### ``` **Traceback (if applicable):** ``` ``` **Additional information:**

mattlward · September 21, 2019, 5:44pm

Thanks, I was just prepping to do the same thing! This is a big oversight, or admins do not understand how these are implemented.

alander · September 21, 2019, 5:52pm

Hopefully it’ll be an easy fix to implement!. I’ve logged my issue too

ohadbenita · November 18, 2019, 7:08am

I’ve been having the exact same issue, the PR currently in review.