A Crestron system that drops touch screens or freezes DM NVX video almost never has a bad processor behind it — it usually has a UniFi network configured for a generic home instead of for Crestron. Crestron devices need their own VLAN, IGMPv2 or IGMPv3 snooping enabled on every switch and VLAN carrying them, exactly one IGMP querier on the network, and fast-leave turned on so multicast video stops cleanly when a display changes source. Get any one of those wrong and the symptoms look like a flaky processor: slow touch panel response, video that won't join a stream, or a control system that works for a few minutes and then stalls.
This matters more on UniFi than on some other platforms because several of UniFi's most convenient defaults are the exact settings Crestron's own documentation says to change. An integrator — or a well-meaning IT contractor — can leave a UniFi network looking perfectly healthy in the controller dashboard while Crestron underneath it behaves erratically.
Which VLAN should Crestron devices sit on?
Crestron's own network planning guidance is direct: control processors, touch screens, and DM NVX encoders/decoders should sit on a dedicated VLAN separate from general household or guest traffic, because "other network activity can impact the response time of Crestron devices and disrupt the user experience" (Plan a Network). Crestron's proprietary control communication relies on a heartbeat packet, and Crestron describes the platform as "very latency sensitive" — losing round-trip heartbeat packets is treated as an unreliable connection, not a cosmetic glitch.
On a UniFi network, that means a Crestron VLAN gets its own subnet, its own DHCP scope (Crestron recommends DHCP for devices on the control subnet, with static or reserved addressing favored for larger installs), and firewall rules that let it reach the services it needs — DNS, DHCP, and whichever VLAN carries AV sources — without exposing it to guest or IoT traffic. If DM NVX endpoints live on a separate segment from the control processor, Crestron's AV-over-IP guidance calls for that segment to still receive DNS, DHCP, and routing access, coordinated deliberately rather than left to UniFi's default inter-VLAN behavior (AV-over-IP Network Design).
This VLAN discipline is the same principle Cave Group applies across every estate network it designs — see why enterprise networking matters for the broader argument. For a Crestron-specific project, a networking upgrade is the point to settle VLAN layout, not something to retrofit after the system is live.
Why does DM NVX video need IGMP done exactly right?
DM NVX is multicast by design — even a single encoder feeding a single decoder depends on IGMP to work. Crestron's minimum network requirements for DM NVX switches are specific: nonblocking Layer 3 switching, IGMPv2 snooping, an IGMPv2 querier, and fast-leave (also called immediate leave) enabled (AV-over-IP Network Design). Without IGMP snooping, a switch that receives a multicast stream floods it to every port, saturating links and producing exactly the symptoms owners describe as "the TV just stopped working."
Crestron's IGMP snooping appendix adds the practical detail that matters most when configuring UniFi switches: snooping should be enabled both globally and per-VLAN for every VLAN carrying DM NVX traffic, the switch should be set to drop unknown multicast packets, and there should be only one IGMP querier active on the network — if more than one switch is configured as a querier, the one with the lowest IP address wins by default, which can silently hand querier duty to the wrong device (Appendix: IGMP Snooping). On a UniFi deployment with an Enterprise Fortress Gateway and multiple campus switches, that means picking one device — typically the gateway or core switch — to run the querier and verifying no other UniFi device has it also enabled.
Crestron also recommends setting the IGMP query interval to 60 or 125 seconds (the network switch's default is usually fine) and enabling fast-leave so a decoder dropping one multicast group doesn't wait out a long leave timer before the next stream joins cleanly.
What UniFi defaults should be checked before go-live?
Two Crestron-documented behaviors are worth checking against UniFi's defaults specifically:
- IGMP proxy on the control processor. Crestron's AV-over-IP design guidance says IGMP proxy functionality should be disabled on control processors with routing enabled (Crestron names the CP3N, PRO3, AV3, and DMPS3 as processors where this applies) "to ensure that DM NVX multicast traffic does not interfere with the control processor." If a Crestron processor's router-mode IGMP proxy is left on, it competes with the UniFi switch's own IGMP handling, producing inconsistent multicast behavior.
- Multiple IGMP queriers. UniFi gateways and switches can each independently offer IGMP querier functionality. Crestron is explicit that good network performance depends on exactly one querier existing on the network — confirm querier is enabled on only one UniFi device, not left on by default across several.
Crestron's broader design considerations also call for Rapid Spanning Tree Protocol to keep network loops discoverable, nonblocking switch fabric sized for the number of DM NVX endpoints, and 802.1Q/802.1P QoS tagging to prioritize DM NVX and IGMP traffic over lower-priority web or SSH traffic — all things a UniFi campus switch deployment should be configured for explicitly rather than assumed.
What should a post-change verification checklist include?
Any time VLANs, firmware, or switch configuration change on a network carrying Crestron, the integrator should re-verify: that IGMP snooping and the single querier are still active on every Crestron and DM NVX VLAN, that fast-leave is still enabled, that the control processor's IGMP proxy setting hasn't reset after a firmware update, and that touch panels and DM NVX endpoints rejoin their multicast streams cleanly after an AP reboot or switch failover. This is a short list to document once and recheck after every network change — not a one-time install step.
Frequently asked questions
Does Crestron really need its own VLAN?
Crestron's own network planning documentation recommends a dedicated Crestron-only VLAN because other network traffic can interfere with the heartbeat packets that control processors and touch screens depend on for reliable response.
What is an IGMP querier and why can only one exist?
An IGMP querier is the network device that tracks which ports have multicast senders and receivers. Crestron's documentation notes that if multiple switches are configured as queriers, the one with the lowest IP address becomes the default — so an unintentional second querier can quietly take over and cause inconsistent DM NVX behavior.
What is fast-leave and why does DM NVX need it?
Fast-leave (immediate leave) lets a switch stop forwarding a multicast stream to a port as soon as a device leaves that group, rather than waiting out the full leave timer. Crestron lists fast-leave as a minimum network requirement for DM NVX switches.
Can IGMP proxy on a Crestron processor cause problems?
Yes — Crestron's AV-over-IP design guidance specifically recommends disabling IGMP proxy functionality on routing-enabled control processors like the CP3N, PRO3, AV3, and DMPS3 so it doesn't interfere with DM NVX multicast traffic.
Who should configure these settings — the AV integrator or the IT contractor?
Because the settings span both the Crestron program side and the switch/VLAN configuration side, they work best when one team owns both, or when the two teams coordinate explicitly before go-live rather than assuming the other has handled it. Cave Group designs around this by owning both the Crestron programming and the UniFi network configuration on a given project.