-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Pi-hole switch always in 'off' mode. #46
Comments
Hi @PatriceRobert, you're not the only reporting this issue as other users are experiencing this bug with the latest pi-hole versions. I am leaving this issue open as a spike. |
Yes, finding this is the case also on Pi-hole v5.8.1 FTL v5.13 Web Interface v5.10.1 & homebridge-pihole v0.4.1 |
haha I just spent 1-2 hours trying to get this to work my toggle was always set to disabled even though pihole was enabled. I am guessing this bug is still active? Because otherwise this is not working at all for me it works in homeassistant with their plugin flawlessly but I am trying to go away from homeassistant because it is just to much hassle to get it to work |
I rebuilt my homebridge as hoobs this morning and have spent hours trying to sort this! |
Ye it sucks it works perfect in homeassistant though so I guess it is coded better in there |
Here's the update from the PiHole release team: Soon-ish™ But really, it all depends on when we can align ourselves to get a release prepped and pushed out. We (the folk that press all the buttons) all live in different parts of the world, so it can be tricky to tie down a time sometimes. The fix will be in the next release, but I can't tell you at this point in time when that next release will be without being as vague as Soon. |
I've created a pull request that works around the Pihole bug: #49 |
Hi everyone, and thank for the support! |
I had been running the same issue but it seems to be fixed in Pi-hole v5.9 FTL v5.14 Web Interface v5.11 Here's the update from admin thread |
Pi-hole switch always in position 'Off' in homekit.
Steps to reproduce the behavior:
The actions are well executed via API so connection is ok, API key is correct and working fine, the only issue is to see the Pi-hole switch back to 'Off' all the time.
This is happening since the latest Pi-hole update running under docker:
No a big issue as it's still working but annoying as we cannot get the correct state and it can break some automations.
The text was updated successfully, but these errors were encountered: