Write a feature record for the exact device
Use one row for each function you actually need: basic on/off, dimming, lock state, temperature, energy reporting, scenes or notifications. For every row, record whether the function is exposed through Matter, remains vendor-app-only or is unresolved. Include device model, region, firmware, bridge firmware and the controller application version so the record can be checked again after an update.
A bridge adds another compatibility boundary
A Zigbee accessory behind a Matter bridge is not a native Matter-over-Thread accessory. The bridge decides what it exports. Home Assistant documents that Hue's native local integration offers Hue-specific functions beyond the basic controls exposed by its Matter bridge. That is a concrete reason to compare integration routes rather than replacing a working native route for the Matter label.
Pairing locally and controlling remotely are different
Apple documents direct local accessory pairing and control on supported iPhones and software, with additional hub and Thread conditions. That does not imply an unattended household has a complete remote-control path. Record which always-on controller, border router and account must be available for each routine, then distinguish local operation from control while away.
Test the intended route before moving the whole home
Start with one non-essential accessory. Check the required controls, a second household user, a router restart and loss of internet while the local network remains powered. Save the working settings before changing networks. Home Assistant's Matter documentation requires local IPv6 and multicast discovery; isolated networks need explicit network design, not random firewall changes.