Skip to content

Poll for new status after update #23

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

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

natefox
Copy link
Contributor

@natefox natefox commented Aug 7, 2024

@warmfire540
Copy link

@natefox how reliable is this 100ms delay? will sometimes it be 120ms needed, etc?

if we know we are disabling, could we poll until it is actually disabled? maybe someone has a slow network or slow pi-hole

@natefox
Copy link
Contributor Author

natefox commented Aug 11, 2024 via email

@natefox natefox changed the title add 100ms delay for pihole to catch up Poll for new status after update Sep 1, 2024
@natefox
Copy link
Contributor Author

natefox commented Sep 1, 2024

Finally got around to updating this. Opted to keep the polling within the original timeout(5) rather than add another timeout just for the polling. I'm open to adjusting though.

@Jab2870
Copy link

Jab2870 commented Oct 31, 2024

so, just wanted to give feedback and say that this patch is working and has been working fine for me for a while. Is there any specific tests anyone would like me to do that might help get it merged?

@fabaff fabaff merged commit 364097a into home-assistant-ecosystem:master Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pi-Hole switches bounce back to enabled after disabling
4 participants