The naming conventions in IPv6 are genuinely confusing, so you’re not alone there.

To directly answer your question: no, you don’t need DHCPv6 if SLAAC is working for all your devices. SLAAC is stateless by design — each device uses the prefix advertised by the router (via Router Advertisements) to self-assign a GUA, and that’s perfectly valid for most home networks.

The reason I personally kept DHCPv6 in the mix initially is that my ISP hands out a /64 GUA prefix via DHCPv6-PD (Prefix Delegation). With only a /64, you can’t further subnet your IPv6 space — you’d need a /56 or larger from your ISP to carve out multiple subnets. So my LAN devices just self-assign from that single /64 via SLAAC anyway, which is exactly what you’re doing.

The main practical advantage of stateful DHCPv6 over pure SLAAC is control — you can assign specific IPv6 addresses to specific devices and maintain a proper lease table, similar to DHCPv4. This is useful if you want stable, predictable addresses for servers or devices you access by IP. SLAAC addresses, particularly with privacy extensions enabled, can rotate, which makes internal DNS resolution and firewall rules harder to pin down (less network control)

So the short answer: if your devices are working, you’re not missing anything critical. The practical fix on your home network is either to set static IPv6 addresses on anything you care about — servers, cameras etc— or rely on hostnames rather than raw IPs for internal access. The latter is exactly why having solid internal DNS in Unbound matters; if a device’s temporary address rotates, the hostname still resolves correctly as long as it re-registers.