📘 RosCard for Home Assistant

Astrion Astrion - Development & Advanced
1

:blue_book: RosCard for Home Assistant

Complete Technical Documentation (v2.0.0)

Product: Astrion Remote HA100
Last Updated: December 5, 2025
Maintained by: Sanytron Technology

:pushpin: About This Document

This post is the official technical reference for RosCard, the custom Home Assistant card system designed for Astrion Remote.

RosCard acts as the communication bridge between Astrion hardware and Home Assistant, enabling:

  • Real-time control

  • Optimized UI rendering

  • Physical button integration

  • Secure local communication

:warning: This document is intended for advanced users, integrators, and developers.

:locked_with_key: Copyright & Disclaimer

© 2025 Sanytron Technology. All rights reserved.
This document contains proprietary information. Specifications may change without notice.

  • Home Assistant is a trademark of the Home Assistant project

  • All other trademarks belong to their respective owners

:books: Table of Contents

  1. Introduction to RosCard

  2. System Architecture

  3. Installation Guide

  4. Configuration & Setup

  5. Card Types & Features

  6. API Integration Details

  7. Troubleshooting

  8. Advanced Features

  9. FAQ

  10. Support & Resources

  11. Version History

:one: Introduction to RosCard

1.1 What is RosCard?

RosCard is a custom Home Assistant card package built specifically for the Astrion Remote HA100.

Without RosCard:

  • Astrion cannot communicate with Home Assistant

  • No entity control or status sync is possible

RosCard translates HA states and services into a UI optimized for Astrion’s 3.1" touchscreen and physical buttons.

1.2 Key Principles

  • :link: API-Based Communication (HA WebSocket API)

  • :high_voltage: Real-Time State Synchronization

  • :locked_with_key: Secure Token-Based Authentication

  • :desktop_computer: Astrion-Optimized UI Rendering

  • :control_knobs: Physical Button Mapping Support

1.3 System Requirements

Component Minimum Recommended
Home Assistant Core 2023.1+ 2024.1+
HACS 1.30.0+ Latest
Network Local Wi-Fi 5GHz
Astrion Remote FW 1.0+ FW 1.2+

:two: System Architecture

2.1 Communication Flow

Astrion Remote  ⇄  WebSocket API  ⇄  Home Assistant + RosCard

  • Astrion handles UI & hardware input

  • RosCard handles HA communication & data formatting

  • HA remains the single source of truth

2.2 Data Flow Example

  1. Astrion requests entity state

  2. RosCard queries HA WebSocket

  3. HA returns entity data

  4. RosCard optimizes data for display

  5. Astrion renders UI

2.3 Security Model

Feature Implementation
Authentication Long-lived HA tokens
Data Storage No HA data stored on remote
Network Local WebSocket
Token Control Revocable via HA
Encryption HTTPS / Secure WS

:three: Installation Guide

3.1 Prerequisites

  • Home Assistant running

  • HACS installed

  • Astrion on same network

  • Network discovery enabled

3.2 Installation Steps (HACS)

Step 1 – Add Repository

HACS → Integrations → Custom Repositories
URL: https://github.com/yyqclhy/RosCard
Category: Dashboard

Step 2 – Install RosCard

Search "RosCard" → Download → Restart HA

Step 3 – Create Access Token

Profile → Security → Long-lived Tokens
Name: Astrion Remote

Step 4 – Generate QR Code

http://HA_IP:8123?token=YOUR_TOKEN

:four: Configuration & Setup

4.1 Astrion Remote Connection

  • Settings → Home Assistant → Scan QR Code

  • Manual setup supported if needed

4.2 Creating RosCard Views

  • Edit Dashboard → Add Card

  • Select Custom: RosCard

  • Enable Independent Display for full-screen use

4.3 Physical Button Mapping

Path:
Remote Settings → Shortcut Configuration

Supported actions:

  • Light / Climate control

  • Media playback

  • Scene activation

  • Custom HA service calls

:five: Card Types & Features

Climate Card

  • Temperature presets

  • Mode selection

  • Fan & swing control

  • Real-time feedback

Light Card

  • Brightness (0–100%)

  • Color temp / RGB

  • Group & scene support

Media Card

  • Android TV / Apple TV

  • Playback & navigation

  • Custom key mapping

Supported Card Summary

Card Purpose
Climate AC & heating
Light Dimming & color
Switch Power control
Cover Curtains & blinds
Scene Automation
Media AV control
Weather Forecast
Host System actions

:six: API Integration

6.1 WebSocket API

RosCard uses HA’s official WebSocket API for:

  • State subscriptions

  • Event handling

  • Service execution

6.2 Performance Optimization

  • Lazy loading

  • Delta updates

  • Data compression

  • Cached UI assets

  • Batched requests

