I think you can adjust the scan interval in HA, if it is that important.
The scan interval of devices can be changed - true.
But not the behavior of DNS requests that comes with that - even with DHCP.
Meaning I tried to influence the caching as part of the DHCP request by giving the HASS server a âfixedâ IP address based on the MAC-address of the NIC.
Part of the DHCP request is DNS - which includes some caching timers. Tried to set these for 24-hrs - including the NX responses. It looks like HASS is ignoring these.
But if this caching thing is the âbiggestâ problem in my life I guess I can live with that⌠
The DHCP options you are talking about is only suggest time-to-live (TTL) values for that specific device that makes the DHCP request and only if the DNS service accept dynamic allocations.
Often the DNS server do not accept dynamic allocations and when it do it is even rarere to actually take those TTL values into account.
I was able to work around this from the DNS server side. Iâve switched to Technitium DNS and configured the Filter AAAA app so that Home Assistant receives NODATA responses for AAAA requests with a SOA record specifying a TTL of 600 seconds. This makes the response cacheable and HA indeed only asks about the respective domains every 10 minutes (instead of once per poll) which greatly reduced the overall DNS traffic in my network.
That is probably the best solution possible.
It is using a true DNS service in a setting that it is meant to used in and it is not trying to change the devices or the protocols.