I came across something surprising recently, and I was wondering if anyone else had come across it: I keep everything in my home networks on static IP reservations so that the devices on my home and IoT networks are clearly identified in my router setup. Recently, I noticed an unknown device in active DHCP leases and started looking for it. I came to realize that it was one of my HomePods, but I was surprised to see that the MAC address didn't match what the Home app for the device looked like. Upon restart, the HomePod mini will ping for approximately 30 seconds at the reserved reserved IP address before making another DHCP request under another MAC address and switching IPs ... another restart would result another new MAC address and another new IP. address and so on. Pinging room-name-homepod.local was helpful in understanding what was going on. This looks exactly like the functionality of the iOS / iPadOS / WatchOS "Private Address" feature, but from what I've read, HomePod shouldn't [support this](https://support.apple.com/en-ca/HT211227). As a test and without touching my router configuration, I made sure that the "Private Address" setting is disabled for the iPhone network, and I reset the HomePod mini and set it up fresh. No problem then, HomePod constantly gets the right IP through reboots. Maybe this is just an error, or maybe the "Private Address" setting was turned on and transferred from my iPhone when I set up this HomePod, and this is an expected behavior? Has anyone else suffered from this? Editing: Spelling change 2: It seems to be related to use as an AppleTV home theater speaker. See [sabinfigaros comment](https://www.homekit.blog.com/r/HomeKit/comments/rxkcqh/comment/hritgw0/?utm_source=share&utm_medium=web2x&context=3)