Reverse engineer a remote, sensor or alarm

A burst nothing decodes is still kept. Click its row for the envelope, the instantaneous frequency and a hex dump, with the coding inferred and the bits sliced out, which is enough to recognise the same device again and start working out what the fields mean.

The packet log stores the mark and gap timings, the frame bytes and the burst’s own samples rather than the parsed fields, so a decoder written next month gets its chance at a burst heard today. --record writes rtl_433 style captures that both programs read, and the raw capture can be armed on energy so a file is written per burst with the signal from before it triggered.

The scripts panel holds every Flipper .sub file on the machine and keys one at the frequency it names, and a heard burst can be written back out as a key file, which closes the loop between reading a remote and reproducing it.

$ waveshark --tune 433.92 --record captures
$ waveshark --replay captures