-
Id like to understand why these query rates are so high.
Hue Sync PC software seems to query api.amplitude.cim 15k times per day on my network!
Stonehedge-
So just looking at the last 24 hours:
nest.com is hit 2422 times, of which 1508 are logsink.devices.nest.com (the others must be under 350 each, as they don't show in the top 10 resolved domains)
ubnt.com is hit 2906 times, of which 2752 are ping.ubnt.com (again, others must be under 350 as per above)
For Nest, I've 6 Nest devices, 4 of which are hard wired to power. My understanding is that the battery powered ones only check connectivity a couple of times a day, whereas the others are much more frequent. That would make 4 devices checking in 1508 times, meaning each does it ~375 a day, or 15 times an hour, so once every 4 minutes ish.
With the Unifi one, I do wonder if each device on the network checks in individually, I've 3 switches, 4 APs and a cloud key, so that's 8 devices. If it is each device, then that would be each 344 per day, or ~15 and hour again,
I'll try to dig out other domains later on.
MrDrem
ubnt.com - the performance stats on the internet and I think some of the external app bits
nest.com - I suspect that ability to check in on the Nest bits that I've got round the house (3 thermostats, and 3 smoke alarms)
I think that even if they are blocked at nextdns, they still count as a lookup (which is fair enough)
I think that unbt had about 10k lookups (which is slightly nuts, a ping every 30 seconds), and nest about 5K (so one a minute, again a bit nuts TBH).
A PiHole looking to limit queries via aggressive caching and letting nextdns do the heavy lifting might be the answer