-
-
Notifications
You must be signed in to change notification settings - Fork 91
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] PiHole (Device sync) not working due to incorrect PIHOLE_CMD SQL query #521
Comments
Hi there! Can you please provide the log for the PiHole plugin load from the pialert.log file? The relevant section should contain a log similar to the one below (notice the first line):
If nothing too different shows up, check also the Plugins objects imported by the plugin: |
One more thing - can you try to use the dev branch to see if issues persist? version: "3.9"
services:
pialert_dev:
...
image: "jokobsk/pi.alert_dev:latest"
...
|
I see more information on the logs now with the _dev: |
Can you try to replace the PIHOLE_CMD setting with the following value?
|
New log file: |
Thanks! I can still see the old setting value in the log:
Can you make sure the setting is set to (notice the
|
Oh... I thought I double-checked that. Anyway, now it is working! Thank you, and happy new year! |
Thanks for the update, the default value will be fixed in the next release 👍 |
Released -> Closing |
First time install, I have four scanners: Internet-Check, PiHole (Device sync), DHCP Leases (Device import), and Arp-Scan (Network scan). They are all on the same schedule [*/10 * * * *]. DHCP leases and ARP took a while to produce anything, but they are working. I don't see anything coming from PiHole (Device sync). I enabled debug but cannot see anything abnormal in the log. I also had debug on because I couldn't make SMTP publisher work but I quit that and configured apprise to talk to my SMTP. During that time, no errors from SMTP were in the log, so I wonder where all plugin errors go.
The files are properly mounted, I logged inside the container just to make sure it was there (/etc/pihole/pihole-FTL.db)
Happy to provide more information.
The text was updated successfully, but these errors were encountered: