WHERE THIS TEST ENDED
The Flipper successfully replays the power command. Moving those codes into Fletcher is the next step.
- Original remote
- Flipper capture
- Saved button codes
- Replay test
Capture the remote I actually have
The projector above the desk turns on with its own remote. To reproduce those presses, I open infrared learning on the Flipper Zero, point the remote at it, and press a button. The Flipper detects the signal immediately in this test.
I save the captured buttons with names such as Up and Power. Keeping a name beside each code makes it possible to connect a software action to the right remote press later.
Test playback before building around it
After saving Power, I send that command back from the Flipper to the projector. The projector responds. That test establishes that the captured command can control this unit, before adding another board or a voice command to the chain.
The exported Remote.ir reference records NEC address 0x02, with commands Up 0x09, Down 0x01, Left 0x0A, Right 0x08, OK 0x0B, and Power 0x1D. These are the codes from my remote, rather than a code list assumed to fit every projector sold under the same model name.
What comes after this video
I end by planning to move the codes onto the computer and into the Raspberry Pi workflow. The next update builds the small transmitter that can stay near the projector.
The successful result here is capture and replay with the Flipper. Voice control and an automatic trip through the projector menus are later work.
About this breakdown
Matched to this original TikTok, including its spoken captions. Technical context also comes from the corresponding Fletcher build notes. The result above describes this episode; later work is identified separately.
Breakdown checked September 6, 2026.