6.3 Service Call Mapping

RosCard converts Astrion actions into standard HA service calls
(e.g. light.toggle, climate.set_temperature).

:seven: Troubleshooting

Common Issues

Issue Cause Solution
No connection Network Re-scan QR
No response Entity mapping Rebind
Slow UI Network Use 5GHz
Device missing Discovery Restart HA

Reset Options

  • Soft Reset: Restart remote

  • Hard Reset: Factory reset

  • RosCard Reset: Reinstall via HACS

:eight: Advanced Features

Custom Icons

Path:
/local/community/RosCard/icon_img/

Formats:

  • PNG (recommended)

  • SVG

  • JPG

Templates & Automations

RosCard supports:

  • HA templates

  • Button-triggered automations

  • Multi-user dashboards

  • Per-user access tokens

:nine: FAQ (Short Version)

  • Why RosCard? → Required communication layer

  • Multiple remotes? → Yes, one token per device

  • Remote lost? → Revoke token

  • Remote-only use? → Works as Lovelace cards too

:link: 1​:zero: Support & Resources

Official

Community

  • GitHub: RosCard Repository

  • Facebook: Astrion Remote Users

:four_o_clock: Document Version History

Version Date Notes
1.0.0 Nov 2025 Initial
1.1.0 Dec 2025 Troubleshooting
2.0.0 Dec 2025 Full documentation

:inbox_tray: Downloads

Always refer to this forum post or the official portal for the latest updates.

5

Can you add some details on HA Templates and Button-triggered automations please.

6

Hi @peteS-UK, great question.

HA Templates

RosCard supports Home Assistant templates, because templates are evaluated by HA itself.
Astrion simply displays and controls the resulting entities.

Common uses:

  • Conditional entities
  • Time-based behavior
  • State-dependent controls

Button-triggered automations

Physical buttons on Astrion can trigger:

  • Scenes
  • Scripts
  • Automations
  • Custom HA service calls

Typical flow:
Astrion button → HA event/service → HA automation logic

7

yes but how to configure buttons?

8

you can bond with the shortcuts in the remote

9

Just those that are configurable?

Not cursor, home etc?

Currently they are hard bundled to android / apple.

I need them to control for example my amplifier’s volume

10

Hi Nicola, welcome again — great question.

At the moment, not all physical buttons are fully user-configurable yet. Some keys — such as cursor navigation, Home, and certain system-level buttons — are currently mapped at the system layer (Android / OS level), which is why they behave as fixed keys rather than user-assignable ones.

Right now, the buttons that can be configured are mainly those exposed through the shortcut / custom binding layer, which allows you to map them to Home Assistant entities, scripts, scenes, or service calls.

That said, what you’re describing — for example using directional or system buttons to control an amplifier’s volume — is exactly the type of advanced customization we want to support more broadly. Expanding full key remapping capability, including system buttons, is already under evaluation for future firmware updates.

For the time being, advanced users sometimes implement logic through HA itself (for example using scripts or input helpers as routing layers), but we agree that native remapping will be a much cleaner solution and that’s the direction we’re working toward.

We really appreciate you raising this, because requests like yours help us prioritize which control features to unlock next.

11

We are looking for a way to map the Volume +/= Mute/Unmute buttons to a separate entity, or have the ability to discrete program them to send REST commands to another entity. We have a system with many Android TV devices where the master volume is controlled by an audio DSP. We want to map the shortcut buttons to act as a zone select and have the volume controls follow that.

We are also dealing with problems getting the Android TV D pad buttons, back, home etc to work with the standard Media Player/Remote entity assignments in Roscard.

12

Hi @Gabe_Gonzalez, welcome to the community — and thanks for the detailed explanation of your setup :+1:

Your use case with multiple Android TV devices and a central audio DSP controlling the master volume is very interesting and actually aligns well with the type of flexibility we want Astrion to support.

Volume and navigation button mapping

With the latest RosCard v1.1.1, you can now select different entities or scripts for several buttons, including:

  • Up / Down / Left / Right

  • Volume + / Volume −

  • Mute

  • other commonly used control buttons

This means you can bind those buttons directly to Home Assistant entities or scripts, which should allow you to route volume commands to your DSP instead of the Android TV device.

For example, the Volume + / − buttons could call a Home Assistant script or service that adjusts the volume of your DSP zone rather than the TV.

Custom entity buttons

Regarding the eight custom entity buttons, these currently support entity actions, and in upcoming versions we also plan to allow direct script binding to those buttons. This will make it easier to implement workflows such as:

  • selecting an audio zone

  • launching automations

  • triggering custom REST/service commands

Android TV navigation behavior

For the D-pad, Back, Home, etc., behavior can depend on which Android TV integration you are using in Home Assistant (Android TV Remote vs ADB integration). In many cases RosCard works best when the commands are bound either to the remote entity or to scripts that wrap the integration service calls.

