PiHole Switch

Geoff_B · October 8, 2021, 6:03pm

Ok, I figured out the missing API key entry in the config flow, for whatever reason my brain glossed over the ‘statistics only’ checkbox. Once I uncheck that, a second screen follows with an API key prompt (duh).

I still don’t get timely refreshes. Looking in the code I see
MIN_TIME_BETWEEN_UPDATES = timedelta(minutes=5)

Can we consider adding this to the config flow and making it a parameter?

ffm777 · October 9, 2021, 9:24am

Same problem here. The Pi-Hole switch used to work perfectly, where the status instantly updated even if the Pi-hole was disabled through the web interface. Not working anymore. I can disable the Pi-hole with the switch, however the switch goes back to on almost instantly despite the Pi-hole being disabled. This way it is really unusable.

Manlycookiebear · October 18, 2021, 12:40pm

Having this problem as well. A fix would be wonderful.

goobags · October 19, 2021, 9:02am

Also having this problem. Anyone raised an actual issue for it?

VerifiablyMrWonka · November 4, 2021, 5:28pm

github.com/home-assistant/core

Pi Hole does not immediately update switch/sensor status on changes.

opened 05:26PM - 04 Nov 21 UTC

cooperaj

### The problem The Pihole integration provides a switch/sensor that tells the …user what the status of their PiHole is i.e. blocking or not blocking ads. It's possible to disable it for a period of seconds in the PiHole UI or using the switch and service using something like ``` service: pi_hole.disable entity_id: switch.pi_hole data: duration: '00:00:15' ``` This will correctly shutoff PiHole for 15 seconds. After that time has elapsed the PiHole UI will show that the service is back up and running, however the sensor/switch in Home assistant takes a significant amount of time to revert back to 'on'. This makes it quite difficult to provide a nice responsive UI to a HA user. For instance they may click a button to turn off blocking, and come back later to try again only to find it still says things are off even though their site doesn't work correctly. I believe the issue is a hardcoded update interval in the integration. ### What version of Home Assistant Core has the issue? 2021.10.6 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Container ### Integration causing the issue Pi Hole ### Link to integration documentation on our website _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

There is now.

oalbaf · February 9, 2022, 8:43am

You can create a command line switch. Here is a switch that turns off Pi-Hole for an hour. Work’s fine.

You must search and changeWEBPASSWORD and known Pi-Hole IP.

# For find WEBPASSWORD execute 'cat /etc/pihole/setupVars.conf' in your Pi-hole Server.
switch:
  - platform: command_line
    switches:
      pihole:
        command_on: "curl -ks 'http://X.X.X.X/admin/api.php?enable&auth=WEBPASSWORD'"
        command_off: "curl -ks 'http://X.X.X.X/admin/api.php?disable=3600&auth=WEBPASSWORD'"
        command_state: "curl -ks GET 'http://X.X.X.X/admin/api.php'"
        value_template: "{{ value_json.status == 'enabled' }}"
        friendly_name: Pi-Hole

Ragetti13 · March 5, 2022, 12:34pm

How can you amend the command line to use the !secret facility so as to not have the password within the main configuration.yaml?

oalbaf · March 10, 2022, 2:51pm

Try the following, but I don’t think it will work.

command_on: !secret <command_on_line_name>

GaryK · December 7, 2022, 3:56pm

I’ve added the Pi-Hole integration to my HA instance and used your command_line switch successfully to enable/disable DNS filtering. For automation purposes, could I use similar syntax to send the Pi a sudo shutdown now command?