Use the receiver for audio without losing TV navigation
Many media systems split responsibility across several devices. The display handles navigation, the AV receiver or soundbar owns volume and inputs, and a streamer owns playback. Treating all three as one generic media player often produces the wrong command path.
Assign the Audio Target deliberately
Choose the Home Assistant entity that actually controls the sound as the Audio Target. Tactra can then send volume and mute there while the Remote Target continues to receive directional navigation and the Playback Target receives transport commands.
This is especially useful when HDMI-CEC exposes overlapping controls. Explicit roles make the intended route visible rather than relying on whichever entity happens to react.
Keep source and power capability-driven
Tactra presents source and power controls according to the capabilities and actions available for the selected setup. Test the source or service in Home Assistant first. If startup requires Wake-on-LAN or several ordered actions, configure that behavior as Media Setup power actions or in a Home Assistant scene or script. Activities run presets; they do not sequence a setup’s power actions.
If Home Assistant already owns a reliable startup sequence, let Tactra launch that scene or script. The remote should stay a thin control surface over the working automation.
Frequently asked questions
Why should an AV receiver be the Audio Target?
If the receiver or soundbar produces the sound, assigning it as Audio Target sends volume and mute to the correct Home Assistant entity.
Can the TV remain the Remote Target?
Yes. TV navigation and receiver audio can belong to different roles in the same Media Setup.
What should I check when source selection fails?
Verify that the selected Home Assistant entity reports source capability and that the desired source appears and works in Home Assistant.
For the complete setup model, read the Home Assistant TV remote guide.