🧩 Experimental ideas & development feedback

Astrion Astrion - Development & Advanced
, ,
21

The TV ROS Card should be able to to be pre-programmed with commands from LG webOS TV integration. For me personally I could use it but I use my LG TV as a display only and feed components (Shield TV and Oppo 205) into it.

Other major TV / Media Servers that could be added are:

22

Hi Datortarps :waving_hand:

First of all, welcome to the community — and thank you for the kind words. Really glad to hear you’re enjoying both the RosCard and the remote :raising_hands:

Appreciate you taking the time to share such structured feedback. I’ll respond to your points one by one:

:control_knobs: RosCard – Button-style UI

Yes, this is very aligned with our current direction.

We are actively working toward making the RosCard more UI-flexible and entity-driven, including:

  • custom buttons inside cards

  • richer layout composition

  • better grouping of controls per device / activity

The goal is exactly what you described: more “control surface” flexibility, less rigid templates.

:television: LG TV support

Good point — and also a common request.

We already see strong demand for native integrations across:

  • LG webOS (Home Assistant LG webOS TV integration)

  • Sony Bravia

  • Samsung Smart TV

Our direction here is not to hard-code per-brand cards, but to ensure the TV ROS Card can properly consume standard HA media entities, so integrations like LG webOS become plug-and-play through Home Assistant itself.

That said, we are actively reviewing optimizations for major platforms.

:alarm_clock: Clock / alarm on remote display

This is an interesting one because it touches both UX and product positioning.

We already support basic screensaver clock behavior, and we agree that:

  • “always-on clock while charging”

  • optional alarm functionality

…could be valuable for bedside use cases.

At the same time, we’re balancing this with the primary design intent (media + home control), so this may come as an optional mode rather than default behavior.

:repeat_button: Two-way remote integration (very important point)

We strongly agree here.

What you’re describing:

  • battery status reporting

  • find-my-remote

  • room/context awareness

  • brightness control via HA automations

…is exactly the direction we are moving toward.

We are working on a two-way state sync model between HA and Astrion, so the remote is not just a controller, but also a visible, manageable device inside the smart home ecosystem.

:compass: Overall direction

Your feedback aligns very well with what we are already prioritising:

  • richer RosCard UI model

  • stronger HA-native integration layer

  • more device state visibility (not just control)

  • improved media system compatibility

Thanks again for the thoughtful suggestions — and really appreciate you joining the community at this stage of the product. Feedback like this is exactly what helps shape the next iterations :+1: