core: pi_hole.enable/disable not working
The problem
Calling the pi_hole.enable or disable service does not have any effect. No errors in the logs. With debug logging on I can see the following after calling enable or disable.
[hole] Response from *hole: 200
Environment
- Home Assistant Core release with the issue: 0.109.0
- Last working Home Assistant Core release (if known): several releases already, never got it to work
- Operating environment (Home Assistant/Supervised/Docker/venv): Home Assistant
- Integration causing this issue: pi_hole
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/pi_hole/
- Pi-hole Version v4.4
- Web Interface Version v4.3.3
Pi-hole running on a separate Pi in Docker: pihole/pihole:v4.4-armhf
Problem-relevant configuration.yaml
pi_hole:
- host: 10.0.0.111
api_key: !secret pi_hole
Traceback/Error logs
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (12 by maintainers)
There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
@shenxn I was not aware of the api token UI and mistakenly used the login password 😳
The 200 response of pi-hole is very confusing. I will check how the 5.0 release that was released last week behaves and maybe create a PR to improve handling incorrect authentication.