HEDD CTRL may fail to detect a speaker in deep sleep because its network chip can remain inactive. A white status light means standby; green means active, so check the cabinet before changing anything on your computer. If it stays asleep, stop playback, switch its power off and back on, then try connecting again.
Your browser can work perfectly while CTRL shows an empty device list. Being online doesn't prove the application can reach your speakers. Note whether a speaker is missing entirely or listed but ignoring commands.
Some docks restrict the network access CTRL needs, even when you can still browse the web. Try a USB-to-Ethernet adapter connected directly to the computer, keeping the same cable and switch port where possible.
Once the speakers appear, reconnect through the dock and repeat the test. A failure that returns with the dock gives you a reason to investigate that connection before replacing the speaker.
The computer and speakers need addresses in the same subnet. Sharing a managed switch is not enough. Its ports can belong to different virtual networks, so have whoever configured it check their assignments.
When a speaker is listed but ignores adjustments, check its firmware compatibility with the installed CTRL version. Seeing its name tells you discovery has worked at least once; permissions or firmware can still prevent control.
The firewall controls are under System Settings, Network, Firewall, then Options. When the firewall is on, check whether CTRL can receive incoming connections rather than assuming Local Network permission covers both. Also check whether Block all incoming connections is enabled.
If you previously denied the local-network request, check that setting before reinstalling CTRL. There's no need to leave the firewall off while you sort out the app's access.
On Windows, open Windows Security and check Firewall & network protection before adding an exception for CTRL. Check the active network profile, too, because private and public networks can have different firewall rules.
Windows also offers a setting that blocks all incoming connections, including those from allowed apps. A checked box there overrides your exception. Adding CTRL again will not resolve the restriction.
Use an app-specific allowance instead of opening ports guessed from someone else's audio setup. An open port stays open until you close it, while an allowed app opens the required ports only when needed. Less exposure, without disabling the whole firewall.
A company-managed computer may prevent you from changing these settings at all. Give the administrator the application name and the network you are using, rather than requesting that they disable protection.
On a network carrying substantial multicast Dante audio, snooping prevents that traffic from reaching every switch port unnecessarily. Disabling it across the switch can waste bandwidth and increase the load on devices that never requested those streams.
A mostly unicast Dante setup has different needs from a network carrying many multicast flows. Multicast sends traffic to a group of receivers, while unicast addresses one receiver. Advice for a small, dedicated audio network won't necessarily suit a shared studio installation.
Use a separate test network with your computer and HEDD speakers connected through a simple switch. Keep them on the same subnet, using a router for automatic addressing or valid static addresses, and disconnect the shared studio network.
Success on the separate network narrows your investigation to differences in the original setup. It does not identify a particular switch feature, because moving the equipment changed several parts of the connection at once.
A NETGEAR M4300 carrying multicast Dante, for example, needs IGMP snooping enabled under its documented configuration. Its querier checks multicast group membership, so the switch knows which devices need those streams. Disabling snooping may restore one control connection while sending unwanted multicast traffic to other devices.
Your browser can work perfectly while CTRL shows an empty device list. Being online doesn't prove the application can reach your speakers. Note whether a speaker is missing entirely or listed but ignoring commands.
A live Ethernet port can still leave speakers missing
Check for activity at the Ethernet ports on the monitor, switch, and computer connection. A missing link light makes the cable, port, or adapter worth testing before you reinstall anything. If only one monitor is missing, try a known working cable without changing other settings.Some docks restrict the network access CTRL needs, even when you can still browse the web. Try a USB-to-Ethernet adapter connected directly to the computer, keeping the same cable and switch port where possible.
Once the speakers appear, reconnect through the dock and repeat the test. A failure that returns with the dock gives you a reason to investigate that connection before replacing the speaker.
The computer and speakers need addresses in the same subnet. Sharing a managed switch is not enough. Its ports can belong to different virtual networks, so have whoever configured it check their assignments.
When a speaker is listed but ignores adjustments, check its firmware compatibility with the installed CTRL version. Seeing its name tells you discovery has worked at least once; permissions or firmware can still prevent control.
Your firewall is not the only permission check
On a Mac, permission to reach nearby equipment sits in Local Network under System Settings, then Privacy & Security. Find HEDD CTRL there and enable its access if it is switched off. This permission is separate from the firewall.The firewall controls are under System Settings, Network, Firewall, then Options. When the firewall is on, check whether CTRL can receive incoming connections rather than assuming Local Network permission covers both. Also check whether Block all incoming connections is enabled.
If you previously denied the local-network request, check that setting before reinstalling CTRL. There's no need to leave the firewall off while you sort out the app's access.
On Windows, open Windows Security and check Firewall & network protection before adding an exception for CTRL. Check the active network profile, too, because private and public networks can have different firewall rules.
Windows also offers a setting that blocks all incoming connections, including those from allowed apps. A checked box there overrides your exception. Adding CTRL again will not resolve the restriction.
Use an app-specific allowance instead of opening ports guessed from someone else's audio setup. An open port stays open until you close it, while an allowed app opens the required ports only when needed. Less exposure, without disabling the whole firewall.
A company-managed computer may prevent you from changing these settings at all. Give the administrator the application name and the network you are using, rather than requesting that they disable protection.
A shared audio switch needs a narrower fix
IGMP snooping manages where multicast traffic goes, so changing it can affect more than the missing speakers. The connection fixes in HEDD CTRL 2.0.1 improve the application's handling of it, but do not make every switch configuration suitable.On a network carrying substantial multicast Dante audio, snooping prevents that traffic from reaching every switch port unnecessarily. Disabling it across the switch can waste bandwidth and increase the load on devices that never requested those streams.
A mostly unicast Dante setup has different needs from a network carrying many multicast flows. Multicast sends traffic to a group of receivers, while unicast addresses one receiver. Advice for a small, dedicated audio network won't necessarily suit a shared studio installation.
Use a separate test network with your computer and HEDD speakers connected through a simple switch. Keep them on the same subnet, using a router for automatic addressing or valid static addresses, and disconnect the shared studio network.
Success on the separate network narrows your investigation to differences in the original setup. It does not identify a particular switch feature, because moving the equipment changed several parts of the connection at once.
A NETGEAR M4300 carrying multicast Dante, for example, needs IGMP snooping enabled under its documented configuration. Its querier checks multicast group membership, so the switch knows which devices need those streams. Disabling snooping may restore one control connection while sending unwanted multicast traffic to other devices.
