Hi,
looking for help with these quesions:
Thanks
Hi starob,
Great questions — welcome! I’ll go through each one step by step so you have a clear overview of how things work today and what options you have.
You can bind a physical button through the Shortcut / Button Binding settings:
Typical flow
Remote button → Shortcut binding → HA entity/service → Script executes
To do this:
Create your script in Home Assistant
Expose it as an entity/service
Assign it to a shortcut/button action in the remote configuration
Once linked, pressing that button triggers the script instantly.
Currently, RosCard layouts are primarily vertical-stack oriented for readability and touch usability on the remote screen.
At the moment:
True horizontal card stacking is not yet a native layout option
Layout customization is somewhat constrained by screen scaling and UI density optimization
That said, more flexible layout systems (including multi-column/grid-style arrangements) are under evaluation for future versions because many advanced users have requested this.
A Host Control Card is designed to control a parent or host device/service rather than a simple entity.
Typical use cases:
System-level commands
Mode switching
Master device state control
Triggering higher-level automation logic
Think of it as a controller for logic layers, not just a single device.
A Monitor Card is mainly for displaying status information rather than controlling devices.
Examples:
Sensor values
System stats
Status indicators
Read-only data feeds
It’s useful for dashboards where you want quick system visibility without interaction.
You’re correct — the volume step size comes from the underlying media entity’s configured step value.
Possible solutions:
Adjust the volume step in the Home Assistant integration (if supported)
Wrap volume commands inside a script and bind buttons to that script with custom step logic
Use repeated small-step service calls instead of default volume_up/down
Native adjustment for volume increment size directly on the remote side is a reasonable request and something we’re considering adding as a configurable parameter.
RosCard currently supports nine control categories (lighting, climate, curtains, media, scenes, statistics, etc.), so depending on your use case you may find a built-in card that already fits your workflow. Our knowledge section posts, manuals, and tutorial videos include configuration examples that can be very helpful when setting up advanced layouts or logic chains.
Thank you Charles. How do I expose a scripts so that I can link it to a button in the remote? I don’t see any of my scripts listed as options to create such a link.
The software shown in the video seems to support swiping sceens. Mine does not. Is this a newer version? What are the latest software versions?
I have:
No updates are offered at the moment for my device.
Thanks.
Hi Charles,
still struggling with the Host control card. I can only select “remote” entities in the UI but the card does not show on the Astrion. I can link it to a button though but it doesn’t do anything.
please forget the host card since it require the AIKS or Link-On AV controller for test, we will develop this card for new application
Hi @starob
As a test for the host card the remote entities dont show up for me either however if i manually add switch entities it does show up and work. The host card is filtered to remote entities.
What I also noticed with the host card is somethimes it does not sync correctly. To fix this i had to rearrange the cards in the UI and sync again and it showed up.
type: custom:aiks-host-card
entities:
- entity_id: remote.bravia_kd_65a8g
uuid: 70d2848b-d765-4fc0-b536-60044022739e
alias: ""
- entity_id: remote.universal_remote
uuid: 29ffe877-65a0-4aa2-b52b-5dd27878c45a
alias: ""
- entity_id: switch.clear_voice
alias: ""
uuid: 3d01da5a-0960-4582-89c4-0a93c3ba9b00
- entity_id: switch.dishwasher_power
alias: ""
uuid: dfdd413a-2b11-4a20-b380-2879379c9f23
Thanks for sharing the details and the screenshots — it helps clarify the situation. 
Regarding the Host Control Card:
As mentioned previously, the Host Card currently requires the AIKS or Link-On AV controller to fully function. Without one of these, selecting remote entities in the UI will not make the card appear or work correctly on the Astrion remote.
The card is also filtered to remote entities, so if you manually add switch entities (like @MRRIZK did), it can show up and respond. That’s expected behavior for testing purposes.
Some users have noticed sync issues, which can often be fixed by rearranging the cards in the UI and performing a sync again. This forces the card to refresh and display correctly.
For now, please ignore the Host Control Card unless you are using it with a supported AIKS / Link-On AV system. We plan to rework and fully develop this card for future applications, so it will be more flexible and reliable.
Your testing and feedback are very helpful — it allows us to understand how users interact with these cards in practice and will guide improvements in upcoming firmware updates.
— Charles
Sanytron Team