📍 Astrion Remote Roadmap & Development Status

Astrion Astrion – Official Announcements
1

Welcome to the official Astrion Product Roadmap.

This topic provides a high-level overview of ongoing development, upcoming features, and long-term direction for Astrion Remote and related software such as RosCard.

:rocket: Current Focus

  • Firmware stability and performance optimization
  • RosCard UI/UX improvements
  • Home Assistant compatibility tracking
  • Expanded device and integration support

:compass: Planned Features (Subject to Change)

  • Advanced button and gesture customization
  • Expanded media and climate control capabilities
  • Improved multi-device and multi-room handling
  • Installer-oriented configuration enhancements

:counterclockwise_arrows_button: Status Definitions

  • Planned – Confirmed but not yet started
  • In Development – Actively being worked on
  • Testing – Internal or limited user testing
  • Released – Available to users

:ballot_box_with_ballot: Community Feedback

Feature requests and feedback are extremely valuable to us.
Please submit suggestions in the Feature Requests category so they can be properly tracked and prioritized.

:warning: Note: Roadmap items may change based on technical feasibility, stability, or user feedback.

Thank you for being part of the Astrion community.
— Sanytron Team

5

:rocket: HA100 Version 1.1.1 — Coming Soon!

We’re excited to share a preview of the upcoming HA100 v1.1.1 update, focused on expanding flexibility, improving usability, and responding directly to community feedback :light_bulb:

:sparkles: What’s New
• TV Cards now support script binding — buttons can directly run scripts for advanced control scenarios (IR commands, automations, multi-step actions, and more).
• Dropdown menu enabled — smoother navigation and better interaction flow.
(Note: When navigating within looping interfaces, Back will still return to the previous page.)
• Blank homepage guidance — if a homepage view is empty, helpful instructions and a refresh button will appear.
• Scene Cards upgraded → “Scenes & Scripts” — you can now add scripts directly inside these cards for more powerful control setups.

:locked: What’s Next
After v1.1.1 is released, we’ll dedicate the following two weeks to APK security optimizations to further strengthen system reliability and protection.

:folded_hands: Thank you to our community
Many of these improvements come directly from your suggestions and real-world use cases. Please keep the ideas coming — your feedback truly shapes the future of the platform.

If you’d like preview examples, configuration samples, or use-case guides after release, let us know what you want to see!

#HA100 #SmartControl #HomeAutomation #UpdatePreview

3 Likes
❓ Device compatibility questions (Lights, AC, TV, etc.)
6

Hi Charles,
that sounds very exciting. Looking forward to check it out once released.
Cheers

1 Like
7

Hi @Charles, exciting!

For script binding it would be great if you can pass variables to the script.

Example use case for me is the Foxtel STB that has all the IR codes learned in the IR file with its friendly name. ie: Power, Up, Down, Play, Pause etc so instead of having a script for each button you can just have the same script with a variable that is passed from the remote. eg device and command

action: remote.send_command
target:
  entity_id: remote.universal_remote
data:
  num_repeats: 1
  delay_secs: 0.4
  hold_secs: 0
  device: "{{ device }}"
  command: "{{ command }}"
1 Like
8

I fully agree with MRRIZK. Is this implemented in v1.1.1 ?

1 Like
9

Hi @MRRIZK and @starob,

Thanks for your feedback — you’ve both highlighted exactly the kind of flexibility we want Astrion to support! :+1:

In RosCard v1.1.1, you can now bind scripts to buttons like Up/Down/Volume+/Volume−, and assign different entities or scripts for each button. However, passing variables directly to scripts (like device and command) is not yet supported in v1.1.1.

This means that for now, you would still need separate scripts if you want to trigger different commands. Your example with the Foxtel STB is exactly the use case we have in mind for future updates.

We are actively planning to allow script parameterization in an upcoming version, so that a single script can handle multiple commands or devices, greatly reducing the number of scripts needed for setups like yours.

Thanks again for sharing your use case — feedback like this directly influences which features we prioritize next! :rocket:

— Charles
Sanytron Team