IR Devices

The HA100 has an infrared blaster. Astrion can use it to control your TV, amplifier, projector… without any hub, Home Assistant or cloud, fully offline.

An IR device is a named list of commands (power, hdmi1, volume_up…) for one physical device. You set it up once on the remote's web page › IR Devices, then use it everywhere: tiles, buttons, hotkeys, remote cards and Activities.

Two ways to get the codes

1. From the IR database (recommended)

Ready-made code sets by category › brand › model:

1. Open the ir-database picker and find your device.
2. Download the category file it gives you.
3. On the remote's web page › IR database, upload it.
4. IR Devices › + Add device › Reference the ir-database. Under Already on this remote, pick category › brand › model: the fields and the list of known commands fill in.
5. Name the device (TV living room) and Save.

The commands are read from the file at runtime, so keep the file on the remote. Deleting it warns you if a device still uses it.

2. Paste Pronto codes by hand

For a single button, or a code you learned yourself:

1. + Add device › Paste Pronto codes by hand.
2. Paste a Pronto Hex code (0000 006D 0022 …). Only learned codes, type 0000, are supported.
3. Give it an id (power, hdmi1…) and an optional label, then + Add command. Repeat for each button.
4. Save device.

Where are commands sent from?

Where should this device's commands actually get sent from?

• This remote's own IR blaster (default): point the remote at the device.
• An IR extender: a network IR blaster near the device, for a closed cabinet or another room. Only devices from the IR database can use an extender for now.

It's set once per device, and every card or hotkey using it follows.

Using an IR device

Where	How
Scene grid / button grid	IR device + command on a tile or button (e.g. an HDMI-input popup)
Hotkeys	In the JSON: "irDevice": "tv_lg", "irCommand": "power"
Activities	Power on/off and input commands per device, with a delay for slow TVs

Tips

• Point and range: the built-in blaster needs line of sight, like any remote. An extender removes that limit.
• Discrete codes are best: prefer power_on / power_off over a single power toggle when the database has them. Activities then never toggle a device the wrong way.
• Command ids are what you type in the JSON and see in the builder, so keep them short and consistent (volume_up, not Vol+).