Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New device - GN Resound / AB Transistor - Lynx Doorbell #3042

Open
kimballen opened this issue Aug 26, 2024 · 6 comments
Open

New device - GN Resound / AB Transistor - Lynx Doorbell #3042

kimballen opened this issue Aug 26, 2024 · 6 comments
Labels
device support Request for a new/improved device decoder

Comments

@kimballen
Copy link

New to this but can't get it right there's something I'm missing, very simple device just a doorbell.

433MHz

https://github.com/kimballen/rtl_433-Recorded-Signals/tree/main/GN%20Resound%20-%20AB%20Transistor%20Lynx%20Doorbell%20(433MHz)

@zuckschwerdt
Copy link
Collaborator

Try a sample on https://triq.org/pdv/ -- looks like 13 bits of (leading gap) PWM with 1000µs / 2000 µs pulses, bit-width 3000 µs. I.e. this should get your data: rtl_433 -R 0 -X 'n=lynx,m=OOK_PWM,s=1000,l=2000,r=3000'
Also best not to hit the transmission frequency dead on, default 433.92M should be fine.

@klohner
Copy link
Contributor

klohner commented Sep 2, 2024

The "code" value seems to have its bits reversed. This seems to work for me:

decoder {
    name          = Lynx_Doorbell,
    modulation    = OOK_PCM,
    short         = 1016,
    long          = 1016,
    reset         = 3048,
    bits         >= 40,
    bits         <= 41,
    preamble      = {1}8,
    symbol_zero   = {3}2,
    symbol_one    = {3}6,
    get           = id:@4:{8}:%d,
    get           = button:@0:{4}:[0:0 1:8 2:4 3:C 4:2 5:A 6:6 7:E 8:1 9:9 10:5 11:D 12:3 13:B 14:7 15:F],
}

@klohner
Copy link
Contributor

klohner commented Sep 2, 2024

Just found the product manual for the Lynx Door Transmitter. Perhaps, if what I thought was the ID is actually a static product code for all of these devices, this might be more discriminating:

decoder {
    name          = Lynx_Doorbell,
    modulation    = OOK_PCM,
    short         = 1016,
    long          = 1016,
    reset         = 3048,
    bits         >= 40,
    bits         <= 41,
    match         = {24}24b659,
    preamble      = {1}8,
    symbol_zero   = {3}2,
    symbol_one    = {3}6,
    get           = id:@4:{8}:%d,
    get           = button:@0:{4}:[0:0 1:8 2:4 3:C 4:2 5:A 6:6 7:E 8:1 9:9 10:5 11:D 12:3 13:B 14:7 15:F],
}

@zuckschwerdt
Copy link
Collaborator

@klohner do suspect it's really 40 bits PCM? I'm pretty sure it's 13 bits PWM with leading gaps. I.e. symbols of 1000 µs gap + 2000 µs pulse and 2000 µs gap + 1000 pulse.
E.g. "Code A" g188_433.884M_250k.cu8:

lynx13

@klohner
Copy link
Contributor

klohner commented Sep 2, 2024

You're right, but my decoder is doing OOK_PCM, discarding the first pulse symbol, then doing essentially "gap width modulation" on each group of three symbols with the symbol_zero and symbol_one patterns. The "bits" value seems to operate before the preamble and "symbol_*" decodings.

1 (discarded preamble symbol) + 12 * (3 symbols per logical bit) + 3 (trailing gap symbols before reset detected) = 40 symbols.

@zuckschwerdt
Copy link
Collaborator

Oops, completely missed the symbol_zero/symbol_one in your decoder, my bad.

@gdt gdt added the device support Request for a new/improved device decoder label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
device support Request for a new/improved device decoder
Projects
None yet
Development

No branches or pull requests

4 participants