Integration Querying in Pihole
Yesterday I upgraded from the old Homarr. I set up my integrations with the calendar, download client and DNS hole controls and summary. I've noticed that my Pihole stats have shifted greatly since I set up those integrations.
When I checked Pihole itself, it was showing that the integrations with the calendar were querying every integration I connected to it every minute. It would do the same thing with each integration for download client and DNS hole control and summary, but for every 5 seconds. When I checked the last hour, it was showing the dashboard sent 19,638 requests.
I know it wasn't like this with the old version. Is this the new normal?
4 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
The problem is that pi-hole returns a
time to live for dns query requests of 0 seconds
See https://github.com/homarr-labs/homarr/issues/1141#issuecomment-2676891690
The reason why there are so many requests in the first place is, that in 1.0+ we have background jobs that query data which is then updated in realtime with websockets on the client. So some integrations query data every 5 secondsGitHub
bug: Request are not cached resulting in high network usage · Issue...
Provide environment information any Describe the bug Some queries are not cached but should. This results in an insane amount of queries (This is a 7h span). This is because the media information f...
To me it seems excessive, but I understand how others would want that, it's just not for me. I'll look into Pihole about potentially adjusting that TTL for these, but if I'm unable to get it right, I'll either start looking for a new dashboard or go back to the old version. Thank you for the information!
Just as an information, this problem is not exclusive for Homarr and will be an issue for all of your devices in the network. Homarr is just fetching more frequently than other applications on your network, which exacerbates the issue.
I outlined the solution quite clearly in my comment in the GitHub discussion above; just follow the configuration steps clearly and you will be good to go.