Key takeaways
- HDMI-CEC is one standard marketed under different names, Anynet Plus on Samsung, SimpLink on LG, and Bravia Sync on Sony, and each device in the chain needs it enabled separately.
- Enabling CEC in the order TV first, then soundbar, then any source device avoids most of the conflicts that appear when several devices negotiate control at once.
- Power on and off cascading between devices is the most reliable CEC function. Play, pause, and rewind passing through a single remote is far less consistently supported across brands.
- A TV turning off a games console unexpectedly is usually a CEC power cascade setting, not a fault, and it can often be disabled on its own without losing other CEC functions.
- Two devices both trying to control the same input switching is the most common cause of CEC behaving worse after a third device joins the chain.
Three remotes are lined up on the coffee table, and starting a film means picking up the TV remote to turn everything on, the soundbar remote to check the volume actually came through, and then hunting under a cushion for the console’s own remote just to press play.
HDMI-CEC exists inside almost every TV, soundbar, and games console sold in the last decade specifically to remove that ritual. It rarely arrives switched on everywhere it needs to be, which is why the coffee table still has three remotes on it.
Setting it up properly takes about fifteen minutes across a typical three device setup: TV, soundbar, and one source. This walkthrough covers each device in the order that avoids the most common conflicts, what to test once it is done, and what to do when two devices end up arguing over who is in charge.
What each brand calls this feature
HDMI-CEC is a single standard, but no manufacturer sells it under that name. Samsung calls it Anynet Plus, LG calls it SimpLink, Sony calls it Bravia Sync or Control for HDMI, and Panasonic calls it VIERA Link. Underneath, all five are the same protocol defined as part of the HDMI specification.
That naming difference is the first thing that trips people up when a TV and a soundbar come from different brands. Enabling Anynet Plus on a Samsung TV does nothing by itself if the soundbar attached to it is an LG model expecting SimpLink to be found and never told to look for it under a different name.
The HDMI Licensing Administrator’s own resources confirm the underlying protocol is identical regardless of brand, which is useful to know before assuming a mismatch is a compatibility fault rather than a naming one.
Philips uses EasyLink, and a handful of smaller brands license the standard without giving it any distinct marketing name at all, simply calling it HDMI control or CEC directly in the settings menu. If the exact wording on a specific remote or menu does not match any brand name above, searching the TV’s own model number alongside the word CEC usually turns up the right setting within a minute.
Turning CEC on for every device in the chain
Start with the TV. The setting usually sits under General or External Device Manager in the main settings menu, labelled with whichever brand name applies, and it needs to be switched on before anything downstream will respond to it.
Move to the soundbar next. A Samsung HW-Q990D or Sonos Arc Ultra typically ships with CEC support enabled by default, but it still depends on the TV’s own setting being active first, so enabling both in sequence rather than assuming one implies the other matters here.
Power cycle the TV after enabling CEC, before moving on to the soundbar. Several models only fully register the change after a restart, and skipping that step is a common reason the very next device in the chain seems not to respond.
Finally, check any source device plugged directly into the TV or the soundbar: a games console, a streaming stick, or a 4K Blu-ray player. Consoles often bury the setting under power or HDMI options with their own wording, separate from the audio and video settings entirely.
A streaming stick plugged directly into the TV rather than the soundbar is worth checking too, since it counts as a device in the chain even though it never touches the soundbar’s own ports. Leaving its CEC setting off is a common reason one specific app behaves differently to the rest.
Testing which remote functions actually transferred
Power on and off cascading is the most reliably supported function across brands. Turning on the TV should wake the soundbar automatically, and turning off the TV should put the soundbar to standby within a few seconds without touching its remote at all.
Volume control usually transfers well too, since it is a simple command with little room for brands to interpret differently. Playback functions, play, pause, rewind, sent from a universal remote through the TV toward a source device are supported far less consistently, and some combinations of brands never pass them through at all.
| Function | Typical reliability |
|---|---|
| Power on and off cascade | High, works across most brand combinations |
| Volume control | High, one of the most consistent CEC functions |
| Input switching to the active source | Moderate, occasionally needs a manual nudge |
| Playback control, play, pause, rewind | Low, inconsistent across mixed brand setups |
Knowing which row of that table matters to your own routine sets realistic expectations before assuming a setup has failed. For a related connection issue that can masquerade as a CEC fault, see clearing an HDMI handshake problem.
Confirming one remote is genuinely in control
Test the chain in the actual order a movie night uses it. Turn the TV on with its remote alone and watch whether the soundbar wakes on its own within a few seconds. Then adjust volume from the TV remote and confirm the soundbar’s own display changes to match.
If everything above works, treat playback control passthrough as a bonus rather than an expectation. A soundbar and console combination that handles power and volume but still needs its own remote for play and pause is working exactly as most CEC implementations are actually built, not malfunctioning.
- CEC enabled on the TV, then power cycled
- CEC enabled on the soundbar, using the correct brand name for the setting
- CEC enabled on any source device plugged into the chain
- Power, volume, and input switching tested in the order a real movie night uses them
When two devices fight over control
The most common complaint after adding a third device, typically a games console, is a TV that will not stay off, or a soundbar that powers down and immediately back up. This is usually two devices both trying to act as the CEC controller for the same input at once.
The fix is rarely disabling CEC altogether, which throws away the convenience along with the fault. Most TVs let you disable the power off cascade specifically while keeping volume and input switching active, which resolves the loop without losing everything CEC was set up for.
A home theater room I fitted last year had exactly this fault: turning off the TV woke the games console from standby, which then re-woke the soundbar a few seconds later, in an endless loop. Disabling the console’s own CEC power features, while leaving the TV and soundbar’s settings untouched, broke the cycle completely.
Where the fault sits somewhere between CEC and the underlying HDMI connection rather than CEC specifically, the first port of call should be the basics covered in which HDMI port to use for your soundbar, since a marginal connection can produce symptoms that look exactly like a CEC conflict. If the remote itself has stopped responding altogether rather than the devices ignoring valid commands, that is a separate and more specific problem covered in when the soundbar remote stops working.
Getting CEC working across three devices from three different manufacturers takes fifteen minutes done in the right order. Done in the wrong order, the same three devices can spend an evening fighting each other over which one gets to be in charge.
A games console added later, through connecting a game console through a soundbar, is the single most common trigger for a CEC setup that worked fine for months to suddenly need revisiting.
Questions readers ask about this
Generally yes, since all brands implement the same underlying HDMI-CEC standard regardless of what they call it. Bravia Sync on the Sony side and Anynet Plus on the Samsung side both need enabling independently, and mixed brand chains occasionally support fewer functions than a single brand setup, particularly for playback control.
This is CEC's power cascade function working as designed, not a fault, though it is not always wanted. Most consoles and TVs let this specific behaviour be disabled separately from other CEC functions, usually under a power or standby related setting rather than the main CEC toggle itself.
On most modern TVs and soundbars, yes. Volume and power cascading are usually controlled by separate settings, even though both fall under the same overall CEC toggle in the main menu. Checking the advanced or expert settings usually reveals the finer grained option.
The difference is small, generally under 1 watt of additional draw while devices remain ready to receive a wake signal over HDMI. It is not a meaningful cost concern compared with the convenience CEC provides across a typical home theater setup.
This usually means CEC is enabled on the soundbar but not on the TV, or the two devices are using different terms for the same feature and one has been left off. Confirm both settings independently rather than assuming enabling one side covers the other.
About the author
Rahul Gupta
Rahul Gupta has spent nearly a decade quietly wiring living rooms, testing soundbars in every awkward apartment layout imaginable, and untangling the kind of HDMI handshake problems that make people give up on Atmos altogether. He writes here about what actually works when you get the boxes home—not what the spec sheet promises. If a piece of gear on this site earns a recommendation, it earned it in a real room with real furniture, not a lab.
