I believe there is a UI/data-model issue with how Ring displays the MAC address for cameras that support both Wi-Fi and Ethernet/PoE.

I have six Ring cameras:

• 3 × Outdoor Cam 4K using PoE
• 2 × Outdoor Cam 4K using Wi-Fi
• 1 × Wired Doorbell using Wi-Fi

I tracked each device individually through DHCP requests after rebooting them.

The results are consistent:

• For all 3 cameras operating over Wi-Fi, the MAC address shown in the Ring app matches the MAC address seen by my DHCP server.
• For all 3 cameras operating over PoE/Ethernet, the MAC address shown in the Ring app does NOT match the MAC address seen by DHCP.
• The PoE MAC addresses all share the same manufacturer/OUI, while the Wi-Fi MAC addresses share a different manufacturer/OUI.
• The Ring app nevertheless continues to display the Wi-Fi interface's MAC address.

This strongly suggests that the camera has separate MAC addresses for its Wi-Fi and Ethernet interfaces, but the Ring app is displaying the Wi-Fi MAC as the generic "MAC Address" regardless of which interface is currently being used.

I recommend changing the Device Health/Network UI to explicitly distinguish:

• Wi-Fi MAC address
• Ethernet MAC address
• Active network connection/interface

For example:

   Connection: Ethernet (PoE)
   Ethernet MAC: xx:xx:xx:xx:xx
   Wi-Fi MAC: xx:xx:xx:xx:xx

This would prevent confusion for customers using DHCP reservations, VLANs, firewall rules, network monitoring, and other network-management systems.

I believe this is a UI/data-model issue rather than MAC randomization. The behavior is reproducible across three separate PoE cameras, while Wi-Fi-connected cameras correctly report within the Ring app the MAC seen by DHCP.