Button Binding & Mapping FAQ
Advanced answers for users who want to understand the boundaries of Astrion Remote's button binding system — which buttons can be customized, how scripts work, and current limitations.
Button Binding Evolution
The Astrion Remote's button binding capabilities have evolved significantly across firmware versions. Understanding this evolution helps explain why certain buttons behave differently.
8 custom buttons — users could bind directly via the remote interface.
Gradual expansion — more buttons became available for binding across multiple versions.
8-button remapping — 4 smart home shortcuts became AV/media control buttons. TV Card supports up to 8 custom physical button mappings.
Button Event Reporting restored — physical button presses now report to Home Assistant for advanced automations[reference:2].
For the latest binding capabilities, always refer to the firmware release notes.
Can the physical volume/mute keys be bound globally?
Limited Support Currently, the physical volume +/− and mute buttons are handled by the system media control layer. They are not limited to a specific RosCard being displayed. However, the current firmware does not yet expose a fully customizable global button mapping interface for these keys.
The "Button Behavior" setting mentioned in the documentation is located in the RosCard configuration section, where button actions can be assigned for supported cards.
Tip: Volume keys work system-wide but are not fully customizable yet. This is on our roadmap for future firmware updates.
Are Light/Curtain/Music/AC/Custom 1–4 the complete list of globally bindable buttons? Can D-pad, Back, and Power also be bound?
Currently Supported At the moment, those are the buttons exposed through the current global binding interface.
The D-pad, Back, and Power buttons are handled differently:
- D-pad buttons are mainly designed for navigation and media control scenarios.
- Back and Power are system-level buttons and are not currently available for custom binding.
Future Consideration We are continuing to improve the button mapping system, and your feedback is exactly the type of use case we want to support.
Can a button bind to a script instead of a single entity?
Supported (with workaround) Currently, button binding is mainly designed around entities and service actions available through Home Assistant.
For more advanced logic, the recommended approach is to:
- Create a Home Assistant Script first
- Bind the action to that script
This allows you to combine multiple actions — for example: turning on TV + AVR + selecting input + launching Kodi — into one button press.
Tip: Scripts are the most powerful way to create complex automations triggered by a single button press. Learn more about Activities & Scripts →
Can a card be bindable without appearing on the home screen?
Not Yet Supported Currently, cards need to be available in the dashboard structure to be selected and used. A hidden or background card system is not supported yet.
Future Consideration We are aware of this use case and are considering ways to make card management more flexible in future versions.
Is the Scene list deliberately scoped to the home view only?
Current Design Yes, the current design mainly focuses on scenes available from the home dashboard.
Future Consideration We are considering ways to make scene access more flexible in future versions.
Can a macro target Power long-press specifically?
System Reserved At the moment, Power long-press is reserved as a system function and cannot be used as a custom macro trigger.
This is by design to ensure the power button always provides reliable system-level functionality.
Why does the volume overlay show when pressing Mute but not when pressing the physical +/− buttons?
Technical Explanation
You are correct that the media_player entity reports
volume_level correctly and supports:
VOLUME_SETVOLUME_STEPVOLUME_MUTE
The reason you see the volume overlay when pressing Mute, but not when pressing the physical +/− buttons, is because these two actions currently use different handling paths.
- Mute button triggers the Android/system volume overlay directly
- Physical volume +/− keys send volume step commands through the media control layer
The volume value changes correctly, but the overlay feedback is not triggered in the current implementation. This is being reviewed for future firmware updates.