• Infrared
  • Intermediate
  • 3 min
  • Serial CLI

Recipe · Intermediate · Infrared

How to record an IR remote file

Use INFRARED record to capture remote frames and save them to LittleFS in Flipper-style .ir format.

Infrared remote file workflow.
Start with read-only checks, then move to write, replay or automation only when the setup is understood.
Step 1

Commands

Use the shortest command path that matches the documented firmware workflow. When a mode needs setup, follow the prompts shown on first entry.

Result

What it means

The command path is working when the target responds and the firmware prints the expected menu, status or captured data.

Troubleshooting

  • Re-enter the mode setup when pins or peripherals are not already initialized.
  • Check common ground and target voltage before blaming software.
  • Prefer Serial CLI for long captures or high-volume output.
  • Repeat the read or capture to confirm stability.

Next steps

  • Save the output in your project notes.
  • Compare the result with the full wiki page for mode-specific details.
  • Create a shorter alias if you repeat this workflow often.

Infrared .ir recording FAQ

When should I record a .ir file instead of using receive?

Use receive for quick protocol, address and command checks. Use record when you want a reusable LittleFS file, several buttons, or a signal that does not decode cleanly every time.

How do I know the recorded .ir file is usable?

Replay only on your own device and compare behavior with the original remote. If one button is unreliable, record it again under cleaner lighting and with a steady distance.

Where does the recorded IR file live?

The record workflow saves the captured remote data into LittleFS. Use the project file tools or Web UI workflow to manage, back up, or replace the .ir file.

Go deeper