Skip to Content

Beyond a Remote: The Thinking Behind Astrion Pro

How Astrion Pro builds on the HA100's familiar touchscreen-and-button design, responds to community feedback, and creates more room for the next stage of home control.
October 27, 2026 by
Beyond a Remote: The Thinking Behind Astrion Pro
Sanytron, Charles
| No comments yet

The Home Deserves Its Own Interface

Your phone is personal. Your home is shared.

We use our phones for communication, work, entertainment, and a hundred other things. But controlling a home is different. It's part of everyday life: adjusting the lights, starting a movie, changing the temperature, setting the right atmosphere for a moment.

These actions should feel immediate. They shouldn't always require finding a phone, unlocking it, opening an app, and navigating through layers of screens.

That belief has shaped Astrion from the beginning. We see a home-control device as more than a remote with a touchscreen. It's a dedicated physical interface between people and the technology around them.

Astrion Pro continues that idea. The familiar form is intentional. Rather than changing the design just to make a new product look different, we focused on evolving the hardware platform underneath — and on finding better ways for people to interact with their homes.

Astrion Pro builds on the HA100 design with a more capable hardware platform: an octa-core processor, Android 12, expanded memory and storage, and dual-band Wi-Fi. Infrared learning has been verified on production-intent hardware. Bluetooth HID and BLE compatibility remain subject to final validation, and we'll share specific compatibility claims once that work is complete. The goal is to give future software and interaction improvements more room to develop, while keeping the touchscreen-and-button approach that defines Astrion.

Why Touch and Physical Controls Belong Together

Astrion has 23 physical buttons alongside its touchscreen. Their purpose isn't simply to provide more controls. It's to make frequently used actions easier to find by touch.

A touchscreen is versatile. It can display different controls, present information, and adapt to the task at hand. But it also asks users to look at it, identify the right control, and sometimes navigate through several steps.

Consider a familiar situation: you're watching a movie and want to lower the volume, pause playback, or dim the lights. You may not want to interrupt your attention to hunt for the right screen or menu.

With a familiar layout, users can learn where important controls are and reach for them without studying the screen every time. That matters when adjusting volume mid-movie, navigating playback, or making a quick change without breaking the experience.

The touchscreen remains available for tasks that benefit from visual feedback and flexible controls. Neither interaction method has to do everything. The combination lets each one do what it's actually good at.

Astrion also has a dedicated physical voice button. Users can press and hold it to interact with Home Assistant Assist, without navigating through menus first. The principle is the same as with the physical controls: make interaction direct and easy to understand.

Voice is particularly useful when an intention is hard to express through a single button. A request involving lighting, media, and other devices may be more natural to say in ordinary language than to assemble through a series of separate controls. The actual result depends on the configured Home Assistant Assist pipeline, available integrations, and the actions the system can execute. We believe in the potential of this approach, but useful voice control has to be grounded in capabilities that work reliably in real homes.

The dedicated voice button isn't there to make Astrion feel futuristic. It's there to make voice accessible when voice is the right tool.

From Direct Actions to Intents and Activities

The most useful interface isn't the one with the most controls. It's the one that helps people accomplish what they want with the least unnecessary effort.

A button provides a direct, familiar action. A touchscreen exposes a wider range of choices. But a user's intention may be broader than any single device command.

When someone wants to watch a movie, the desired outcome might involve a display, an audio system, lighting, and curtains. The person is thinking about the experience, not about each individual device.

Our work on Intents and Activities explores how home-control experiences can be organized around these real-world goals. Rather than treating every device as an isolated destination, an Intent describes what a person wants to achieve, while an Activity provides a meaningful way to carry out that intention in context.

This doesn't make direct controls obsolete. Quite the opposite: familiar buttons remain valuable for immediate actions, while intent-driven interactions can offer a more natural way to coordinate complex tasks. We see them as complementary, not competing.

It's worth being clear about where things stand. Today, Astrion offers touchscreen controls, 23 physical buttons, and voice through the supported Home Assistant Assist integration. We're continuing to expand flexible button mapping within the capabilities supported by the software. More context-aware interaction remains a broader design direction that we intend to explore as the platform evolves. The longer-term direction — organizing control around intents and activities rather than isolated devices — is what we're working toward, not something already shipped.

That distinction matters to us. We'd rather be honest about the boundary than let a vision read like a feature list.

Why Astrion Pro Needed a Stronger Foundation

Astrion has continued to evolve through software improvements, Home Assistant integration work, and feedback from people using it in real homes.

That feedback clarified where the next hardware evolution mattered most. Users asked for more flexible Bluetooth-based control and the ability to learn infrared commands when an existing code library didn't cover their equipment.

These requests weren't about adding specifications for their own sake. They reflected a practical expectation: a home-control interface should adapt to the devices people already own.

The original HA100 has made real progress, but every hardware platform has limits. Processor capacity, memory, the operating system, and connectivity all influence how comfortably new capabilities can be developed and delivered.

Astrion Pro keeps the familiar physical design of the HA100 series while addressing the limitations of the original platform. The aim is to give future software improvements and new interaction capabilities the headroom they need, rather than trying to push every new idea onto hardware that was never designed for it.

That's the purpose of the Pro evolution: not to abandon what made Astrion distinctive, but to give that design philosophy a stronger base to work from.

The Next Step

Astrion Pro may look familiar beside the HA100 series. That's intentional.

The touchscreen-and-button combination remains central to our design. Our interest in Home Assistant, flexible physical interaction, voice, Intents, and Activities continues from the same starting point.

What changes is the foundation beneath that experience. Some capabilities are available today. Others require further implementation and validation. Our responsibility is to communicate that distinction clearly.

Astrion Pro is not a different remote. It's a stronger platform for a different way of thinking about home control.

We're grateful to the community whose questions, ideas, and real-world experiences helped shape this direction. We look forward to continuing that work together.

Your phone is personal. Astrion belongs to the home.

​

Share this post
Archive
Sign in to leave a comment