TP-Link Omada MAC filtering becomes unreliable after making changes — anyone else experiencing this?

I’m running an Omada setup with an OC300 controller, ER8411 gateway and EAP772 access point.

I’m having a very strange problem with MAC filtering / allow-listing.

The basic situation:

• I have MAC filtering enabled with specific devices allowed.
• Devices initially connect correctly.
• If I modify the MAC filtering configuration — for example, remove a MAC address, unblock a device, or change the allowed list — Omada can become inconsistent.
• A device that should be allowed can suddenly no longer connect.
• The MAC address may still appear somewhere in the Omada configuration/client information even though it has been removed or unblocked.
• In some cases, the device completely disappears from the expected connected/blocked state in Omada, making it difficult to understand what is actually being enforced.
• Re-adding the MAC address does not necessarily restore connectivity immediately.
• This seems to behave almost like Omada is retaining a stale MAC-filtering state/cache somewhere.

I have also experienced this with an Apple device using the same Wi-Fi network and the same automatic/private MAC configuration. MTU is standard (1500).

At this point, I suspect either a MAC filtering bug, stale state between the OC300/EAP, or a synchronization problem in Omada, rather than a simple incorrect MAC address.

Has anyone experienced this behavior with recent Omada firmware?

OC300 + ER8411 + EAP772

I would particularly like to know if there is a recommended way to completely clear/reset the MAC filtering state without having to reboot the entire network.