RF Rolling code pairing/recording capabilities (port from Momentum firmware)#2567
RF Rolling code pairing/recording capabilities (port from Momentum firmware)#2567Doominator1 wants to merge 5 commits into
Conversation
…utech, Hormann) Add rolling_aes, rolling_code_db, rolling_code_proto modules and extend rf_send, rf_scan, rf_utils, RFMenu, config, and display with rolling code protocol detection, capture, replay, and UI integration. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
….gitignore" This reverts commit de35bc0.
|
Bruce-lilygo-t-embed-cc1101.bin.zip edit: updated .bin |
|
I have tried it on tembed c1101 and a cardputer adv with c1101/nrf24 and it works well. But what‘s with they /mfkeys, how does that work? |
Thanks for testing, the mfkeys are the manufacturer keys that a few protocols require (but not all), to use the rolling code signal generator with one of those protocols that require it, you need to supply the manufacturer keys yourself. Thanks |
Sorry for the late reply, I tried it with an old-ish garage door opener/motor thing, and it seems to pick up and receive a signal, but stuff like a tesla key make it ask for a "key to continue". I tried to figure out what's going on, but I can't seem to find the right info on the mfkeys and how to get them in there |
Ok that's good, the tesla one needing a key is expected - actually I don't think teslas are supported :/ |
|
I'd like to test it on my card computer. Do I need two CC1101 modules? I saw a video where the user uses two modules; with one, they receive the signal from the remote control, and the other module blocks the signal from being received by the gate. |
|
refactored RF is now on dev, i'm closing this PR as it is now outdated. Thank you for contributing. |
4 participants
HEAVILY UNTESTED - PLEASE HELP TEST IF YOU CAN
I couldn't test much because I obviously don't own every model of garage door in the world.
Signal creator - Bbility to pair with rolling code recievers (e.g. garage door, gate, ect.)
Rolling code scanner - Records rolling code RF signals, attempts to convert them into readable format (manufacturer, protocol, ect)
Rolling code signal sender - Ability to send previously paired rolling code signals to recievers, increments number by n.
Seperates Static RF from Rolling RF (2 different menus)
Basically everything ported from momentum firmware, adjusted/translated to work on bruce with the cc1101 (and maybe the other subghz transceiver, I haven't tested on the m5 stick as I don't have one).
I think this should be added because it would just be really useful for people wanting this feature and would make Bruce better!
Types of Changes
Verification
Try building from source or downloading the .bin and flashing, the ui should be split into 2 groups as said above, and the new rolling code features mentioned above should be there and usable.
Testing
We need YOU to help test that the signal pairing and signal recording works, because I cannot test them all myself, as I don't own a device for every protocol.
UI and basic signal testing has been done on the t-embed cc1101 plus - all the original features still work fully as before.
Linked Issues
#2181
#1956
User-Facing Change
Yes, current rf send/record menus have been moved into the Static RF submenu (to keep them all organised clean)
And obviously the new rolling code features being added.
Further Comments
Thanks a lot momentum community!
Also I removed the .codex_tmp folders because I don't think those are meant to be there right?
Images:
(will add soon)