IR Remote

Not a single device. An IR Remote instance is one piece of gear paired with a codeset — a set of button-to-IR-code mappings — where each button becomes a command. Those codes are sent out through a pluggable emitter, so the same codeset works whether you blast it from a Global Caché box, a LIRC device, or an ESP32.

Connection

The codeset stays the same; the emitter transport is what changes:

• globalcache — iTach / GC-100 network IR.
• lirc — a local /dev/lirc0 device.
• serial — a USB or ESP32 IR blaster.
• network — a plain TCP emitter.
• mock — for testing without hardware.

Traits: ir.emitter and proxy. For the physical side — wiring an IR LED, choosing where to place it — see Wiring: IR.

Setup

• Transport — globalcache, lirc, serial, network, or mock.
• Emitter / port — for Global Caché, the specific IR port to use.
• Codeset — managed in the hub’s Remotes editor; each button maps to an IR code.

What it can do

Command	What it does
(codeset buttons)	Transmit the IR code bound to that button
learn	Capture an IR code from a physical remote
transmit	Send an arbitrary IR code as JSON
emitters	List available emitter ports (Global Caché)

Each button in the codeset shows up as its own command. learn captures codes from a real remote to build or extend a codeset, and transmit is the escape hatch for sending any IrCode directly.

Notes

Note

The codeset is a codeset config field on the driver, but you don’t hand-edit it — the Remotes editor writes the JSON into it. One codeset can be transmitted through any of the emitter transports.