Enhancement/add support pihole v6

[KallanX]

Adding support for the newly released Pi-hole major version 6. This update changed how you interact with the API.

[ralphocdol]

You could probably get away with using the existing password though that's for the maintainer to decide

[ralphocdol]

Missing allowInsecure, I was getting certificate error

[ralphocdol]

The API was rewritten, and so are the output, it looks like you're still using the same piholeStatsResponse as v5. I think you'd need to query multiple API from pihole to get those required data as /api/stats/summary doesn't have everything required for the widget to work.

# Probably for QueriesSeries and BlockedSeries, 
# or not
/api/stats/database/summary?from=1740020400&until=1740021160`

# TopBlockedDomains
/api/stats/top_domains?blocked=true&count=10

The rest should be available from the first query.

[KallanX]

@ralphocdol I've been able to fix a good portion of your comments. The only thing left is for me to understand these two values:

QueriesSeries piholeQueriesSeries `json:"domains_over_time"`
BlockedSeries map[int64]int       `json:"ads_over_time"`

Are these in the original /api/stats/summary response or are they separate? I was able to grab the top blocked domains by hitting the separate /api/stats/top_domains?blocked=true.

[ralphocdol]

@KallanX I think this has something to do with the widget's bar graph based on the comment on this code

// Pihole _should_ return data for the last 24 hours in a 10 minute interval, 6*24 = 144
if len(r.QueriesSeries) != 144 || len(r.BlockedSeries) != 144 {
	return stats
}

So the API /api/stats/database/summary?from=1740020400&until=1740021160 was incorrect.

Looking at the screenshot from the DNS Stats docs

The reddish one is most likely the BlockedSeries while the gray one is the QueriesSeries

[ralphocdol]

/api/history looks closer

{
  "history": [
    {
      "timestamp": 1511819900.539157,
      "total": 2134,
      "cached": 525,
      "blocked": 413,
      "forwarded": 1196
    },
    {
      "timestamp": 1511820500.583821,
      "total": 2014,
      "cached": 52,
      "blocked": 43,
      "forwarded": 1910
    }
  ],
  "took": 0.003
}

BlockedSeries = blocked
QueriesSeries = total

[KallanX]

@ralphocdol

This kind of got away from me. Took some time away to think about it all. I really don't understand why the Pi-hole developers had to change so much of their API. If it was for security reasons, I would argue they make it an opt-in feature, rather then a permanent feature. As I would assume most users of Pi-hole host their instances within their own home networks with no outside access (as I do) which would make the security argument a rather mute point.

I ran into an issue where SIDs were refused access after a period of time and hitting any endpoint would not revive them. So I had to include a check function along side a fetch function for the SIDs.

Anyways, check the latest. Let me know.

[ralphocdol]

Made a pull request on your fork KallanX#1

[ralphocdol]

Let's wait for the maintainer @svilenmarkov to review this.