feat: Host configuration tool (GUI) + rtl_433 decoder generation #47

New issue

Open

opened 2026-08-29 20:53:43 +00:00 by time · 0 comments

time commented

2026-08-29 20:53:43 +00:00

Contributor

A key requirement at this stage: the tool must also output a compliant rtl_433 decoder matching the configured packet format. The current decoder (deps/rtl_433/src/devices/cryogencc_pickle_01.c) is hand-written; the tool should generate one from the config so any configured packet format has a matching decoder.

Open questions:

language/stack (Python? C? GUI toolkit?)
serial port handling (FTDI/CP210x/CH340 drivers, baud rate)
how to represent the packet format declaratively so the decoder generator can consume it
generate a standalone .c file, or integrate with rtl_433's flex decoder
how to validate the generated decoder (round-trip test via the tx_emulator)

A PC application that talks to a device over the UART config session, provides a GUI for the configuration (frequency slot, region, update rate, analog pin config, I2C sensor config), and writes the config block to the device's EEPROM. A key requirement at this stage: the tool must also output a compliant rtl_433 decoder matching the configured packet format. The current decoder (`deps/rtl_433/src/devices/cryogencc_pickle_01.c`) is hand-written; the tool should generate one from the config so any configured packet format has a matching decoder. Open questions: - language/stack (Python? C? GUI toolkit?) - serial port handling (FTDI/CP210x/CH340 drivers, baud rate) - how to represent the packet format declaratively so the decoder generator can consume it - generate a standalone `.c` file, or integrate with rtl_433's flex decoder - how to validate the generated decoder (round-trip test via the `tx_emulator`)