parental controls or device prioritization just stopped working after an app update.

Diagnosis

The failure of Parental Controls and Device Prioritization on the Linksys Velop MX5300 is typically caused by a synchronization mismatch between the Linksys Cloud account and the local firmware's API. When the app updates, the authentication tokens used to push "Quality of Service" (QoS) rules and "Pause Internet" commands to the node can become corrupted or desynchronized. This creates a state where the app interface shows a feature as "On," but the actual routing table on the MX5300 hardware has not received the instruction to drop packets or prioritize traffic. You can confirm this by checking the "Device List" in the app. If a device is marked as "Paused" but can still ping an external server (like google.com) or browse the web, the control plane has failed. This is often exacerbated if the node is running an outdated firmware version that is no longer fully compatible with the latest app's API calls, leading to a "silent failure" where no error message is displayed, but the functionality simply ceases to exist.

How to Fix It

To restore the handshake between the app and the MX5300 hardware, you must perform a synchronized power cycle and a cache clear of the management interface.

1. Force close the Linksys app on your mobile device by swiping it away from your active apps list.
2. Physically unplug the power adapter from the primary Velop node (the one connected to your modem). Leave it unplugged for exactly 60 seconds to ensure the volatile memory (RAM) is fully cleared.
3. Plug the primary node back in and wait for the LED indicator to turn solid blue, indicating a full internet connection is established.
4. Once the primary node is stable, restart any secondary child nodes one by one.
5. Clear the app cache: On Android, go to Settings > Apps > Linksys > Storage > Clear Cache. On iOS, uninstall and reinstall the app to clear the local plist configuration files.
6. Log back into the app and navigate to Menu > Device Prioritization. Toggle the priority "Off" for all devices, wait 30 seconds, and then re-enable the priority for your target devices.
7. Navigate to Parental Controls, remove the existing profile for the problematic device, and recreate the profile from scratch to force a new rule set to be written to the router's NVRAM.

If That Didn't Work

• Perform a Manual Firmware Force: Access the Velop web interface by typing the IP address (usually 192.168.1.1) into a browser while connected to the network. Click the "CA" link in the bottom right corner of the login screen to enter the advanced settings. Check for firmware updates here; if the app says "Up to Date" but the web interface shows a pending version, install it manually to resolve API incompatibilities.
• Disable "Automatic Firmware Updates": In the app, go to Network Administration > Advanced Settings and disable automatic updates. Sometimes the system pushes a "beta" or "staged" firmware that breaks QoS features. After disabling, reboot the system again to see if it reverts to a stable state.
• Assign Static DHCP IPs: Parental controls often fail if a device changes its internal IP address via DHCP. In the web interface (under Connectivity > Local Network), assign a "Reserved IP" to the devices you wish to control. This ensures the router's MAC filtering and prioritization rules always hit the correct target.
• Hard Factory Reset: If the routing table is corrupted, press and hold the Reset button on the bottom of the primary node for 10-15 seconds until the light turns red. You will need to set up the network from scratch, but this wipes the corrupted configuration files that often persist through simple reboots.

Heads Up

• Avoid using third-party DNS providers (like OpenDNS or AdGuard) in conjunction with Linksys Parental Controls, as this can create conflicting rules that cause the "Pause" feature to fail intermittently.
• Device Prioritization significantly reduces the bandwidth available to "non-prioritized" devices; if you prioritize too many devices (more than 3-4), the QoS engine can crash, leading to the exact failure you are experiencing.
• Ensure your primary node is not placed directly on a metal surface, as this can cause intermittent packet loss that the app misinterprets as a device being "offline" or "paused."
• Regularly check that your mobile device is on the same subnet as the Velop nodes when making configuration changes to ensure the local API can verify the command before pushing it to the cloud.