đŸ§© How are you using Astrion Remote in your daily setup?

Astrion Astrion - Core Discussions
, ,
21

Hi @Skeltonmfc,

Thanks for sharing the screenshot — that makes things much clearer.

From what you describe, it looks like the issue isn’t with the Astrion Remote or RosCard itself, but with the Android TV / NVIDIA Shield integration. The NVIDIA Shield app (and the built-in Shield Pro remote) can launch apps and toggle power, but DPAD navigation won’t work if the app doesn’t expose the full remote control API or if certain features are disabled on your Shield firmware.

Here’s what I recommend:

  1. Check Entity Binding in RosCard:

    • For navigation buttons like DPAD_UP, DPAD_DOWN, etc., make sure you’re using the remote entity (e.g., remote.shield4k) and not the media_player entity.

    • In Home Assistant → Developer Tools → Services, test remote.send_command with remote.shield4k and DPAD_UP. If it works there, it should work in RosCard too.

  2. Firmware & App Updates:

    • Ensure both your Shield TV devices are running the latest firmware.

    • Update the NVIDIA Shield app you’re using to control the box, if applicable. Sometimes older versions limit DPAD access for third-party apps.

  3. Consider the Android TV Remote Integration:

    • The official Android TV Remote integration in Home Assistant is the most reliable for DPAD navigation. ADB commands like input keyevent sometimes work inconsistently on newer Shield firmware.

  4. Alternative Workaround:

    • Some users set up custom scripts in Home Assistant to send sequences of DPAD commands for navigation as a temporary fix.

    • If you’re using multiple Shield devices, make sure each one has a separate remote entity in HA to avoid command conflicts.

If you can share the exact entity you’ve bound in RosCard (remote vs media_player) and whether DPAD commands work via Developer Tools → Services, I can suggest a step-by-step setup to make DPAD navigation work on both Shield devices.

These setups can be tricky due to variations in Shield firmware and the Android TV Remote API, but once configured correctly, RosCard should handle navigation as expected.

22

Hi Charles,

Thanks for your support i have managed to get it working, not quite sure how, deleted some applications and clear some cache and the remotes started working. I have a final question what are the Physical Keys A,B,C in the TVRos card realting to ?

23

@Skeltonmfc Thank you for the feedback. I’m glad to know that works.

Not all TV remotes come with physical key shortcuts A, B, and C. However, you can use scripts bonding or other functions on your TV remote. Additionally, these keys are available on the number keypad in case your TV remote does not have them.