Protocols

Fourteen definitions ship with the program: ten verified, four draft.

The list is short on purpose. Adding a name to a menu is easy; being able to say why a reading is right is not. Every definition here either has a recording behind it or is marked as not having one.

Browse & edit definitions →

The protocol definitions repository on GitHub contains the JSON files, their schema and contribution guidelines.

What the two words mean

verified A real recording has been decoded with it and the result checked – ideally against an independent reading of the same signal, such as a Flipper's own decode of the same button press, or rtl_433's output for the same sensor. The definition carries that recording as a test, so a later change that breaks it fails the build.
draft Written from a datasheet, from somebody else's firmware, or from a recording that was not conclusive. It is ranked lower, because a definition that has never met a signal will cheerfully match ones it has nothing to do with – especially a short frame with no checksum, which cannot be told from noise on its own.

This distinction is not bureaucracy. One of the definitions below decoded its test recording perfectly — and backwards. Only a second, independent reading of the same button press showed it, and the bit order was inverted as a result.

Remote controls and gates

ProtocolStatusFrameNotes
EV1527
ev1527
verified 24 bit, PWM The most common cheap 433 MHz remote and PIR encoder: 20 bits of identifier, 4 of button.
PT2262
pt2262
verified 12 tri-state, PWM Older encoder whose address and data lines carry three states, not two. Read as tri-state rather than forced into binary.
CAME 18-bit
came-18
verified 18 bit, PWM Used by appliance remotes as well as gates. Verified against a Flipper RAW and Key pair, which is what revealed the inverted bit order.
GateTX
gate-tx
verified 24 bit, PWM Verified against a paired RAW and Key capture from a TX028C-S ceiling-fan remote.
Somfy RTS
somfy-rts
verified 56 bit, Manchester Blind and awning remote on the unusual 433.42 MHz. Identification only – it is a rolling code, and the payload is obfuscated.
KeeLoq
keeloq
draft 66 bit, PWM Gate, garage and alarm remotes with a Microchip HCS encoder. Identification only – the frame is split into its encrypted part, serial number and buttons, and nothing is decrypted. Draft because a rolling-code recording cannot be published as its evidence.
CAME 12-bit
came
draft 12 bit, PWM Gate and garage remotes in their twelve-bit form, and the many clones of it.
Nice FLO
nice-flo
draft 12 bit, PWM Fixed code, frames separated by a gap alone and no checksum – which is precisely why it stays a draft: there is nothing in the frame to tell it apart from noise.
Holtek HT12X
holtek-ht12x
draft 12 bit, PWM From the datasheet and a 315 MHz sweep recording. The framing is consistent at a measured 430 µs element, but the frame is ambiguous with CAME and no paired decoded key has confirmed it.

Weather and temperature sensors

ProtocolStatusFrameNotes
Nexus-TH
nexus-th
verified 36 bit, PPM A very common cheap outdoor temperature and humidity sensor, sold under many names.
Fine Offset WH2
fineoffset-wh2
verified 48 bit, PWM Also sold as Agimex Rosenborg 66796 and various Clime models.
Acurite 609TXC
acurite-609txc
verified 40 bit, PPM Outdoor sensor for the 00609 and similar displays.
LaCrosse TX141TH-Bv2
lacrosse-tx141thb2
verified 40 bit, PWM Verified against a Flipper RAW and decoded Key pair: the identifier, temperature and humidity all agree, and the digest checks out.
Bresser 6-in-1
bresser-6in1
verified 144 bit, FSK, PCM The first FSK definition: framed on the sync word 0x2dd4 and protected by a 16-bit LFSR digest. Only the identifier, sensor type and channel are declared; temperature, humidity, wind and rain are packed in a way the schema cannot describe yet.

Writing your own

A definition is a small JSON file against a schema published in the definitions repository – radio parameters, timing, coding, frame layout, fields and a check – not code. Put yours in your own folder (Settings → Protocol definitions) and it is loaded after the built-in ones, so a definition with the same id replaces one that ships with the program. That is how you fix a shipped definition without waiting for a release.

Supported today:

ModulationOOK/ASK end to end, and 2-FSK through the PCM coding, which frames the demodulated bit stream on a sync word. 4-FSK and PSK are demodulated and give bits, but a definition cannot be driven from them yet, so that work continues in Bits.
CodingPWM, PPM, Manchester (both conventions), NRZ, differential Manchester, PCM
ChecksParameterised CRC-8 and CRC-16, byte sum, XOR, LFSR digest
FieldsUnsigned, signed, BCD, with scale and offset – so a sensor reads in °C and per cent, not in hex

The shipped definitions are released under CC0 1.0: use them anywhere, including in rtl_433, ESPHome or Flipper firmware, without asking and without credit.

What is missing, and why