Astrion HA100 Remote Controller - Complete Specifications & Features

Astrion Astrion - Knowledge Base & Tutorials
1

Astrion Smart Remote — Specifications & Overview

Hello everyone,

For those who are new to the Astrion ecosystem, here is an overview of the Astrion Smart Remote, a smart controller designed specifically for Home Assistant environments.

The Astrion remote combines Android-based flexibility, physical shortcut buttons, and a touchscreen interface to provide an efficient and convenient way to control smart home devices, scenes, and automations.

Product Overview

The Astrion Smart Remote (Model: HA100) is designed for smart home scenario management and deep integration with Home Assistant (HA).

It supports touchscreen control, physical shortcut buttons, and voice interaction, allowing users to quickly access devices, scenes, and automation functions.

Key Features

Magnetic Charging Dock

The Astrion remote includes a magnetic charging dock. Simply place the remote back on the dock after use to keep it charged and ready.

Dual Interaction Modes

Astrion supports both:

  • Touchscreen operation for dynamic smart home controls

  • Physical shortcut buttons for fast access to frequently used actions

Voice Control Support

Astrion includes a built-in microphone and a dedicated voice button located below the D-Pad, allowing users to trigger voice control features in Home Assistant.

Long Standby Battery

A 2000mAh rechargeable lithium battery provides extended standby time for daily smart home use.

Compact Smart Display

Astrion features a 3.1-inch touchscreen display with 480 × 800 resolution, providing clear visual control while keeping the device compact and ergonomic.

Basic Specifications

Parameter Details
Product Name Astrion Smart Remote
Model HA100
Operating System Android
Memory 1GB RAM + 8GB ROM
Display 3.1-inch touchscreen
Resolution 480 × 800 pixels
Wi-Fi 2.4 GHz (802.11 b/g/n)
Bluetooth Bluetooth 4.0
Battery 2000mAh rechargeable lithium battery
Power Input 5V DC, 2A
Button Backlight Supported
Microphone Built-in

Connectivity

Astrion currently supports:

  • Wi-Fi connection for Home Assistant integration

  • Bluetooth support

  • Built-in IR hardware (future firmware support planned)

Note: Infrared functionality is present in the hardware but not enabled in the current firmware version.

Product Dimensions

Dimension Size
Length 220 mm
Width 52.9 mm
Thickness 12.7 mm

Material

  • Aluminum alloy housing

  • High-gloss PC front panel

Environmental Parameters

Parameter Range
Operating Temperature 0°C – 45°C (non-condensing)
Storage Temperature −10°C – 60°C
Humidity 10% – 95% RH (indoor environment)

Package Contents

The Astrion package includes:

  • Astrion Smart Remote ×1

  • Magnetic Charging Dock ×1

  • USB Charging Cable ×1

  • User Manual ×1

  • Certificate of Conformity ×1

Compliance

The Astrion Smart Remote complies with RoHS (Restriction of Hazardous Substances) Directive standards for electrical and electronic equipment.

:speech_balloon: If you have any questions about Astrion setup, Home Assistant integration, or RosCard configuration, feel free to ask in the comments.

2

Might want to update that (and the web store pages!) if there is no plan to implement Bluetooth control functionality, currently it cant be used for any control functions and your team (or at least the AI replies) have basically confirmed it is impossible to implement without either a hardware revision, a complete OS overhaul, or a custom kernel driver.

Bluetooth control implementation would need the ability for the remote to use Bluetooth HID emulation at the very least, which Android 8 does not natively support.

1 Like
3

Hi Faceman :waving_hand:

Good catch — and thanks for raising this directly, because this is exactly the kind of wording issue that can easily create confusion.

Let me clarify it properly:

:blue_circle: 1. “Bluetooth support” vs “Bluetooth control”

You’re right to separate these.

At the moment, Astrion’s Bluetooth capability is not designed for HID / control emulation (keyboard, mouse, remote HID profiles, etc.).

So:

  • :white_check_mark: Bluetooth exists at hardware/system level

  • :cross_mark: It is not exposed as a “Bluetooth remote control / HID device” feature

  • :cross_mark: It is not intended to replace a Bluetooth universal remote

:gear: 2. Is HID control possible on current architecture?

Your assessment is broadly correct:

On the current Android-based stack:

  • native HID peripheral mode is not available in a clean or supported way

  • implementing full HID emulation would require:

    • kernel-level changes or

    • a deeply modified system framework layer

So yes — it is not something we can realistically “just enable” via app or firmware toggle.

:compass: 3. Why Bluetooth is present today

Bluetooth in Astrion is currently used for:

  • device connectivity (setup / pairing scenarios)

  • internal system components

  • future expansion paths (depending on hardware variants)

But it was never positioned as a universal Bluetooth control protocol layer.

:hammer_and_wrench: 4. Documentation / store page accuracy

You are absolutely right on this point.

If the current store or messaging implies “Bluetooth control functionality”, that is something we need to correct.

We will:

  • review all product page wording

  • clearly separate:

    • Bluetooth connectivity support

    • vs control protocol capabilities (IR / IP / HA / future extensions)

Clarity here is important to avoid mismatched expectations.

:rocket: 5. Long-term direction

Rather than forcing Bluetooth HID into the current architecture, the more realistic direction we are exploring is:

  • HA / IP-based control as primary path

  • Astrion as a control surface, not a Bluetooth peripheral

  • optional bridge layers (via HA or companion services) if needed

This keeps the system:

  • stable

  • extensible

  • and not tied to low-level OS limitations

:+1: Final note

Appreciate you calling this out directly — this is exactly the kind of technical realism that helps us avoid over-promising or ambiguous positioning.

We’ll make sure the messaging is corrected so it reflects the actual capability boundaries clearly.

1 Like