RosCard TV Card Guide

Overview

The RosCard TV Card provides a dedicated interface for controlling television and media player devices from your Astrion Remote. It supports multiple device types including Android TV, Apple TV, and generic media players, with full button mapping and script binding capabilities.

The TV Card is designed to work alongside Home Assistant scripts to create Harmony-style activities — where a single button press can trigger a sequence of actions across multiple devices.

💡 Tip: The TV Card supports script binding for buttons like POWER, Volume, and Navigation[reference:2]. Use this to route volume control to an AVR while navigation controls stay with the TV — perfect for complex home theater setups.

Features

Step-by-Step Configuration

YAML Reference

Full Parameter List

TV Types

• android_tv — Android TV devices (NVIDIA Shield, Sony, etc.)
• apple_tv — Apple TV devices

Button Keys

• POWER — Power toggle
• VOLUME_UP / VOLUME_DOWN — Volume control
• CHANNEL_UP / CHANNEL_DOWN — Channel control
• NAVIGATION — Directional pad (UP, DOWN, LEFT, RIGHT, OK)
• BACK / HOME — System navigation
• NUMBER_0 through NUMBER_9 — Numeric input

Button Action Types

• remote — Send a command to a Home Assistant remote entity
• script — Trigger a Home Assistant script[reference:5]

Activity-Based Workflows

The TV Card is designed to support Harmony-style activity workflows using Home Assistant scripts. This approach gives you significantly more flexibility than traditional harmony remotes[reference:6].

Typical Activity Flow

• Turn on TV — Send POWER command via remote entity or IR
• Turn on AVR — Send POWER command via remote entity or IR
• Select source — Switch TV input or AVR source
• Route volume control — Map volume buttons to AVR instead of TV
• Update remote context — Change button mappings based on active activity

Example: Movie Night Script

Troubleshooting

TV Card Not Showing on Astrion Remote

• Refresh the remote: Pull down from the top of the home screen and tap Refresh.
• Verify entity exists: Make sure the media player or remote entity is available in Home Assistant.
• Check YAML format: Ensure your configuration uses the correct syntax and indentation.
• Update RosCard: If you're running an older version, update RosCard via HACS.

Button Controls Not Responding

• Check entity status: Verify the remote or media player entity is available in Home Assistant.
• Test in Home Assistant: Try sending the command directly from the Home Assistant UI to rule out connection issues.
• Verify script exists: If using script binding, ensure the script ID is correct and the script is enabled.
• Check command values: Verify the command value matches what the remote entity expects (e.g., "POWER" vs "power").

Volume Control Not Working as Expected

• If volume buttons are controlling the wrong device, check that the entity_id in the button mapping points to the correct remote entity.
• For activity-based setups, ensure your script handles volume routing correctly.
• Some Android TV devices may require specific volume commands — check your device's documentation.

Script Not Triggering

• Verify the script exists in Home Assistant and is enabled.
• Check that the entity_id in the button mapping matches the script's entity_id.
• Test the script directly from Home Assistant to ensure it works.
• Check the script's mode — if it's single, it won't trigger while already running.