If you’d like, feel free to share which Android TV integration and entity type you are using, and we can help verify the most reliable configuration.

Thanks again for sharing your scenario — setups like yours are very helpful for guiding how we expand Astrion’s control flexibility in future updates. :rocket:

13

Hi! Are you planning to implement full, dedicated support for Music Assistant in RosCard? As MA is becoming increasingly powerful and popular, a dedicated card (similar to the current Media card but optimized for MA features) would be a great addition for Astrion users.

I’ve just ordered the Astrion remote from you and can’t wait to test it out. It would be awesome to see full MA integration in the near future!

2 Likes
14

Agree, would be ideal.

1 Like
15

Hi Robert_P :waving_hand: and Chykan_Hunter :waving_hand:

First of all, welcome Robert — and thanks for the order, really appreciate the support :raising_hands:

This is a very good suggestion, and also one we’ve been paying close attention to.

:musical_note: Music Assistant support (ROS Card direction)

Yes — we are actively looking at deeper integration with Music Assistant inside the ROS Card ecosystem.

Right now, Astrion can already work with MA indirectly via Home Assistant media entities, but we fully agree that this is not the same as a dedicated, optimized experience.

:compass: What “dedicated support” would mean

What you’re describing is essentially:

  • browsing MA sources (libraries, playlists, providers)

  • proper queue + playback control

  • richer metadata (artwork, artists, albums)

  • fast navigation optimized for remote control

  • seamless integration with HA media state

That is very aligned with our thinking for a future “Music / Media Experience layer” inside ROS Card, rather than treating MA as just another generic media_player.

:gear: Current reality (important)

Today:

  • MA works through standard HA media_player abstraction

  • so functionality is already possible, but limited to generic controls

What’s missing is:
:backhand_index_pointing_right: MA-aware UI logic inside the card system

:rocket: Direction we’re heading

We are evaluating a dedicated media experience layer that would:

  • better understand MA structures

  • reduce navigation depth

  • expose “music-first” UI instead of generic media controls

This would likely evolve as:

  • enhanced Media Card first

  • then optional MA-optimized mode inside it (or separate card profile)

:+1: Final note

This is definitely not just a “nice-to-have” request — Music Assistant is becoming a core part of advanced HA media setups, and we agree it deserves better native treatment than generic media control.

We’ll keep you updated as this evolves, and your feedback here is going straight into the prioritisation discussion :+1:

1 Like
16

And that emphasizes everything. :slightly_smiling_face:

17

Hi team,
Do you have a roadmap of expected features?
Love the product but worried about development cycle and intended capabilities being delayed that will improve user experience.
How often are you expecting to release updates

2 Likes
18

Hi Joshua :waving_hand:
Welcome to the community — and thank you for the kind words about Astrion, we really appreciate it.

This is a very fair question, especially for a platform that is evolving as actively as Astrion + ROSCard.

:compass: About Roadmaps

We intentionally don’t publish a rigid long-term feature roadmap with dates.

The reason is simple:

Astrion is not developing like a traditional fixed-feature consumer remote.
It is evolving together with Home Assistant, Music Assistant, and the broader automation ecosystem — which itself moves very quickly.

Instead of committing to distant timelines that may change, we focus on:

  • shipping improvements continuously

  • prioritizing real user workflows from this community

  • refining interaction design based on actual usage

Many of the features now in Astrion came directly from forum discussions like this one.

:rocket: Development Direction (High Level)

Without giving exact dates, the main areas currently receiving active attention are:

:white_check_mark: Stability & connection reliability
:white_check_mark: Faster HA communication layer
:white_check_mark: Expanded hardware button behavior
:white_check_mark: Media experience improvements (including Music Assistant direction)
:white_check_mark: Better activity / workflow navigation between cards
:white_check_mark: UI usability improvements and customization

You’ll notice a common theme:
making the remote feel more natural and less configuration-heavy over time.

:counterclockwise_arrows_button: Update Frequency

Our general approach is:

  • Regular firmware + ROSCard updates rather than large infrequent releases

  • Smaller iterations released once they are stable

  • Continuous refinement instead of waiting for “big version jumps”

In practice, users typically see meaningful updates every few weeks, with larger capability expansions appearing periodically as systems mature.

:speech_balloon: Transparency Note

Astrion is a young platform, and we try to be honest about that.

Some capabilities are still evolving — but development is very active, and community feedback directly influences what comes next. Posts like yours genuinely help guide priorities.

Thanks again for joining us, and please keep sharing your experience as you explore the system :+1:

1 Like
19

Does anyone have news and when a new update is going to be released, been waiting a bit

20

I would appreciate non ai generated answers

1 Like