ir-adapter

Turn IR sources into a common Signal that drives both ESPHome firmware and a Home Assistant IR-proxy custom component — one representation, two transmit paths. The signal/protocol sibling to ir-canonical (which owns the name).

pip install homeops-ir-adapter

Use it

from ir_adapter import flipper, ha, Signal

signals = flipper.from_file("TVs/Sony/Sony_Bravia.ir")   # a Flipper-IRDB .ir path
signals = ha.from_codeset("vizio/tv")                    # an infrared-protocols code set

s = signals[0]
s.name           # "Power"
s.canonical      # "power_toggle"  (resolved via homeops-ir-canonical; None if unmapped)
s.carrier_hz     # 38000
s.timings        # (9000, -4500, 560, -560, ...)  signed: + mark, - space
s.protocol       # "NEC" (None for raw captures)
s.address, s.command
s.repeat         # transmit-layer repeats (parsed frames need ~3)

Every Signal is self-describing: it carries its canonical control id, so a consumer (esp-codegen, concerto) depends only on homeops-ir-adapter and gets the control name for free — no separate name-resolution step.

A Signal carries both forms so either consumer uses what it needs:

Adapters

Parsed protocols (NEC/NECext, Sony SIRC/15/20, Samsung32, RC5/RC5X, Sharp) are encoded to timings by infrared-protocols — the same encoder HA's IR proxy uses, so codes are protocol-correct by construction. A Flipper type: raw capture passes through as-is.

Requires Python ≥ 3.14 (the infrared-protocols dependency). Parsing of .ir text works without it; encoding parsed protocols needs it.

Develop

python -m build --wheel --no-isolation
pip install dist/*.whl && pytest -q

Releases: release-please cuts a release PR; merging it tags + publishes to PyPI via trusted publishing (publish.yaml, environment pypi).