rtl_433 decoder not upstreamed - at risk of being lost #10
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wait-to-fix
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
daru/PICsense#10
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
cryogencc_pickle_01.c lives in the rtl_433 submodule but is not in upstream. A submodule update could drop it.
Fix: upstream the decoder or maintain as a patch on top of the submodule.
We're working out of sync from the upstream intentionally right now---once we have our decoder locked in, we're going to pull the current version from upstream, add our changes, and submit a PR. For now we should wait on this.
Maybe it's possible to entirely utilize a flex decoder? Is it possible to assign bitfields like in the full device decoders?
The decoder
cryogencc_pickle_01.clives in the rtl_433 submodule atdeps/rtl_433/src/devices/and is tracked by theforgejo/feat-cryogencc_pickle_01remote branch. If the submodule is updated to a newer rtl_433 commit that doesn't include this branch, the decoder could be lost.Two options:
-Xflag which define the decoder inline. This avoids the upstreaming problem entirely.The flex decoder approach is viable: the commit
921be6fshowsrtl_433 -f 915000000 -X n=test,m=OOK_MC_ZEROBIT,...working. A flex decoder spec could be added to the README and the submodule dependency could eventually be removed for the decoder.The rtl_433 decoder (
cryogencc_pickle_01.c) was updated to match the new 0xCEBC preamble (was 0x1EBC). The tx_emulator'sgenerate_burst.pyalready had 0xCEBC but its comment said 0xA956655a — fixed to 0x5A56655A.The decoder still lives in the submodule. The flex decoder approach from commit
921be6f(rtl_433 -X n=test,m=OOK_MC_ZEROBIT,t=50,s=250,y=0,r=600,preamble=0xcebc,invert) is viable as a fallback, but upstreaming remains the cleanest long-term solution.The flex decoder is looking increasingly like a viable method for this device; for more advanced automatic setup, a full decoder will probably be necessary in the future.